https://app.dialfetch.com/api/mcp ↗
com.dialfetch/dialfetch is a remote MCP server published at app.dialfetch.com. It has been probed 35 times since 9/4/2026. It answered in only 0 of them (0.0%), indicating low availability. Median response time is 198 ms, placing it among the faster endpoints. Its tool list could not be read; the server is closed to direct calls.
Give your AI agent a phone: place calls, navigate IVRs, wait on hold, get structured answers.
Can an LLM agent pick the right tool here — names, descriptions and parameter clarity are assessed.
| Run | Era | Modern | ms | Legacy | ms | Versions |
|---|---|---|---|---|---|---|
| 2026-09-07 07:55:38 | Unreachable * | — | 71 | — | 70 | — |
| 2026-09-07 05:25:31 | Unreachable * | — | 135 | — | 134 | — |
| 2026-09-07 02:57:58 | Unreachable * | — | 198 | — | 196 | — |
| 2026-09-07 00:27:42 | Unreachable * | — | 82 | — | 81 | — |
| 2026-09-06 22:36:06 | Unreachable * | — | 111 | — | 112 | — |
| 2026-09-06 20:44:13 | Unreachable * | — | 154 | — | 154 | — |
| 2026-09-06 18:49:47 | Unreachable * | — | 132 | — | 132 | — |
| 2026-09-06 16:56:18 | Unreachable * | — | 154 | — | 153 | — |
| 2026-09-06 15:42:25 | Unreachable * | — | 90 | — | 92 | — |
| 2026-09-06 13:49:02 | Unreachable * | — | 79 | — | 77 | — |
Each cell is one probe run. Faded cells are incomplete probes — one leg did not answer, so the era is inconclusive.
The two probe legs separately: modern server/discover and legacy initialize.
Derived by comparing consecutive probes — changes in era, protocol version, build and reachability.
Add this badge to your README — it updates automatically as measurements change.
[](https://mcpmetrics.io/servers/com-dialfetch-dialfetch)<a href="https://mcpmetrics.io/servers/com-dialfetch-dialfetch"><img src="https://mcpmetrics.io/badge/com.dialfetch/dialfetch/era.svg" alt="mcpmetrics"></a>You are seeing the last 7 days. Sign up for the full history. Which check failed and why is in the dashboard.
Sign up free to see