Gridzen Verification

ai.gridzenv0.2.0Updated Oct 8, 2026

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

VerifiedStreamable HTTPWeb executableDeveloper ToolsSecurity & Monitoring

Overview

AI-generated overview

Lets an assistant research country verification coverage, plan verification flows, and run synthetic sandbox tests with no live identity checks.

What it does
Gridzen Verification exposes five tools: get_coverage, plan_verification, create_sandbox_verification, get_sandbox_verification, and explain_result. They work against a bundled offline research catalog covering 198 countries and territories plus synthetic fixtures, so an assistant can look up which verification capabilities exist per country, draft an integration plan for an event such as a payout, and run simulated outcomes like timeout or not_found. The tools are described as read-only and idempotent, and no live provider is enabled.
When to use it
Useful when you are scoping or designing identity-verification integrations and want country coverage research, an integration plan, or synthetic test outcomes before wiring up a real provider. It is not for verifying real people or authorizing real payments.
Requirements
A remote Streamable HTTP endpoint at the provider's developers path needs no account or API key. The local option is a Python 3.11+ stdio server installed from a GitHub release or website download (no PyPI package yet); the CLI and MCP use the bundled offline catalog, while the HTTP client and example call the public sandbox. Remote use is rate limited to 120 requests per minute per client address and 600 per minute overall.
Before you install
No live provider is enabled and no real person is verified; a synthetic match cannot authorize real users or payments, and simulation IDs are fixtures, not unique transaction identifiers. Never send identity numbers, bank accounts, documents, or credentials to the sandbox. Remote usage sends the documented arguments to the provider, while local stdio stays offline. Research evidence is distinct from commercial permission to use a provider.

Installation

In SourceWeft

  1. Open Gridzen Verification in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.

Other MCP clients

Add this to your client's mcpServers config.

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

README

Gridzen Developer Kit 0.2.0

Research for 198 countries/territories, a verification integration planner, five synthetic outcomes, an HTTP SDK, local MCP server and three Skills. No live provider is enabled. No real person is verified. The research snapshot is dated 2026-10-07, with source links and file hashes.

中文指南 · Guía en español

Try it

Public playground: https://gridzen.ai/developers/

Download gridzen-developer-kit.zip, extract it, then:

sh
python3 -m venv .venv. .venv/bin/activatepython -m pip install './gridzen-developer-kit[mcp]'gridzen coverage --country ID --capability bank_account_matchgridzen plan --country ID --event payoutgridzen simulate --country ID --capability bank_account_match --scenario timeoutpython gridzen-developer-kit/examples/payout.py

Python 3.11+. CLI and MCP use the bundled offline catalog and fixtures; the Python HTTP client/example calls the public sandbox. Dependencies are downloaded only during installation. API reference: https://gridzen.ai/developers/api/openapi.json .

MCP

Register a local stdio server in your MCP client. Use the absolute path to the installed executable; configuration syntax varies by client. A conventional mcpServers configuration is:

json
{"mcpServers":{"gridzen":{"command":"/absolute/path/to/.venv/bin/gridzen-mcp","args":[]}}}

Tools: get_coverage, plan_verification, create_sandbox_verification, get_sandbox_verification, explain_result. All operate on local research or synthetic fixtures, with read-only/idempotent annotations. Public research/sandbox MCP endpoint: https://gridzen.ai/developers/mcp (Streamable HTTP, no account or API key). It has the same five tools and zero live providers. Remote usage sends the documented arguments to Gridzen; local stdio remains offline. Limits: 120 requests/minute per client address and 600/minute overall, returning HTTP 429 with Retry-After.

Skills

Copy the individual directories from skills/ into your compatible agent's project or user skill directory. Each entrypoint is SKILL.md; preserve its references/ directory. No marketplace listing or automatic registration is implied.

HTTP SDK

python
from gridzen_developer.client import Gridzenclient = Gridzen()plan = client.plan('ID', 'payout')result = client.simulate('ID', 'bank_account_match', 'not_found')assert result['status'] == 'inconclusive'assert result['verified'] is False

Only documented country/event/capability/scenario fields are accepted. Never send identity numbers, bank accounts, documents or credentials to the sandbox. Simulation IDs encode fixtures and are not unique transaction identifiers. A synthetic match cannot authorize real users or payments. Research evidence is distinct from Gridzen availability or commercial permission.

Repository checkout: local service and checks

sh
python -m pip install '.[test,server]'python -m pytest -qpython scripts/check_mcp.pyuvicorn gridzen_developer.server:app --host 127.0.0.1 --port 8030

Production uses an independent container at localhost:8030 proxied only under /developers/. See deploy/compose.yml and deploy/developers.conf. Removing that proxy file and stopping this container rolls back the preview; the existing API and Agent Company stacks are separate.

Repository checkout: build distributions

python scripts/build_downloads.py creates allowlisted developer-kit and Skills ZIPs; it excludes tests, deployment files, private credentials and itself from recursive download packaging. python scripts/build_catalog.py <repo>/docs/research/identity-verification/2026-10-07 refreshes the public research projection. Main repository report files remain the provenance source.

Public distribution

Source: https://github.com/immurray/gridzen-developer-kit . Install the Skills:

sh
npx skills add immurray/gridzen-developer-kit

Install the tagged Python/MCP release from GitHub (Python 3.11+ and Git):

sh
python -m pip install "gridzen-developer-kit[mcp] @ git+https://github.com/immurray/[email protected]"

A PyPI package is not published yet. Use the GitHub release or website download until the release tracker records a verified PyPI URL.

Remote client configuration (conventional JSON; client syntax may vary):

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

For Claude Code: claude mcp add --transport http gridzen https://gridzen.ai/developers/mcp. For Cursor: add the remote URL in its MCP settings. For portable Agent Plugins, use the packaged plugin.json and mcp.json; the portable transport identifier is streamable-http. Marketplace admission is separate from compatibility.

Original code and Skills: MIT. Research provenance and third-party rights: NOTICE.md. Support: [email protected] .

Marketplace availability

Source, release downloads, the official MCP Registry entry and three Skills.sh pages are public. Docker catalog submission is awaiting review. See the publication ledger for exact status and remaining platform steps.

Source: README.md at commit f5dd9aa

Tools

0
Tool metadata has not been indexed yet.

Version history

1
  1. v0.2.0LatestOct 8, 2026