Remote MCP · Endpoint
Verifi MCP server
No. Verifi answered an MCP handshake 6 hours ago.
UpLast checked 6 hours ago
Server URL
https://verifi.cloud/mcp
The last check completed an MCP handshake.
- Registry name
- cloud.verifi/human-verification
- Transport
- Streamable HTTP
- Protocol negotiated
- 2025-06-18
- Handshake latency
- 335 ms
- Tools exposed
- 4 tools
- Uptime, last 30 days
- 100% from 17 checks
- Described by its publisher as
- Get a real human to verify, decide, or improve an AI agent's work. Pay per review via x402 on Base.
- Website
- https://verifi.cloud/docs/
- Repository
- https://github.com/jyharju-code/verifi
- Listing
- From the official MCP registry (active).
| Checked | Result | Handshake |
|---|---|---|
| 6 hours ago | Handshake completed | 335 ms |
| 2 days ago | Handshake completed | 334 ms |
| 4 days ago | Handshake completed | 330 ms |
| 5 days ago | Handshake completed | 333 ms |
| 7 days ago | Handshake completed | 333 ms |
| 8 days ago | Handshake completed | 332 ms |
| 9 days ago | Handshake completed | 336 ms |
| 12 days ago | Handshake completed | 332 ms |
| 13 days ago | Handshake completed | 329 ms |
| 15 days ago | Handshake completed | 352 ms |
| 16 days ago | Handshake completed | 335 ms |
| 17 days ago | Handshake completed | 327 ms |
| 18 days ago | Handshake completed | 351 ms |
| 19 days ago | Handshake completed | 372 ms |
| 20 days ago | Handshake completed | 342 ms |
| 21 days ago | Handshake completed | 360 ms |
| 22 days ago | Handshake completed | 378 ms |
The last 17 checks. Full history is kept for 30 days; the all-time counter stands at 17 responding of 17.
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 Verifi and makes no claim about it beyond what these checks measured.