Is PostCode Check down?

MCP serverBy postcodecheck.mike-tusa.workers.dev. How to connect and its trust score are on the listing page.

Up

No, PostCode Check is up.

It passed its latest check 5 h ago in 108 ms, and every check since we started checking it on 26 Oct 2026.

Latest check

Last check
5 h ago (31 Oct 2026, 15:12 UTC)
Response time
108 ms (typical 112 ms)
Next check
In about 8 h
How often
About every 13 hours over the last 7 days

Uptime

Last 24 hours100%2 checks
Last 7 days100%10 checks
Last 30 days100%10 checks
All checks passedSome failedAll failedNot checked

Uptime is the share of checks that passed. We checked it about every 13 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

WhenResultHTTPTime
31 Oct 2026, 15:12 UTCPassed200108 ms
31 Oct 2026, 00:55 UTCPassed200105 ms
30 Oct 2026, 11:31 UTCPassed200106 ms
29 Oct 2026, 22:26 UTCPassed200118 ms
29 Oct 2026, 08:42 UTCPassed200143 ms
28 Oct 2026, 19:27 UTCPassed200116 ms
28 Oct 2026, 05:48 UTCPassed200112 ms
27 Oct 2026, 17:13 UTCPassed200132 ms
27 Oct 2026, 04:12 UTCPassed20095 ms
26 Oct 2026, 15:50 UTCPassed200115 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 13 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.