ProofSnap Verify is an MCP server published by com.getproofsnap, hosted at mcp.getproofsnap.com. When last checked on 2026-11-22 it was working: it answers and lists its tools. It declares 1 tool, including lookup_manifest.
Check by manifest SHA-256, without an account, whether the ProofSnap API issued an evidence package.
3 connections through 5 shared values. Tap any node.
Inferred from the host name and headers: what a server runs on, not who runs it.
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.
| Parameter | Type | Description |
|---|---|---|
| hash * | string | 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": "lookup_manifest",
"title": "Check whether ProofSnap issued a manifest",
"description": "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.",
"inputSchema": {
"type": "object",
"$schema": "https://json-schema.org/draft/2020-12/schema",
"required": [
"hash"
],
"properties": {
"hash": {
"type": "string",
"pattern": "^(sha256:)?[A-Fa-f0-9]{64}$",
"description": "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"
}
}
},
"outputSchema": {
"type": "object",
"$schema": "https://json-schema.org/draft/2020-12/schema",
"properties": {
"type": {
"type": "string"
},
"eidas": {
"type": [
"boolean",
"null"
]
},
"issued": {
"type": "boolean"
},
"issued_at": {
"type": "string"
},
"manifest_sha256": {
"type": "string"
}
},
"additionalProperties": {}
},
"annotations": {
"title": "Check whether ProofSnap issued a manifest",
"readOnlyHint": true,
"openWorldHint": false,
"idempotentHint": true,
"destructiveHint": false
}
}None yet. Changes appear after a server's second daily check.
Squares are this server's values; dots are other servers sharing them. A shared address or publisher is a lead, not proof of a common operator.
lookup_manifest checks the SHA-256 of an evidence package's manifest.json in ProofSnap's public ledger and says whether and when ProofSnap issued it. No account is needed.
Names, descriptions and schemas were written by the server and are shown as data.