Is DialMyCalls MCP by usefulapi down?
Down
Yes, DialMyCalls MCP by usefulapi is down.
It has not passed a check since we started checking it on 24 Oct 2026. Latest error: initialize returned HTTP 302.
Latest check
- Last check
- 18 h ago (10 Nov 2026, 09:10 UTC)
- Response time
- Not measured
- Next check
- In about 3 days
- How often
- About every 4 days over the last 7 days
Uptime
Uptime is the share of checks that passed. We checked it about every 4 days over the last 7 days.
Outages in the last 30 days
No outages in the last 30 days. An outage starts when two checks in a row fail and ends at the next passing check.
Recent checks
| When | Result | HTTP | Time |
|---|---|---|---|
| 10 Nov 2026, 09:10 UTC | initialize returned HTTP 302 | 302 | 109 ms |
| 6 Nov 2026, 20:29 UTC | initialize returned HTTP 302 | 302 | 136 ms |
| 3 Nov 2026, 12:33 UTC | initialize returned HTTP 302 | 302 | 79 ms |
| 2 Nov 2026, 04:32 UTC | initialize returned HTTP 302 | 302 | 71 ms |
| 1 Nov 2026, 01:17 UTC | initialize returned HTTP 302 | 302 | 480 ms |
| 30 Oct 2026, 18:32 UTC | initialize returned HTTP 302 | 302 | 84 ms |
| 29 Oct 2026, 12:14 UTC | initialize returned HTTP 302 | 302 | 119 ms |
| 28 Oct 2026, 03:23 UTC | initialize returned HTTP 302 | 302 | 119 ms |
| 26 Oct 2026, 20:11 UTC | initialize returned HTTP 302 | 302 | 149 ms |
| 25 Oct 2026, 12:41 UTC | initialize returned HTTP 302 | 302 | 112 ms |
How we check
Up means the MCP handshake and the tool list worked, or the server asked for sign-in or payment.
Checks come from our server, about every 4 days for this listing over the last 7 days. A failure can also mean the service blocks our checks. Two failed checks in a row count as an outage, which ends at the next passing check.
If you think a check is wrong, contact hello@toolvet.app. More on how we check and score.