Skip to content

ProofSnap Verify MCP server

com.getproofsnap/proofsnap-verifygetproofsnap.comstreamable-httpv1.0.1Scanned

Check by manifest SHA-256, without an account, whether the ProofSnap API issued an evidence package.

1 tool: 1 only read.

Tools: 0 delete, 0 irreversible, 0 write, 1 read.
  • Reads private data · 0
  • Reads text others write · 0
  • Can send data out · 0
  • No findings

Tools listed without sign-in. Remote posture

With Anlyon

Decide which of this server's tools your agent can use.

  • Anlyon lists the tools and adopts none.
  • Each tool you adopt gets approvals and receipts.
  • Your agent never holds the key.
Govern this server →

A tool your agent calls directly is not routed through Anlyon and is not governed by it. Anlyon Radar only lists and labels, and these labels are the same either way.

What the ProofSnap Verify MCP server can do

The ProofSnap Verify MCP server is published by getproofsnap.com, a domain the MCP Registry verified. It has 1 tool. Every one of them only reads: going by their definitions, none of them creates, changes, sends or deletes anything.

None of its tools reads private data, brings in text other people write, or sends data out.

None of the fixed checks matched anything in its tool definitions. That is not a safety guarantee.

Its remote endpoint lists its tools without sign-in, and its tools changed once since Anlyon Radar first saw them.

Last scanned Nov 20, 2026, version 1.0.1.

Tools

Grouped by what each tool does, most consequential first. Open one for its reasons and full description; descriptions are the publisher's own words.

1 tool

Only reads 1Show 1 read-only tool
  • 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.No findings

    Why it is in this group

    • The name "lookup_manifest" says "lookup": a word for reading.
    Description, as the server wrote 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.

    Annotations the server declares

    • title: Check whether ProofSnap issued a manifest
    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false

This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.

Exfil surface

Which tools read private data, which read text someone else can write, and which can send data out. One of each is a path a prompt injection can use.

No private-data, untrusted-input, outbound path in this server alone: no tool is tagged private-data or untrusted-input or outbound.

Reads private data0
Reads files, mail, messages, databases, secrets, calendars or repositories.
Reads text others write0
Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
Can send data out0
Can carry data to people or systems: it sends, posts or publishes, or takes a recipient, channel or URL.

Other servers in the same agent add their own tools to these paths. Audit your whole setup to see them together.

Remote posture

What anyone on the internet sees at the remote endpoint: an anonymous initialize and tools/list, and the public OAuth metadata.

Tools listed without sign-in

Looked at Nov 21, 2026, 19:23 UTC, unchanged since Oct 30, 2026. No credentials were sent and no tool was called. What is looked at.

Reachable
yes
HTTP status of an anonymous initialize
200
tools/list served without credentials
yes
Tools that change things, listed without credentials
0
Protocol version
2025-06-18
WWW-Authenticate on 401
not observed
resource_metadata in WWW-Authenticate
not observed
RFC 9728 protected resource metadata
https://mcp.getproofsnap.com/.well-known/oauth-protected-resource/verify/mcp
Authorization servers
https://mcp.getproofsnap.com
Legacy HTTP+SSE transport
no
Dynamic client registration
yes
Client ID metadata documents
yes

Findings

Matches of fixed checks, with the text they matched.

No check matched anything in these tool definitions. That is not a safety guarantee.

History

Changes to its tool definitions and to its remote endpoint, newest first.

  1. Tools1 changed.~1 changedView diff

Install

Pinned to version 1.0.1. Values in angle brackets are yours to fill in.

claude mcp add --transport http proofsnap-verify https://mcp.getproofsnap.com/verify/mcp
claude mcp add --transport http proofsnap-verify https://mcp.getproofsnap.com/verify/mcp

Run in a terminal.

Claude Code permissions

Allow the reads, ask before a change or a way out, deny the deletes. Paste into .claude/settings.json.

.claude/settings.json
{
  "permissions": {
    "allow": [
      "mcp__proofsnap-verify__lookup_manifest"
    ],
    "ask": [],
    "deny": []
  }
}

Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. A read that can send data out (it takes a URL, say) asks first too. It assumes the server is installed as proofsnap-verify. Review it before you use it.

Pin

Keep the decision: fail CI when the tools change, follow every change, or show a badge.

Pin in CI

Fail a build when the tools you reviewed are not the tools the server serves today.

curl -s "https://radar.anlyon.com/api/v1/servers/com.getproofsnap/proofsnap-verify/verify?hash=4fb78051f1a0c9aaaa809a8f6f6d79a1979ca5e3f8f53c05fb2266d02f61a9c3" | jq -e '.changed == false'

Pinned hash 4fb78051f1a0, from Nov 20, 2026, 12:17 UTC.

Watch

Get told when its tools change: a new tool, a new description, a new class.

https://radar.anlyon.com/servers/com.getproofsnap/proofsnap-verify/changes.xml

An Atom feed. Works in any feed reader or Slack's RSS app.

Badge

Anlyon Radar badge for com.getproofsnap/proofsnap-verify
[![Anlyon Radar](https://radar.anlyon.com/badge/com.getproofsnap/proofsnap-verify.svg)](https://radar.anlyon.com/servers/com.getproofsnap/proofsnap-verify)

Source: MCP Registry · repository. Synced Nov 6, 2026, 11:17 UTC.

ProofSnap Verify MCP server: questions and answers

Answered from the scan above, not from the publisher's description.

Is the ProofSnap Verify MCP server safe?

No scan can promise that. What its definitions show: 1 tool, all of which only read, and 0 findings from fixed checks. Read-only tools can still pass private data to a model.

Can the ProofSnap Verify MCP server delete data?

No tool is classed as destructive: going by their definitions, none of them deletes, cancels or revokes anything.

Can the ProofSnap Verify MCP server do things that cannot be undone?

No tool is classed as irreversible: none of them sends, pays, publishes or merges, going by their definitions.

What tools does the ProofSnap Verify MCP server have?

1 tool: 1 read. lookup_manifest.

Does the ProofSnap Verify MCP server need sign-in or OAuth?

Its remote endpoint listed its tools to an anonymous client, without sign-in.

Does the ProofSnap Verify MCP server send data to outside services?

None of its tools sends, posts or publishes, or takes a recipient, channel or URL.

Has the ProofSnap Verify MCP server changed its tools?

Yes, once since Anlyon Radar started tracking it, most recently on Nov 6, 2026. Every change is on this page and in its Atom feed.