stampthisfile

io.github.stampthisfilePublished by GitHub account stampthisfilev0.1.0Updated Nov 4, 2026

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

VerifiedStreamable HTTPWeb executableFinanceSecurity & Monitoring

Overview

AI-generated overview

Hosted MCP server that timestamps file SHA-256 hashes in Bitcoin via OpenTimestamps, paying per hash in USDC with x402.

What you can do
  • Submit 1-100 SHA-256 hashes for Bitcoin timestamping, paid per hash with x402
  • Check a stamp's status: pending, complete with Bitcoin block height and time, or failed
  • Download the current .ots proof as base64, refetching once complete for the Bitcoin attestation
  • Verify any OpenTimestamps proof, from this service or elsewhere, against a file's SHA-256
When to use it
Useful when an assistant needs to prove that a file existed no later than a certain time, for example to timestamp documents, deliverables or records, and to check or verify OpenTimestamps proofs without a local tool.
Requirements
A remote Streamable HTTP endpoint; nothing to install. No account or API key. Stamping requires payment in USDC on Base through x402, with the signed payment payload sent in the request metadata or a payment argument. Network access to the hosted service.
Before you install
Stamping spends real money: each hash is charged in USDC on Base via x402, so confirm the price and payment flow before calling stamp_hashes. Only hashes are sent, not file contents. A proof shows the file existed by a Bitcoin block time but is not a signature and does not show who made the file.

Installation

In SourceWeft

  1. Open stampthisfile in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.

Use with an agent

Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.

Read https://sourceweft.com/mcp/io.github.stampthisfile%2Fmcp/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config.

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

README

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:

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

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

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

Tools

ToolWhat it does
stamp_hashesTimestamp 1-100 SHA-256 hashes in Bitcoin. Paid per hash with x402; returns a pending .ots proof per hash and a signed receipt
get_stampA stamp's status: pending, complete (with the Bitcoin block and time) or failed
get_proofThe current .ots proof, base64. Fetch it again once complete to get the Bitcoin attestation
verify_proofCheck any OpenTimestamps proof against a file's SHA-256

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, stamp_hashes 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

License

MIT, for the contents of this repository.

Source: README.md at commit 2a07eb9

Tools

4

stamp_hashes

Stamp hashes

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.

Parametershashesrequiredpaymentwebhook

get_stamp

Get stamp

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.

Parametersidrequired

get_proof

Get proof

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.

Parametersidrequired

verify_proof

Verify proof

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.

Parametersotsrequiredhashrequired

Version history

1
  1. v0.1.0LatestOct 20, 2026

Score

100% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 daysRequired25 pts
  • Auth declaredRequired10 pts
  • Tools listedRequired15 pts
  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts
  • License10 pts