Remote MCP · Endpoint

Site MCP MCP server

No. Site MCP answered an MCP handshake 2 hours ago.

UpLast checked 2 hours ago

Server URL

https://sitemcp.dev/sitemcp.dev

The last check completed an MCP handshake.

Registry name
dev.sitemcp/site-mcp
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
125 ms
Tools exposed
6 tools
Uptime, last 30 days
100% from 15 checks
Described by its publisher as
Turn any public website into an MCP server for agents to search, read and navigate.
Listing
From the official MCP registry (active).
Recent checks of Site MCP
CheckedResultHandshake
2 hours agoHandshake completed125 ms
2 days agoHandshake completed204 ms
4 days agoHandshake completed67 ms
6 days agoHandshake completed100 ms
8 days agoHandshake completed106 ms
9 days agoHandshake completed116 ms
11 days agoHandshake completed98 ms
11 days agoHandshake completed603 ms
14 days agoHandshake completed62 ms
15 days agoHandshake completed106 ms
17 days agoHandshake completed69 ms
19 days agoHandshake completed65 ms
20 days agoHandshake completed615 ms
21 days agoHandshake completed422 ms
22 days agoHandshake completed262 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 MCP and makes no claim about it beyond what these checks measured.