Remote MCP · Endpoint
VerifyMCP MCP server
No. VerifyMCP answered an MCP handshake 1 hour ago.
UpLast checked 1 hour 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
- 377 ms
- Tools exposed
- 9 tools
- Uptime, last 30 days
- 100% from 18 checks
- Described by its publisher as
- Independent trust scores, tool surfaces and change history for MCP servers.
- Website
- https://verifymcp.io/
- Repository
- https://github.com/Im5tu/verifymcp
- Listing
- From the official MCP registry (active).
| Checked | Result | Handshake |
|---|---|---|
| 1 hour ago | Handshake completed | 377 ms |
| 2 days ago | Handshake completed | 380 ms |
| 4 days ago | Handshake completed | 620 ms |
| 6 days ago | Handshake completed | 315 ms |
| 7 days ago | Handshake completed | 325 ms |
| 9 days ago | Handshake completed | 636 ms |
| 10 days ago | Handshake completed | 358 ms |
| 11 days ago | Handshake completed | 312 ms |
| 14 days ago | Handshake completed | 278 ms |
| 15 days ago | Handshake completed | 289 ms |
| 17 days ago | Handshake completed | 299 ms |
| 19 days ago | Handshake completed | 321 ms |
| 20 days ago | Handshake completed | 288 ms |
| 21 days ago | Handshake completed | 278 ms |
| 22 days ago | Handshake completed | 337 ms |
| 22 days ago | Handshake completed | 325 ms |
| 23 days ago | Handshake completed | 297 ms |
| 25 days ago | Handshake completed | 298 ms |
The last 18 checks. Full history is kept for 30 days; the all-time counter stands at 18 responding of 18.
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.