MCP.Market

stampthisfile MCP server

online · 100% uptime
by stampthisfile·io.github.stampthisfile/mcp·v0.1.0
No reviews yet

Timestamp files in Bitcoin (OpenTimestamps): send a hash, pay per hash with x402, get a proof.

A89/100grade A
Write a reviewRun it
What users say
No reviews yet
Be the first
Safety scan
A89/100

full report

Adoption
Growing

0 stars

Reviews

Write one

Nobody has reviewed stampthisfile yet.

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

stampthisfile tools (4)

write = sends, deletes, buys or posts
  • get_proofFree

    The current .ots proof of one stamp, base64. Once get_stamp says complete, fetch it again: the complete proof carries the Bitcoin attestation and can be verified by anyone, without us. Save it next to the file as <file>.ots. Free.

  • get_stampFree

    Status of one stamp: pending, complete (with the Bitcoin block height and time, and a statement of what it proves) or failed (not confirmed within 7 days). Free.

  • stamp_hashesFree

    Timestamp 1-100 SHA-256 hashes in Bitcoin. Paid per hash with x402: without a payment the tool returns an error whose structuredContent is an x402 PaymentRequired (x402Version 2, exact scheme, USDC on Base). Retry with the same arguments and the signed PaymentPayload in the request's _meta["x402/payment"] (the x402 MCP transport), or, if your client cannot set _meta, in the `payment` argument. The settlement comes back in _meta["x402/payment-response"]. Returns a batch with, per hash, the stamp id, a pending .ots proof (base64: save it now) and its ots_url, plus a receipt signed by us. Invalid input is never charged; retrying with the same payment and arguments returns the same answer without paying twice.

  • verify_proofFree

    Check an OpenTimestamps proof (from us or anyone) against the SHA-256 of a file. Returns valid with status complete (Bitcoin block and the time the file existed by), valid with status pending (not in Bitcoin yet), or invalid with a reason. A pending proof whose calendars have since committed it comes back complete with `upgraded: true` and the completed proof in `ots` (base64): save it in place of the pending one. Nothing is stored. Free.

Public scan report

scanner v0.1.10 · 2026-10-26 · same rubric, same numbers if you re-run it

no findings
  • –Code scanremote-only server, no package to scann/a
  • Live reliabilityremote reachable in 1120ms20/20
  • Tool poisoning4 tool descriptions checked15/15
  • Auth qualityopen endpoint, read-only tools10/15
  • Maintenancelast push 6 days ago15/15
  • Maintainer identityregistry namespace matches repository owner7/10
Overall 89/100. Components that don't apply are left out of the denominator. Any critical finding is an F.RubricAppeal a findingJSON

How stampthisfile compares

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

Safety score
89/100
higher than 80% of 48,255 servers
Tools
4
the typical server has 7
Tools that change things
0%
typical: 0%. Fewer write tools means less an agent can break
Uptime
100%
of our recent checks; the typical remote server answers 100%
Response time
176 ms
faster than 68% of 30,031 servers

What its tools let an agent do: 4 read

Install stampthisfile in Claude Code, Cursor or VS Code

claude mcp add --transport http mcp https://stampthisfile.com/mcp
Add to Cursor

What the publisher says

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

stampthisfile MCP server

A hosted MCP server that lets AI agents timestamp files in Bitcoin with stampthisfile: send the SHA-256 hash of a file (never the file), pay per hash in USDC with x402, and get a standard OpenTimestamps .ots proof that anyone can verify without us. No account or API key.

  • Endpoint: https://stampthisfile.com/mcp (Streamable HTTP, stateless)
  • Auth: none. Stamping is paid per call with x402; everything else is free.

There is nothing to install or run: this repository describes the hosted server. The server itself is not open source.

Connect

Claude Code:

claude mcp add --transport http stampthisfile https://stampthisfile.com/mcp

Cursor, VS Code and other clients (.mcp.json style):

{
  "mcpServers": {
    "stampthisfile": {
      "type": "http",
      "url": "https://stampthisfile.com/mcp"
    }
  }
}

Tools

A proof is pending at first and completes once Bitcoin confirms it, usually within 1-6 hours. A complete proof shows the file existed no later than the time of its Bitcoin block. It is not a signature and does not show who made the file: read stampthisfile.com/evidence.md before stamping something meant as evidence.

Pricing

Stamping costs a fixed price per hash, in USDC on Base, paid with x402 using the MCP transport: without a payment, stamphashes returns a tool error whose structuredContent is the x402 PaymentRequired. Retry with the signed PaymentPayload in meta["x402/payment"], or in the payment argument if your client cannot set meta. The settlement comes back in meta["x402/payment-response"]. Invalid input is never charged. Reading, downloading and verifying proofs are free.

More

(npx skills add stampthisfile/skills)

  • stampthisfile.com/llms.txt: the API for agents
  • stampthisfile.com/openapi.json: REST API
  • stampthisfile/skills: the same, as agent skills

License

MIT, for the contents of this repository.

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

stampthisfile: common questions

Is stampthisfile MCP server safe?
Yes, by our scan: it is graded A (89/100). Read the stampthisfile safety report
How do I install stampthisfile?
It runs remotely at stampthisfile.com. Add it to Claude Code, Cursor, VS Code or Claude Desktop with the snippets above, or call it through the mcp.market gateway without installing anything.
Does stampthisfile need an API key?
Not as far as the registry entry and our scan can tell: no credentials are declared or required.
Is stampthisfile maintained?
The last commit was 14 days ago (2026-10-20). The latest release is v0.1.0.
Is stampthisfile up?
100% of our last 28 checks got an answer. We check remote servers about four times a day.
How does stampthisfile compare with other MCP servers?
safety score 89/100 (higher than 80% of 48,255 servers); tools 4 (the typical server has 7); tools that change things 0% (typical: 0%. Fewer write tools means less an agent can break). Full comparison.