Remote MCP · Endpoint

VerifyMCP MCP server

No. VerifyMCP answered an MCP handshake 35 minutes ago.

UpLast checked 35 minutes ago

Server URL

https://mcp.verifymcp.io/

The last check completed an MCP handshake.

Registry name
io.verifymcp/mcp
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
312 ms
Tools exposed
9 tools
Uptime, last 30 days
100% from 14 checks
Described by its publisher as
Independent trust scores, tool surfaces and change history for MCP servers.
Listing
From the official MCP registry (active).
Recent checks of VerifyMCP
CheckedResultHandshake
35 minutes agoHandshake completed312 ms
9 days agoHandshake completed300 ms
10 days agoHandshake completed322 ms
11 days agoHandshake completed294 ms
12 days agoHandshake completed317 ms
14 days agoHandshake completed310 ms
14 days agoHandshake completed303 ms
15 days agoHandshake completed349 ms
17 days agoHandshake completed345 ms
19 days agoHandshake completed372 ms
21 days agoHandshake completed297 ms
24 days agoHandshake completed376 ms
26 days agoHandshake completed306 ms
28 days agoHandshake completed377 ms

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

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