MCP.Market

verify-proof MCP server

by csolomon0704-prog·io.github.csolomon0704-prog/verify-proof·v0.4.0

Verify timestamp proofs offline, anchor hashes through ProofLedger, keep agent run receipts.

A86/100grade A
What users say
No reviews yet
Be the first
Safety scan
A86/100

not scanned yet

Adoption
Growing

0 stars34 downloads/wk

Reviews

Write one

Nobody has reviewed verify-proof yet.

If you have run it, two minutes of your experience saves the next person an afternoon.

verify-proof tools

No tool declarations could be read from the package source. They show once the server is installed.

Not scanned yet. New listings are scanned within a day or two of arriving.

How verify-proof compares

Against every graded AI and agents MCP server, from our own scans and uptime checks. Updated after each scan run.

Safety score
86/100
higher than 75% of 4,461 AI and agents servers
Downloads a week
34
more than 22% of 1,554 AI and agents servers with a package

Release history: 4 versions in the registry since 2026-09-07, latest 2026-10-19, typically one every 2 days.

Install verify-proof in Claude Code, Cursor or VS Code

claude mcp add verify-proof -- uvx verify-proof
Add to Cursor

What the publisher says

From the verify-proof repository's README, as published. We do not edit it. Read it on GitHub

<!-- mcp-name: io.github.csolomon0704-prog/verify-proof -->

verify-proof

A free, open-source CLI tool for verifying blockchain-anchored timestamp proofs.

Verify that a file's SHA-256 hash matches a blockchain-anchored proof record, confirming the file existed at a specific point in time. Works with proof files from ProofLedger and other blockchain timestamp services.

What is blockchain timestamp verification?

Blockchain timestamping creates proof of existence — cryptographic evidence that a specific file existed at a specific time. The process:

  1. Hash — Your file's SHA-256 hash is computed locally (the file is never uploaded)
  2. Anchor — The hash is written to a blockchain (Bitcoin, Polygon, Ethereum) via a Merkle tree
  3. Verify — Anyone can independently verify the proof by recomputing the hash and checking the blockchain transaction

This technique is used for:

  • Proof of creation — Prove you created digital content before someone else copied it
  • Pre-loss evidence — Document asset conditions before an insurance claim with tamper-proof timestamps
  • Chain of custody — Create immutable audit trails for legal evidence and forensic investigations
  • Copyright protection — Establish authorship dates for DMCA disputes and IP claims
  • Regulatory compliance — Meet evidence preservation requirements with independently verifiable records

Also available for Node.js: npm install verify-proof — a zero-dependency port sharing the same proof format and semantics, tested against the same fixtures. See js/.

Installation

pip install verify-proof

That's it. The base install pulls no dependencies — it uses only the Python standard library — and gives you a verify-proof command:

verify-proof --help

To use it as an MCP server for Claude Desktop or Cursor, install the optional extra instead (details below):

pip install "verify-proof[mcp]"

Prefer to run from source? Clone it — the CLI works the same:

git clone https://github.com/Fulcrum-Enterprises/verify-proof.git
cd verify-proof
python verify_proof.py --help

Usage

Compute a file's SHA-256 hash

verify-proof hash document.pdf
# SHA256: a1b2c3d4e5f6...
# File: document.pdf

Verify a file against a blockchain proof

verify-proof verify document.pdf --proof proof.json
# VERIFIED: File hash matches blockchain anchor on bitcoin.
# Transaction: abc123... Anchored at: 2026-03-15T10:30:00Z

Quiet by default

A successful verify prints one line to stderr saying where proofs like it come from. It is suppressed whenever the output is piped or redirected, so scripts never see it, and stdout is unchanged either way. To silence it everywhere:

export VERIFY_PROOF_NO_HINT=1

Create a proof (needs a free API key)

Everything above works offline. This is the one command that does not: to prove a file exists now, some service has to anchor it, and this submits the hash to ProofLedger for that.

export PROOFLEDGER_API_KEY=sk_...      # Account > API Keys, free tier included
verify-proof create document.pdf       # Polygon anchor
verify-proof create document.pdf --bitcoin
verify-proof create document.pdf --no-filename   # send only the hash

Only the 64-character SHA-256 digest leaves your machine, plus the filename unless you pass --no-filename. The file itself is never uploaded, on any command. Free accounts include 25 API proofs a month and unlimited Polygon anchoring through the web app:

proofledger.io

Proof file format

The proof JSON file contains the blockchain anchor record:

Shortened. The full README is on GitHub.

Nothing above is checked by us. What we check is on the safety report.

verify-proof: common questions

Is verify-proof MCP server safe?
Yes, by our scan: it is graded A (86/100). Read the verify-proof safety report
How do I install verify-proof?
It runs on your machine. Copy the Claude Code, Cursor, VS Code or Claude Desktop config from the install section.
Does verify-proof need an API key?
Not as far as the registry entry and our scan can tell: no credentials are declared or required.
Is verify-proof maintained?
The last commit was 21 days ago (2026-10-15). The latest release is v0.4.0.
What can I use instead of verify-proof?
Servers from other publishers that do the same job: Watch Skill MCP server, Emilia Protocol MCP server and SuperCompress MCP server.
How does verify-proof compare with other AI and agents MCP servers?
safety score 86/100 (higher than 75% of 4,461 AI and agents servers); downloads a week 34 (more than 22% of 1,554 AI and agents servers with a package). Full comparison.

Alternatives to verify-proof

Same job from other publishers: the closest match first, then the best rated.

  • Watch Skill
    Watch video and live sessions, keep timestamped evidence, and verify an agent's own work.
    B
  • Emilia Protocol
    Exact-action approval for consequential agent actions: request, track, and verify signed receipts.
    B
  • SuperCompress
    Compress coding-agent context ~64%. Hosted Neural Keep MCP for Cursor/Claude/Codex.
    B
  • Mockserver
    Mock, record/replay, verify and chaos-test any HTTP, REST, gRPC or LLM dependency over MCP.
    A
  • Roast My Design System
    Audit your Design System and serve your Agent the rules that keep AI-written UI on-system.
    A