Is Attest MCP Remote down?
Down
Yes, Attest MCP Remote is down.
It has failed every check since 19 Oct 2026, 06:55 UTC (22 days 7 h, 14 checks). Latest error: initialize returned HTTP 500. It last passed on 18 Oct 2026, 22:50 UTC.
Latest check
- Last check
- 1 h ago (10 Nov 2026, 12:16 UTC)
- Response time
- Not measured (typical 842 ms)
- Next check
- In about 3 days
- How often
- About every 3 days over the last 7 days
Uptime
Uptime is the share of checks that passed. We checked it about every 3 days over the last 7 days.
Outages in the last 30 days
1 outage, 22 days 7 h of failed checks in total.
| Started | Duration | Failed checks | First error |
|---|---|---|---|
| 19 Oct 2026, 06:55 UTC | Ongoing, 22 days 7 h so far | 14 | initialize returned HTTP 500 |
Times are when our checks ran, about every 3 days for this listing, so start times and durations are accurate to about that.
Recent checks
| When | Result | HTTP | Time |
|---|---|---|---|
| 10 Nov 2026, 12:16 UTC | initialize returned HTTP 500 | 500 | 599 ms |
| 7 Nov 2026, 03:49 UTC | initialize returned HTTP 500 | 500 | 451 ms |
| 4 Nov 2026, 02:00 UTC | initialize returned HTTP 500 | 500 | 739 ms |
| 31 Oct 2026, 22:40 UTC | initialize returned HTTP 500 | 500 | 641 ms |
| 28 Oct 2026, 13:38 UTC | initialize returned HTTP 500 | 500 | 746 ms |
| 27 Oct 2026, 07:49 UTC | initialize returned HTTP 500 | 500 | 688 ms |
| 25 Oct 2026, 22:53 UTC | initialize returned HTTP 500 | 500 | 592 ms |
| 24 Oct 2026, 17:41 UTC | initialize returned HTTP 500 | 500 | 876 ms |
| 23 Oct 2026, 12:50 UTC | initialize returned HTTP 500 | 500 | 563 ms |
| 22 Oct 2026, 08:05 UTC | initialize returned HTTP 500 | 500 | 774 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 3 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.