mcpbeat Sign in

Gridzen Verification MCP Server

answering

Gridzen Verification is answering right now. Last checked 14 min ago. It exposes 5 tools. Last commit 10 Oct 2026.

Country verification research, integration planning and synthetic tests. No live identity checks.

Uptime history 68 hours of history
68 hours agonow
100.0%
Uptime 24h
91 of 91 checks
5
Tools
read from the server
665 ms
Response time
average over 24h
0
Stars
last commit 10 Oct 2026

What changed 7

Every tool that appeared, vanished or quietly changed what it asks for. Recorded since 9 October 2026. No other catalogue keeps this.

10 Oct a tool changed version2 times that day
10 Oct a tool description was rewritten plan_verification
10 Oct a tool changed the parameters it asks for plan_verification
9 Oct a tool changed version3 times that day
and 3 more, back to 9 October 2026

Nothing serious here today

Today is the operative word: we check Gridzen Verification every 15 minutes and re-read its code on every release. Watch it and you find out the day that stops being true.

Three servers free · no card

Connect this server

Endpoint below is the one we actually reach during checks — not the one copied from a README. Last verified 14 min ago.

run in your terminal
claude mcp add verification --transport http https://gridzen.ai/developers/mcp
~/Library/Application Support/Claude/claude_desktop_config.json
{
  "mcpServers": {
    "verification": {
      "url": "https://gridzen.ai/developers/mcp"
    }
  }
}
~/.codex/config.toml
[mcp_servers.verification]
url = "https://gridzen.ai/developers/mcp"
.cursor/mcp.json
{
  "mcpServers": {
    "verification": {
      "url": "https://gridzen.ai/developers/mcp"
    }
  }
}
.vscode/mcp.json
{
  "mcpServers": {
    "verification": {
      "url": "https://gridzen.ai/developers/mcp"
    }
  }
}

Available tools 5

Read directly from the server with tools/list, grouped by what they act on. If a tool disappears, we record the date.

sandbox
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.
coverage
get_coverage
List country research or inspect one ISO-2 country's capability/access evidence; not live coverage.
explain
explain_result
Explain a sandbox reason code; missing data and timeout remain inconclusive.
plan
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.

Endpoints

URLTransportStateLatencyChecked
https://gridzen.ai/developers/mcp streamable-http answering 686 ms 14 min ago

Alternatives to Gridzen Verification

same job, measured the same way
Curate-Ipsum
by egoughnour

Code synthesis through belief revision, mutation testing, and verification

190 installs/wk local only
L
Lumaion Continuity
by lumaion

Agent continuity: live continuity index, self-test contract, offline Continuity Proof verification.

3 tools answering
SyntheticUser Lab MCP
by syntheticuserlab

Paid remote MCP for synthetic user testing, UX validation, analytics, checkout, and readiness.

answering
QACAT
by dimawin22

Translation QA: automated checks, AI evaluation, linguistic review, and visual in-context testing.

answering
MobiLoop
by enessubass

Guarded AI mobile Appium testing, security scanning, verification, and fix-retest MCP tools.

local only
Plainradar news search
by plainradar

Live news search: recent stories in 45 languages, grouped by coverage and checked for relevance.

answering
M
Misata Studio: verified synthetic data
by misata

Hosted: plan and build multi-table test and demo data, export 25 formats, with checks shown.

12 tools answering
Sap Adt MCP
by yzonur

Give Claude live access to SAP ABAP via ADT: read, search, check, test, and edit objects.

124 installs/wk local only

Gridzen Verification — questions

Answers built from our own checks of this server.

What can Gridzen Verification do?
It exposes 5 tools, read directly from the server on our last check. Among them: create_sandbox_verification, explain_result, get_coverage, get_sandbox_verification, plan_verification. The full list with descriptions is on this page — we take it from the server itself via tools/list, not from a README. How MCP servers expose tools in the first place →
Is Gridzen Verification working right now?
We send a real MCP handshake every 15 minutes. Over the last 24 hours 91 of 91 checks got a reply (100.0%), average response time 665 ms. The bar chart above shows every period we have measured.
How do I connect Gridzen Verification?
Copy the ready config from this page — we generate it for Claude Code, Claude Desktop, Codex, Cursor and VS Code, each with the file path that client actually reads. It is a remote server, so there is nothing to install — the client connects to the address.
Does Gridzen Verification need an API key?
No. Gridzen Verification completed a full MCP handshake with us as an anonymous client and listed its tools without asking for anything. All 5 of them are readable on this page. This is what we observed, not what the docs claim.
How fast is Gridzen Verification?
It answers our handshake in 665 ms on average, which is faster than 16% of all working MCP servers we measure. That is on the slow side — worth knowing if the tool sits inside an interactive loop. The comparison comes from our own checks across the whole registry, every 15 minutes.
Is Gridzen Verification open source?
Yes — it is published under the MIT licence, written in Python and 0 stars on GitHub. The source link is on this page, so you can read exactly what it does with your data before you connect it.