Check by manifest SHA-256, without an account, whether the ProofSnap API issued an evidence package.
Connect Remote server
claude mcp add --transport http proofsnap-verify https://mcp.getproofsnap.com/verify/mcp
{
"mcpServers": {
"proofsnap-verify": {
"url": "https://mcp.getproofsnap.com/verify/mcp"
}
}
}
{
"servers": {
"proofsnap-verify": {
"type": "http",
"url": "https://mcp.getproofsnap.com/verify/mcp"
}
}
}
Settings > Connectors > Add custom connector
URL: https://mcp.getproofsnap.com/verify/mcp
Tools 1 found in our last check
lookup_manifestLooks 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. Retu…
Details
| Endpoint | https://mcp.getproofsnap.com/verify/mcp (Streamable HTTP) |
| First published | 6 Nov 2026 |
| Last updated | 6 Nov 2026 |
| Registry name | com.getproofsnap/proofsnap-verify |
More other servers See all
Listing data from the official MCP registry. Status and tools from NestDaddy's daily check. Browse all MCP servers.
