Remote MCP · Endpoint

SiteCheck MCP server

No. SiteCheck answered an MCP handshake 22 minutes ago.

UpLast checked 22 minutes ago

Server URL

https://api.sitecheck-api.workers.dev/mcp?ref=registry

The last check completed an MCP handshake.

Registry name
io.github.bck-stack/sitecheck
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
911 ms
Tools exposed
225 tools
Uptime, last 30 days
100% from 14 checks
Described by its publisher as
225 pay-per-call agent tools: Polymarket, chain reads, DeFi, web, SEC, KYB, geo, dev, AI. x402
Listing
From the official MCP registry (active).
Recent checks of SiteCheck
CheckedResultHandshake
22 minutes agoHandshake completed911 ms
9 days agoHandshake completed77 ms
10 days agoHandshake completed158 ms
11 days agoHandshake completed652 ms
12 days agoHandshake completed347 ms
14 days agoHandshake completed443 ms
14 days agoHandshake completed503 ms
15 days agoHandshake completed130 ms
17 days agoHandshake completed717 ms
19 days agoHandshake completed79 ms
21 days agoHandshake completed49 ms
24 days agoHandshake completed60 ms
26 days agoHandshake completed354 ms
28 days agoHandshake completed697 ms

The last 14 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 SiteCheck and makes no claim about it beyond what these checks measured.