Is unmarking down?

MCP serverBy unmark.ing. How to connect and its trust score are on the listing page.

Down

Yes, unmarking is down.

It has failed every check since 21 Oct 2026, 18:02 UTC (5 days 9 h, 6 checks). Latest error: initialize returned HTTP 404. It last passed on 21 Oct 2026, 08:08 UTC.

Latest check

Last check
24 h ago (26 Oct 2026, 02:57 UTC)
Response time
Not measured (typical 363 ms)
Next check
In about 3 h
How often
About every 10 hours over the last 7 days

Uptime

Last 24 hours0.0%1 check
Last 7 days40.0%10 checks
Last 30 days80.7%31 checks
All checks passedSome failedAll failedNot checked

Uptime is the share of checks that passed. We checked it about every 10 hours over the last 7 days.

Outages in the last 30 days

1 outage, 5 days 9 h of failed checks in total.

StartedDurationFailed checksFirst error
21 Oct 2026, 18:02 UTCOngoing, 5 days 9 h so far6initialize returned HTTP 404

Times are when our checks ran, about every 10 hours for this listing, so start times and durations are accurate to about that.

Recent checks

WhenResultHTTPTime
26 Oct 2026, 02:57 UTCinitialize returned HTTP 404404326 ms
24 Oct 2026, 20:57 UTCinitialize returned HTTP 404404405 ms
23 Oct 2026, 18:17 UTCinitialize returned HTTP 404404372 ms
22 Oct 2026, 12:57 UTCinitialize returned HTTP 404404669 ms
22 Oct 2026, 02:58 UTCinitialize returned HTTP 404404376 ms
21 Oct 2026, 18:02 UTCinitialize returned HTTP 404404427 ms
21 Oct 2026, 08:08 UTCPassed200434 ms
20 Oct 2026, 22:05 UTCPassed200304 ms
20 Oct 2026, 12:43 UTCPassed200446 ms
20 Oct 2026, 03:43 UTCPassed200395 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 10 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.