ProofSnap MCP

A remote MCP server operated by ProofSnap that allows AI assistants to preserve web pages as signed evidence, verify captures, watch pages for changes, and compare captures. It supports OAuth sign-in or API key authentication and provides tools for compliance and brand protection.

Endpoint and access

No sign-in to connect and list tools. Individual tools may still need a vendor account, credentials, or permissions; check the documented prerequisites.

Vendor evidenceStreamable HTTPNo sign-inEndpoint checked 2026-11-01Operated by ProofSnap

You need:You need a ProofSnap account with a confirmed email address.Create a free account

MCP endpoint (Streamable HTTP)

https://mcp.getproofsnap.com/verify/mcp

Vendor documentation

What you can do with it

Preserve a page as signed evidence
Verify captures and check signatures
Watch pages for changes on a schedule
Compare two captures for changes

Source and maintenance

Vendor evidenceRegistry 1.0.0

mcp-registry: com.getproofsnap/proofsnap-verify@1.0.0 Project website

Protocol and capabilities

Server: proofsnap-verify 0.2.0
MCP protocol: 2025-06-18
Tools: 1 advertised
Resources: Not advertised
Resource templates: Not advertised
Prompts: Not advertised

Server-advertised capabilities

{
  "tools": {
    "listChanged": false
  }
}

Server-provided instructions

Untrusted server output shown for inspection. It is not Koskamo guidance and is excluded from knowledge search.

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.

Tools

1 advertised

lookup_manifest — Check whether ProofSnap issued a manifest

Advertised by the server during the last successful anonymous check.

Advertised read-only

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.

lookup_manifest input schema

{
  "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"
    }
  }
}

lookup_manifest output schema

{
  "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": {}
}

lookup_manifest annotations

{
  "title": "Check whether ProofSnap issued a manifest",
  "readOnlyHint": true,
  "openWorldHint": false,
  "idempotentHint": true,
  "destructiveHint": false
}

Prompts

Not advertised

No prompt definitions available.

Resources

Not advertised

No resource definitions available.

30-day availability

Aggregated from read-only remote checks; this is not a tool-execution or security guarantee.

Successful checks: 1 of 1 (100%)
Average latency: 530 ms
95th percentile latency: 530 ms

Maintenance history

Public check and source-refresh events. Editorial and ownership records remain private.

Nov 1, 2026, 8:11 AM UTC · probe · passed · 530 ms · metadata changed · 1 tool(s)

Connect from your client

Each snippet registers the same endpoint; pick the client you use.

This server is operated by the named third party. Listing and endpoint checks are not an endorsement or a security audit. Review the operator's permissions, terms, and data handling before connecting. How listings are checked and corrected.

Claude Code

Run this once in a terminal. It registers the remote server. Use --scope project to write .mcp.json for the repo.

Claude Code configuration

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

Codex

Run this once. Codex stores MCP servers in ~/.codex/config.toml (or .codex/config.toml in a trusted project).

Codex configuration

codex mcp add proofsnap-mcp --url https://mcp.getproofsnap.com/verify/mcp

Cursor

Merge this server into .cursor/mcp.json in your project, then enable proofsnap-mcp in your MCP settings.

Cursor configuration

{
  "mcpServers": {
    "proofsnap-mcp": {
      "url": "https://mcp.getproofsnap.com/verify/mcp"
    }
  }
}

Cline

Merge this into cline_mcp_settings.json (Cline → MCP Servers → Configure).

Cline configuration

{
  "mcpServers": {
    "proofsnap-mcp": {
      "type": "streamableHttp",
      "url": "https://mcp.getproofsnap.com/verify/mcp",
      "disabled": false
    }
  }
}

VS Code

Merge this server into .vscode/mcp.json. Use MCP: List Servers to start proofsnap-mcp and inspect its tools.

VS Code configuration

{
  "servers": {
    "proofsnap-mcp": {
      "type": "http",
      "url": "https://mcp.getproofsnap.com/verify/mcp"
    }
  }
}

Gemini CLI

Run this once. It writes .gemini/settings.json in the current project; pass --scope user for ~/.gemini/settings.json.

Gemini CLI configuration

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

Claude Desktop

Merge this into claude_desktop_config.json (macOS: ~/Library/Application Support/Claude/, Windows: %APPDATA%\Claude\), then restart Claude Desktop.

Claude Desktop configuration

{
  "mcpServers": {
    "proofsnap-mcp": {
      "url": "https://mcp.getproofsnap.com/verify/mcp"
    }
  }
}

Windsurf

Merge this into ~/.codeium/windsurf/mcp_config.json, then refresh MCP in Cascade. Windsurf remote servers use serverUrl, not url.

Windsurf configuration

{
  "mcpServers": {
    "proofsnap-mcp": {
      "serverUrl": "https://mcp.getproofsnap.com/verify/mcp"
    }
  }
}

Let your agent find its tools

Find servers like ProofSnap MCP from your agent. Add Koskamo once to search the index for endpoints, access requirements, and client setup. Public discovery needs no key.

Connect Koskamo Explore workflows

See all 4,075

Do you run ProofSnap MCP?

Prove ownership with a DNS record, a well-known file, or your Official MCP Registry entry, and your edits publish immediately. Proofs are re-checked weekly; admins can still hide or remove a listing.

Claim this listing