Gridzen Verification
REMOTE · GRIDZEN.AI
Country verification research, integration planning and synthetic tests. No live identity checks.
Available components
Last scanned (26 minutes ago)
Scores higher than 87% of remote servers
Reachable. Last reached 5 Nov 2026.
Category Security
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. How we score → Why this is hard to score →
Endpoint Security80
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- No authorisation is required to call this server. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one. See how to fix → View diagnostics → Partial
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability68
- AI-judged instruction clarity (good).Pass
- Tool/resource definitions use about 270 tokens (~54/item across 5 items; 5 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management90
- Stability observed for 27 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage71
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 0% of tool parameters carry a description.Fail
- Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 5 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 6 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a current MCP spec version (2026-07-28).Pass
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 5 Nov 26 +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.
- 3 Nov 26 +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.
- 1 Nov 26 +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.
- 30 Oct 26 +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.
- 28 Oct 26 +1
- Server version: 0.6.1 → 0.7.0 functional
- 27 Oct 26 +1
- Authorization: unverified → partial ▲ security
- Injection markers: unverified → pass ▲ security
- TLS certificate: unverified → pass ▲ security
- HSTS header: unverified → pass ▲ security
- Transport: fail → pass ▲ security
- Endpoint reachability: unreachable → reachable ▲ functional
- Tool coverage: unverified → 100 ▲ functional
- MCP protocol: unverified → pass ▲ functional
- Stability: unverified → 0.60 ▲ functional
- 26 Oct 26 0
- Endpoint reachability: reachable → unreachable ▼ security
- Stability: 0.53 → unverified ▼ security
- Authorization: partial → unverified ▼ security
- Tool safety: pass → unverified ▼ security
- TLS certificate: pass → unverified ▼ security
- HSTS header: pass → unverified ▼ security
- Transport: pass → fail ▼ security
- Capabilities: pass → unverified ▼ functional
- Tool coverage: 100 → unverified ▼ functional
- First check of Schema quality: unverified functional
- 23 Oct 26 +1
- Tool “plan_verification” rewrote its description, which is the text the model reads security
- Schema quality: 49 → 54 ▼ functional
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 5 Nov 2026 · Probed https://gridzen.ai/developers/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=gridzen.ai | CN=YE1,O=Let's Encrypt,C=US | 27 Oct 2026 | 25 Jan 2027 | ECDSA 256 | ECDSA-SHA384 | 57ce3349ef343dbd3e9b9debc603ff550bb |
| SANs: gridzen.ai, www.gridzen.ai | ||||||
| CN=YE1,O=Let's Encrypt,C=US (CA) | CN=Root YE,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | ECDSA 384 | ECDSA-SHA384 | 5ddd70dd31f801c85c186a7a04b80afe |
| CN=Root YE,O=ISRG,C=US (CA) | CN=ISRG Root X2,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | ECDSA-SHA384 | 872165fc34b6e5fba8add5b3705fb53a |
| CN=ISRG Root X2,O=Internet Security Research Group,C=US (CA) | CN=ISRG Root X1,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | SHA256-RSA | 6c8f1dc727c7117f7baf853ac980f9cd |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of gridzen.ai. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| ai. | present | 1814, 3799 | 8, 8 | Verified |
| gridzen.ai. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 200 |
| Header | Value |
|---|---|
| strict-transport-security | max-age=31536000; includeSubDomains |
| content-security-policy | default-src 'self'; script-src 'self'; style-src 'self'; img-src 'self' data:; connect-src 'self'; frame-ancestors 'none'; base-uri 'none' |
| x-content-type-options | nosniff |
| referrer-policy | no-referrer |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://gridzen.ai/developers/mcp | Verified | 200 | |
| http (plaintext) | http://gridzen.ai/developers/mcp | HTTPS enforced | 301 | https://gridzen.ai/developers/mcp |
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
create_sandbox_verification ~51
Return a synthetic match/mismatch/not_found/timeout/unsupported fixture. Never provide personal data.
| Name | Type | Req | Description |
|---|---|---|---|
| capability | string | yes | – |
| country | string | yes | – |
| scenario | string | – | – |
Structured output declared, but exposes no named fields.
No examples provided.
explain_result ~30
Explain a sandbox reason code; missing data and timeout remain inconclusive.
| Name | Type | Req | Description |
|---|---|---|---|
| reason_code | string | yes | – |
Structured output declared, but exposes no named fields.
No examples provided.
get_coverage ~37
List country research or inspect one ISO-2 country's capability/access evidence; not live coverage.
| Name | Type | Req | Description |
|---|---|---|---|
| capability | – | – | – |
| country | – | – | – |
Structured output declared, but exposes no named fields.
No examples provided.
get_sandbox_verification ~31
Retrieve a deterministic sim_v1 fixture, not a real transaction.
| Name | Type | Req | Description |
|---|---|---|---|
| identifier | string | yes | – |
Structured output declared, but exposes no named fields.
No examples provided.
plan_verification ~89
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.
| Name | Type | Req | Description |
|---|---|---|---|
| country | string | yes | – |
| event | string | – | – |
| stage | string | – | – |
| task | – | – | – |
Structured output declared, but exposes no named fields.
No examples provided.
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.
remote · gridzen.ai
claude mcp add --transport http ai-gridzen-verification 'https://gridzen.ai/developers/mcp'
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.