# Gridzen Verification (remote · gridzen.ai)

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

- Trust score: 83/100 (high trust)
- Change this week: +4
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-05

## Components

- remote · `gridzen.ai`: 83/100 (this document), [markdown](https://verifymcp.io/servers/ai-gridzen-verification/developers-mcp.md), [page](https://verifymcp.io/servers/ai-gridzen-verification/developers-mcp)

## Channel facts

- Endpoint: `https://gridzen.ai/developers/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `0.7.0`

## Trust breakdown

How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-11-05.

- **Endpoint Security**: 80/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - No authorisation is required to call this server. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one.
  - HTTPS is enforced; there's no plaintext access path.
  - The HSTS (Strict-Transport-Security) header is present.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 68/100
  - AI-judged instruction clarity (good).
  - Tool/resource definitions use about 270 tokens (~54/item across 5 items; 5 tools + 0 resources), lean.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 90/100
  - Stability observed for 27 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 71/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 0% of tool parameters carry a description.
  - Structured output schemas are declared (100% of tools); any adoption earns full credit.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 5 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 6 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a current MCP spec version (2026-07-28).

## Install

### How do I install the Gridzen Verification MCP server?

Gridzen Verification is a hosted endpoint at https://gridzen.ai/developers/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

### Claude

```bash
claude mcp add --transport http ai-gridzen-verification 'https://gridzen.ai/developers/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "ai-gridzen-verification": {
      "url": "https://gridzen.ai/developers/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "ai-gridzen-verification": {
      "type": "http",
      "url": "https://gridzen.ai/developers/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.ai-gridzen-verification]
url = "https://gridzen.ai/developers/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "ai-gridzen-verification": {
      "type": "remote",
      "url": "https://gridzen.ai/developers/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add ai-gridzen-verification --url 'https://gridzen.ai/developers/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  ai-gridzen-verification:
    url: "https://gridzen.ai/developers/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "ai-gridzen-verification": {
      "Transport": "http",
      "Url": "https://gridzen.ai/developers/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add ai-gridzen-verification -t streamable-http -u 'https://gridzen.ai/developers/mcp'
```

### Other

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

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-11-05 (score 83, +1)

No change was recorded against any check on this day. Stability & Change Management went from 87 to 90. That category is still filling its 30-day observation window: 26 days of observed history at the previous scan, 27 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-11-03 (score 82, +1)

No change was recorded against any check on this day. Stability & Change Management went from 80 to 83. That category is still filling its 30-day observation window: 24 days of observed history at the previous scan, 25 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-11-01 (score 81, +1)

No change was recorded against any check on this day. Stability & Change Management went from 73 to 77. That category is still filling its 30-day observation window: 22 days of observed history at the previous scan, 23 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-10-30 (score 80, +1)

No change was recorded against any check on this day. Stability & Change Management went from 67 to 70. That category is still filling its 30-day observation window: 20 days of observed history at the previous scan, 21 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-10-28 (score 79, +1)

- [functional] Server version: 0.6.1 → 0.7.0

### 2026-10-27 (score 78, +1)

- [security improvement] Authorization: unverified → partial
- [security improvement] Injection markers: unverified → pass
- [security improvement] TLS certificate: unverified → pass
- [security improvement] HSTS header: unverified → pass
- [security improvement] Transport: fail → pass
- [functional improvement] Endpoint reachability: unreachable → reachable
- [functional improvement] Tool coverage: unverified → 100
- [functional improvement] MCP protocol: unverified → pass
- [functional improvement] Stability: unverified → 0.60

### 2026-10-26 (score 77, 0)

- [security regression] Endpoint reachability: reachable → unreachable
- [security regression] Stability: 0.53 → unverified
- [security regression] Authorization: partial → unverified
- [security regression] Tool safety: pass → unverified
- [security regression] TLS certificate: pass → unverified
- [security regression] HSTS header: pass → unverified
- [security regression] Transport: pass → fail
- [functional regression] Capabilities: pass → unverified
- [functional regression] Tool coverage: 100 → unverified
- [functional] First check of Schema quality: unverified

### 2026-10-23 (score 77, +1)

- [security] Tool “plan_verification” rewrote its description, which is the text the model reads
- [functional regression] Schema quality: 49 → 54

## MCP tools (5)

### `get_coverage` (~37 tokens)

List country research or inspect one ISO-2 country's capability/access evidence; not live coverage.

Input parameters:

- `capability`
- `country`

### `plan_verification` (~89 tokens)

Plan 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 remain supported.

Input parameters:

- `country` (string, required)
- `event` (string)
- `stage` (string)
- `task`

### `create_sandbox_verification` (~51 tokens)

Return a synthetic match/mismatch/not_found/timeout/unsupported fixture. Never provide personal data.

Input parameters:

- `capability` (string, required)
- `country` (string, required)
- `scenario` (string)

### `get_sandbox_verification` (~31 tokens)

Retrieve a deterministic sim_v1 fixture, not a real transaction.

Input parameters:

- `identifier` (string, required)

### `explain_result` (~30 tokens)

Explain a sandbox reason code; missing data and timeout remain inconclusive.

Input parameters:

- `reason_code` (string, required)

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/ai-gridzen-verification/developers-mcp#diagnostics

## Score history

- 2026-11-05: 83
- 2026-11-04: 82
- 2026-11-03: 82
- 2026-11-02: 81
- 2026-11-01: 81
- 2026-10-31: 80
- 2026-10-30: 80
- 2026-10-29: 79
- 2026-10-28: 79
- 2026-10-27: 78
- 2026-10-26: 77
- 2026-10-25: 77
- 2026-10-24: 77
- 2026-10-23: 77
- 2026-10-22: 76
- 2026-10-21: 75
- 2026-10-20: 75
- 2026-10-19: 74
- 2026-10-18: 74
- 2026-10-17: 74
- 2026-10-16: 73
- 2026-10-15: 73
- 2026-10-14: 72
- 2026-10-13: 72
- 2026-10-12: 71
- 2026-10-11: 71

## Common questions

### What is the Gridzen Verification MCP server?

Gridzen Verification is an MCP server listed in the public MCP registry as ai.gridzen/verification. Country verification research, integration planning and synthetic tests. No live identity checks. This page covers its hosted endpoint (https://gridzen.ai/developers/mcp).

### Is the Gridzen Verification MCP server safe to use?

Gridzen Verification scores 83 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

### What tools does the Gridzen Verification MCP server expose?

Gridzen Verification exposes 5 tools: get_coverage, plan_verification, create_sandbox_verification, get_sandbox_verification, explain_result. Their descriptions and schemas cost roughly 238 tokens of context every time the server is loaded.

### Does the Gridzen Verification MCP server require authentication?

No. We connected to Gridzen Verification without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

### Is the Gridzen Verification MCP server still maintained?

Gridzen Verification is still listed as active in the MCP registry. We last reached this channel on 5 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

## Links

- Remote endpoint: https://gridzen.ai/developers/mcp
- Repository: https://github.com/immurray/gridzen-developer-kit
- Website: https://gridzen.ai/developers/
- Changelog RSS feed: https://verifymcp.io/servers/ai-gridzen-verification/developers-mcp.xml
- Changelog JSON feed: https://verifymcp.io/servers/ai-gridzen-verification/developers-mcp.json
- HTML version of this page: https://verifymcp.io/servers/ai-gridzen-verification/developers-mcp