ProofSnap Verify
REMOTE · MCP.GETPROOFSNAP.COM
Check without an account whether ProofSnap issued an evidence package.
Available components
Last scanned (9 hours ago)
Scores higher than 62% 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 Security74
- 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. Nothing on it is marked destructive, but we can't show that an anonymous caller can only read: full credit needs the server to list at least one tool and every tool to be verifiably read-only. We use a best-effort check of tool names and descriptions to tell read-only tools from tools that change things, so some genuinely read-only tools may not get full credit. Names that start with a read verb (get, list, read, search and similar) and accurate readOnlyHint annotations help. Meet that to earn full credit, or require authorisation. See how to fix → View diagnostics → Partial
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
- 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
- Tool/resource definitions use about 183 tokens (~183/item across 1 items; 1 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management20
- Stability observed for 6 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 1 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 2 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
Checks we ran (13)
- TLS certificate
- Authorization
- HTTPS
- HSTS header
- DNSSEC
- Transport
- Schema quality
- Stability
- Tool coverage
- Injection markers
- Destructive annotations
- Judged manipulation
- MCP protocol
Does not apply to this hosted endpoint (2)
- Supply Chain SecurityScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
- Provenance & TransparencyScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
The score does not measure everything. What the score does not measure →
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 13 to 17. That category is still filling its 30-day observation window: 4 days of observed history at the previous scan, 5 at this one. The score rises as the window fills, whether or not the server changes.
- 3 Nov 26 0
- Server version: 0.2.0 → 0.3.0 functional
- 1 Nov 26 +1
- Tool “lookup_manifest” rewrote its description, which is the text the model reads security
- Schema quality: 99 → 183 ▼ functional
- Schema quality: good → excellent functional
- “lookup_manifest” reworded the description of “hash” cosmetic
- 31 Oct 26 +1
- Stability: unverified → 0.03 ▲ functional
- 30 Oct 26 71
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.getproofsnap.com/verify/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=mcp.getproofsnap.com | CN=Amazon RSA 2048 M04,O=Amazon,C=US | 26 Oct 2026 | 11 May 2027 | RSA 2048 | SHA256-RSA | 70cd764ad0b811835a4c8190790547c |
| SANs: mcp.getproofsnap.com | ||||||
| CN=Amazon RSA 2048 M04,O=Amazon,C=US (CA) | CN=Amazon Root CA 1,O=Amazon,C=US | 23 Aug 2022 | 23 Aug 2030 | RSA 2048 | SHA256-RSA | 773124f2a952e3ed18a58bdb85d1bc0ce5f27 |
| CN=Amazon Root CA 1,O=Amazon,C=US (CA) | CN=Starfield Services Root Certificate Authority - G2,O=Starfield Technologies\, Inc.,L=Scottsdale,ST=Arizona,C=US | 25 May 2015 | 31 Dec 2037 | RSA 2048 | SHA256-RSA | 67f944a2a27cdf3fac2ae2b01f908eeb9c4c6 |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of mcp.getproofsnap.com. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | Trust anchor | 20326, 38696 | 8, 8 | Verified |
| com. | DS published | 19718 | 13 | Verified |
| getproofsnap.com. | No DS | 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 |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://mcp.getproofsnap.com/verify/mcp | Verified | 200 | |
| http (plaintext) | http://mcp.getproofsnap.com/verify/mcp | HTTPS enforced |
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 →
lookup_manifest Check whether ProofSnap issued a manifest ~145
Looks up the SHA-256 of an evidence package's manifest.json in ProofSnap's public ledger: whether ProofSnap issued exactly this manifest, and when. It covers packages issued by the ProofSnap API and dashboard; packages made with the browser extension are not in this ledger. Returns issued (true or false) and, when issued, issued_at, the package type and eidas (whether the package carries an eIDAS qualified timestamp). Reads public ledger data only; no account is needed.
| Name | Type | Req | Description |
|---|---|---|---|
| hash | string | yes | SHA-256 of the package's manifest.json as 64 hexadecimal characters (a sha256: prefix is accepted), for example the manifest_hash of a capture |
| Name | Type | Req | Description |
|---|---|---|---|
| eidas | boolean|null | – | – |
| issued | boolean | – | – |
| issued_at | string | – | – |
| manifest_sha256 | string | – | – |
| type | string | – | – |
No examples provided.
How do I install the ProofSnap Verify MCP server?
ProofSnap Verify is a hosted endpoint at https://mcp.getproofsnap.com/verify/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.getproofsnap.com
claude mcp add --transport http com-getproofsnap-proofsnap-verify 'https://mcp.getproofsnap.com/verify/mcp'
What is the ProofSnap Verify MCP server?
ProofSnap Verify is an MCP server listed in the public MCP registry as com.getproofsnap/proofsnap-verify. Check without an account whether ProofSnap issued an evidence package. This page covers its hosted endpoint (https://mcp.getproofsnap.com/verify/mcp).
Is the ProofSnap Verify MCP server safe to use?
ProofSnap Verify scores 74 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 ProofSnap Verify MCP server expose?
ProofSnap Verify exposes 1 tool: lookup_manifest. Their descriptions and schemas cost roughly 145 tokens of context every time the server is loaded.
Does the ProofSnap Verify MCP server require authentication?
No. We connected to ProofSnap Verify without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the ProofSnap Verify MCP server still maintained?
ProofSnap Verify 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.
What did VerifyMCP test on the ProofSnap Verify MCP server?
VerifyMCP ran 13 checks on ProofSnap Verify, covering TLS certificate, Authorization, HTTPS, HSTS header and 9 more. Supply Chain Security and Provenance & Transparency do not apply to a hosted endpoint, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.