Remote MCP · Endpoint
SiteCheck MCP server
No. SiteCheck answered an MCP handshake 3 days ago.
UpLast checked 3 days ago
Server URL
https://api.sitecheck-api.workers.dev/mcp
The last check completed an MCP handshake.
- Registry name
- io.github.bck-stack/sitecheck
- Transport
- Streamable HTTP
- Protocol negotiated
- 2025-06-18
- Handshake latency
- 59 ms
- Tools exposed
- 225 tools
- Uptime, last 30 days
- 100% from 12 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).
| Checked | Result | Handshake |
|---|---|---|
| 3 days ago | Handshake completed | 59 ms |
| 7 days ago | Handshake completed | 411 ms |
| 16 days ago | Handshake completed | 666 ms |
| 17 days ago | Handshake completed | 554 ms |
| 18 days ago | Handshake completed | 585 ms |
| 19 days ago | Handshake completed | 85 ms |
| 21 days ago | Handshake completed | 71 ms |
| 21 days ago | Handshake completed | 128 ms |
| 22 days ago | Handshake completed | 596 ms |
| 24 days ago | Handshake completed | 105 ms |
| 26 days ago | Handshake completed | 58 ms |
| 28 days ago | Handshake completed | 450 ms |
The last 12 checks. Full history is kept for 30 days; the all-time counter stands at 20 responding of 20.
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.