Remote MCP · Endpoint

webcheck MCP server

Yes, as of 1 day ago: the server returned an HTTP error.

DownLast checked 1 day ago

Server URL

https://webcheck.nanocorp.app/mcp

The last check failed: the server returned an HTTP error.

Registry name
app.nanocorp.webcheck/webcheck
Transport
Streamable HTTP
Protocol negotiated
Not measured yet
Handshake latency
—
Tools exposed
1 tool
Uptime, last 30 days
83.3% from 12 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 day agoFailed - the server returned an HTTP error—
5 days agoFailed - the server returned an HTTP error—
16 days agoHandshake completed146 ms
17 days agoHandshake completed1.08 s
17 days agoHandshake completed633 ms
19 days agoHandshake completed269 ms
20 days agoHandshake completed344 ms
21 days agoHandshake completed350 ms
22 days agoHandshake completed423 ms
23 days agoHandshake completed148 ms
25 days agoHandshake completed1.79 s
27 days agoHandshake completed410 ms
30 days agoHandshake completed381 ms

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

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