Remote MCP · Endpoint

Site Check MCP server

No. Site Check answered an MCP handshake 1 hour ago.

UpLast checked 1 hour ago

Server URL

https://mcp.modernmustardseed.com/site-check

The last check completed an MCP handshake.

Registry name
com.modernmustardseed/site-check
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
37 ms
Tools exposed
4 tools
Uptime, last 30 days
100% from 15 checks
Described by its publisher as
Public website health scan, AI-crawler and structured-data readiness, and a local presence score.
Listing
From the official MCP registry (active).
Recent checks of Site Check
CheckedResultHandshake
1 hour agoHandshake completed37 ms
1 day agoHandshake completed39 ms
2 days agoHandshake completed37 ms
3 days agoHandshake completed55 ms
4 days agoHandshake completed32 ms
5 days agoHandshake completed36 ms
6 days agoHandshake completed24 ms
9 days agoHandshake completed37 ms
11 days agoHandshake completed26 ms
14 days agoHandshake completed36 ms
16 days agoHandshake completed45 ms
18 days agoHandshake completed53 ms
20 days agoHandshake completed31 ms
22 days agoHandshake completed50 ms
24 days agoHandshake completed46 ms

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

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 Site Check and makes no claim about it beyond what these checks measured.