Is MCP Assist — Coordination Memory down?
Down
Yes, MCP Assist — Coordination Memory is down.
It has not passed a check since we started checking it on 11 Oct 2026. Latest error: initialize returned HTTP 404.
Latest check
- Last check
- 25 h ago (17 Oct 2026, 07:08 UTC)
- Response time
- Not measured
- Next check
- In about 2 h
- How often
- About every 27 hours over the last 7 days
Uptime
Uptime is the share of checks that passed. We checked it about every 27 hours 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 |
|---|---|---|---|
| 17 Oct 2026, 07:08 UTC | initialize returned HTTP 404 | 404 | 208 ms |
| 16 Oct 2026, 02:45 UTC | initialize returned HTTP 404 | 404 | 132 ms |
| 15 Oct 2026, 00:37 UTC | initialize returned HTTP 404 | 404 | 148 ms |
| 13 Oct 2026, 18:41 UTC | initialize returned HTTP 404 | 404 | 81 ms |
| 12 Oct 2026, 13:10 UTC | initialize returned HTTP 404 | 404 | 151 ms |
| 12 Oct 2026, 03:28 UTC | initialize returned HTTP 404 | 404 | 97 ms |
| 11 Oct 2026, 18:05 UTC | initialize returned HTTP 404 | 404 | 109 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 27 hours 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.