Remote MCP · Endpoint

Gridzen Verification MCP server

No. Gridzen Verification answered an MCP handshake 2 hours ago.

UpLast checked 2 hours ago

Server URL

https://gridzen.ai/developers/mcp

The last check completed an MCP handshake.

Registry name
ai.gridzen/verification
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
220 ms
Tools exposed
5 tools
Uptime, last 30 days
100% from 15 checks
Described by its publisher as
Country verification research, integration planning and synthetic tests. No live identity checks.
Listing
From the official MCP registry (active).
Recent checks of Gridzen Verification
CheckedResultHandshake
2 hours agoHandshake completed220 ms
1 day agoHandshake completed216 ms
2 days agoHandshake completed369 ms
2 days agoHandshake completed223 ms
4 days agoHandshake completed228 ms
7 days agoHandshake completed232 ms
9 days agoHandshake completed338 ms
12 days agoHandshake completed252 ms
14 days agoHandshake completed219 ms
16 days agoHandshake completed215 ms
18 days agoHandshake completed216 ms
20 days agoHandshake completed498 ms
22 days agoHandshake completed205 ms
24 days agoHandshake completed214 ms
25 days agoHandshake completed324 ms

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

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