GridZen MCP server

Which servers in the official MCP registry are GridZen's own, whether they answer, and what they offer. A program checked each of these, nobody copied them from a product page.

read 2026-10-13

← Back to GridZen

Whose server it is

Registry nameai.gridzen/verificationverified in the MCP registry

The registry name sits under gridzen.ai. The registry only lets a publisher use that namespace after proving control of the domain through DNS or HTTP.

When we asked itchecked 2026-10-13

Stateanswerschecked 2026-10-13
Tools5
Server calls itselfGridzen Developer Kit
Server version0.6.1
Protocol version2025-06-18

On 2026-10-13 the server answered initialize and tools/list without a sign-in. First answer in 12 ms.

Tools it offers5 tools · read 2026-10-13

get_coverage
List country research or inspect one ISO-2 country's capability/access evidence; not live coverage.
plan_verification
Plan a specific signup_phone, identity_onboarding or payout_account task. Set stage=production to report missing live routes; legacy event-only calls remain supported.
create_sandbox_verification
Return a synthetic match/mismatch/not_found/timeout/unsupported fixture. Never provide personal data.
get_sandbox_verification
Retrieve a deterministic sim_v1 fixture, not a real transaction.
explain_result
Explain a sandbox reason code; missing data and timeout remain inconclusive.

How to connect

Add the server to your MCP client config. Claude Desktop, Cursor and most other clients read this shape:

{
  "mcpServers": {
    "verification": {
      "type": "http",
      "url": "https://gridzen.ai/developers/mcp"
    }
  }
}

OpenAPI spec

3 paths, read 2026-10-13. Open the spec ↗

Each line is something a program found when it went looking: the registry entry, the server's own answer, a spec that parses. A missing line means we did not find it, not that it does not exist.