Remote MCP · Endpoint

Sitecomb MCP server

No. Sitecomb answered an MCP handshake 21 minutes ago.

UpLast checked 21 minutes ago

Server URL

https://sitecomb.com/mcp

The last check completed an MCP handshake.

Registry name
com.sitecomb/check-website
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
115 ms
Tools exposed
2 tools
Uptime, last 30 days
100% from 14 checks
Described by its publisher as
A quality score out of 100 for any website, plus the areas that need work.
Website
https://sitecomb.com/claude
Listing
From the official MCP registry (active).
Recent checks of Sitecomb
CheckedResultHandshake
21 minutes agoHandshake completed115 ms
9 days agoHandshake completed74 ms
9 days agoHandshake completed68 ms
11 days agoHandshake completed94 ms
12 days agoHandshake completed75 ms
13 days agoHandshake completed135 ms
14 days agoHandshake completed79 ms
15 days agoHandshake completed80 ms
16 days agoHandshake completed81 ms
19 days agoHandshake completed91 ms
21 days agoHandshake completed67 ms
24 days agoHandshake completed79 ms
26 days agoHandshake completed106 ms
28 days agoHandshake completed89 ms

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

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.

Related

All hosted MCP serversGlide connector for AI assistantsGlide for AI agents

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