Remote MCP · Endpoint

webcheck MCP server

No. webcheck answered an MCP handshake 1 hour ago.

UpLast checked 1 hour ago

Server URL

https://webcheck.nanocorp.app/mcp

The last check completed an MCP handshake.

Registry name
app.nanocorp.webcheck/webcheck
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
350 ms
Tools exposed
1 tool
Uptime, last 30 days
100% from 14 checks
Described by its publisher as
The website checker for AI agents. One call: verdict, score out of 100, fix list.
Listing
From the official MCP registry (active).
Recent checks of webcheck
CheckedResultHandshake
1 hour agoHandshake completed350 ms
1 day agoHandshake completed423 ms
2 days agoHandshake completed148 ms
3 days agoHandshake completed1.79 s
6 days agoHandshake completed410 ms
9 days agoHandshake completed381 ms
11 days agoHandshake completed450 ms
13 days agoHandshake completed427 ms
15 days agoHandshake completed384 ms
17 days agoHandshake completed425 ms
19 days agoHandshake completed236 ms
21 days agoHandshake completed187 ms
23 days agoHandshake completed296 ms
24 days agoHandshake completed526 ms

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

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