stampthisfile

Official registry Other

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

Install

Add this to your client's MCP configuration (Claude Desktop: claude_desktop_config.json; Cursor: .cursor/mcp.json; VS Code and others use the same "mcpServers" shape).

Remote (streamable-http)
Claude Code
claude mcp add --transport http stampthisfile 'https://stampthisfile.com/mcp'
JSON configuration (Claude Desktop, Cursor, VS Code)
{
    "mcpServers": {
        "stampthisfile": {
            "type": "http",
            "url": "https://stampthisfile.com/mcp"
        }
    }
}

Documentation

From the project's README on GitHub, refreshed weekly. Links open on GitHub.

Contents
  1. stampthisfile MCP server
  2. Connect
  3. Tools
  4. Pricing
  5. More
  6. License

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

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.

Frequently asked questions

What is stampthisfile?

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

How do I install stampthisfile?

It runs as a remote server. In Claude Code: claude mcp add --transport http stampthisfile 'https://stampthisfile.com/mcp'. For other clients, paste the JSON configuration from this page into their MCP settings.

Does stampthisfile need an API key?

Its registry entry lists no required key or secret. Some features may still need an account with the service it connects to.

Is stampthisfile open source?

Yes. Its code is on GitHub under the MIT license.

Who maintains stampthisfile?

It is published by stampthisfile. AI.tn lists it but does not maintain or endorse it.

From the official MCP Registry. Listing is not an endorsement: review a server's code and permissions before giving it access to your data.