Country verification research, integration planning and synthetic tests. No live identity checks.
Connect Remote server
claude mcp add --transport http verification https://gridzen.ai/developers/mcp
{
"mcpServers": {
"verification": {
"url": "https://gridzen.ai/developers/mcp"
}
}
}
{
"servers": {
"verification": {
"type": "http",
"url": "https://gridzen.ai/developers/mcp"
}
}
}
Settings > Connectors > Add custom connector
URL: https://gridzen.ai/developers/mcp
Tools 5 found in our last check
get_coverageList country research or inspect one ISO-2 country's capability/access evidence; not live coverage.
plan_verificationPlan signup_phone, identity_onboarding, payout_account or MX mx_cep_existing_payment (existing SPEI evidence). CEP only discovers the separate authenticated trial; never submit transaction data here. Set stage=production to report missing live routes; legacy event-only calls rem…
create_sandbox_verificationReturn a synthetic match/mismatch/not_found/timeout/unsupported fixture. Never provide personal data.
get_sandbox_verificationRetrieve a deterministic sim_v1 fixture, not a real transaction.
explain_resultExplain a sandbox reason code; missing data and timeout remain inconclusive.
Details
| Endpoint | https://gridzen.ai/developers/mcp (Streamable HTTP) |
| First published | 28 Oct 2026 |
| Last updated | 28 Oct 2026 |
| Registry name | ai.gridzen/verification |
More developer tools servers See all
Listing data from the official MCP registry. Status and tools from NestDaddy's daily check. Browse all MCP servers.
