McpStamp Check
REMOTE · MCP.ZOVO.ONE
Score any remote MCP server for Claude, ChatGPT, Gemini and MCP Registry readiness.
Available components
Last scanned (58 minutes ago)
Scores higher than 64% of remote servers
Reachable. Last reached 5 Nov 2026.
Category Developer Tools
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 Usability78
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 343 tokens (~171/item across 2 items; 2 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management10
- Stability observed for 3 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
- 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 2 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 3 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 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.
- 4 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 3 to 7. That category is still filling its 30-day observation window: 1 days of observed history at the previous scan, 2 at this one. The score rises as the window fills, whether or not the server changes.
- 3 Nov 26 0
- Stability: unverified → 0.03 ▲ functional
- 2 Nov 26 74
First indexed and scored.
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://mcp.zovo.one/stamp/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=zovo.one | CN=WE1,O=Google Trust Services,C=US | 31 Oct 2026 | 29 Jan 2027 | ECDSA 256 | ECDSA-SHA256 | 39e1adfa4eb6500e0e3d48868766e3e9 |
| SANs: zovo.one, mcp.zovo.one, *.mcp.zovo.one | ||||||
| CN=WE1,O=Google Trust Services,C=US (CA) | CN=GTS Root R4,O=Google Trust Services LLC,C=US | 13 Dec 2023 | 20 Feb 2029 | ECDSA 256 | ECDSA-SHA384 | 7ff31977972c224a76155d13b6d685e3 |
| CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) | CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE | 15 Nov 2023 | 28 Jan 2028 | ECDSA 384 | SHA256-RSA | 7fe530bf331343bedd821610493d8a1b |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of mcp.zovo.one. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| one. | present | 64939 | 8 | Verified |
| zovo.one. | 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=15552000; includeSubDomains; preload |
| x-content-type-options | nosniff |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://mcp.zovo.one/stamp/mcp | Verified | 200 | |
| http (plaintext) | http://mcp.zovo.one/stamp/mcp | HTTPS enforced | 301 | https://mcp.zovo.one/stamp/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 →
check_mcp_server Check MCP server readiness ~140
Check a public remote MCP server URL (Streamable HTTP) for readiness for the Claude Directory, ChatGPT Apps, Gemini Connected Apps and the MCP Registry. Returns the 0-100 score, A-F grade, readiness per store, every failing or warning check with its fix, the report URL and README badge markdown. Results are cached for 10 minutes; set fresh to true to force a new check.
| Name | Type | Req | Description |
|---|---|---|---|
| fresh | boolean | – | Run a new check even when a result from the last 10 minutes exists. Default false. |
| url | string | yes | The https URL of the MCP endpoint, for example https://example.com/mcp |
| Name | Type | Req | Description |
|---|---|---|---|
| auth | string | – | – |
| badge_markdown | string | yes | – |
| badge_url | string | – | – |
| cached | boolean | – | – |
| checked_at | string | – | – |
| grade | string | yes | – |
| issues | array | yes | – |
| report_url | string | yes | – |
| score | number | yes | – |
| stores | object | yes | – |
| url | string | yes | – |
No examples provided.
explain_check Explain a McpStamp check ~84
Explain one McpStamp Check rule by its id (for example tool_annotations or auth_prm): what it tests, why stores need it, which stores it blocks, its weight and the store or spec documents it comes from. Use it after check_mcp_server to understand a failing check.
| Name | Type | Req | Description |
|---|---|---|---|
| check_id | string | yes | Check id from a check_mcp_server result. |
| Name | Type | Req | Description |
|---|---|---|---|
| blocks | array | – | – |
| counts_for | array | – | – |
| group | string | – | – |
| id | string | yes | – |
| meaning | string | yes | – |
| rule | string | yes | – |
| sources | array | yes | – |
| sources_file | string | – | – |
| title | string | yes | – |
| weight | number | – | – |
No examples provided.
How do I install the McpStamp Check MCP server?
McpStamp Check is a hosted endpoint at https://mcp.zovo.one/stamp/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 · mcp.zovo.one
claude mcp add --transport http theluckystrike-mcpstamp-check 'https://mcp.zovo.one/stamp/mcp'
What is the McpStamp Check MCP server?
McpStamp Check is an MCP server listed in the public MCP registry as io.github.theluckystrike/mcpstamp-check. Score any remote MCP server for Claude, ChatGPT, Gemini and MCP Registry readiness. This page covers its hosted endpoint (https://mcp.zovo.one/stamp/mcp).
Is the McpStamp Check MCP server safe to use?
McpStamp Check scores 75 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 McpStamp Check MCP server expose?
McpStamp Check exposes 2 tools: check_mcp_server, explain_check. Their descriptions and schemas cost roughly 224 tokens of context every time the server is loaded.
Does the McpStamp Check MCP server require authentication?
No. We connected to McpStamp Check without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the McpStamp Check MCP server still maintained?
McpStamp Check 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.