Remote MCP · Endpoint

Corrie Site Check MCP server

No. Corrie Site Check answered an MCP handshake 36 minutes ago.

UpLast checked 36 minutes ago

Server URL

https://corrie.io/mcp

The last check completed an MCP handshake.

Registry name
io.corrie/site-check
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
263 ms
Tools exposed
1 tool
Uptime, last 30 days
100% from 14 checks
Described by its publisher as
Free HTTPS and security header check from Corrie, uptime monitoring for small teams. No auth.
Listing
From the official MCP registry (active).
Recent checks of Corrie Site Check
CheckedResultHandshake
36 minutes agoHandshake completed263 ms
8 days agoHandshake completed118 ms
9 days agoHandshake completed102 ms
11 days agoHandshake completed101 ms
12 days agoHandshake completed102 ms
12 days agoHandshake completed328 ms
14 days agoHandshake completed122 ms
14 days agoHandshake completed223 ms
16 days agoHandshake completed165 ms
19 days agoHandshake completed141 ms
21 days agoHandshake completed108 ms
24 days agoHandshake completed103 ms
26 days agoHandshake completed103 ms
28 days agoHandshake completed99 ms

The last 14 checks. Full history is kept for 30 days; the all-time counter stands at 16 responding of 16.

How to read this

  • ·Handshake latency is one measurement from one probe, from our infrastructure. It is a smoke signal about the endpoint, not a benchmark of your own connection to it.
  • ·An authentication challenge counts as responding. A hosted server that refuses an anonymous prober is behaving correctly.
  • ·A tool count of “behind credentials” means the handshake worked but listing tools needed a token we do not hold.
  • ·Uptime covers the last 30 days of our own checks, at most one an hour, and says how many checks it is drawn from.

Listing data comes from the official MCP registry. Glide is not affiliated with Corrie Site Check and makes no claim about it beyond what these checks measured.