stampthisfile
REMOTE · STAMPTHISFILE.COM
Timestamp files in Bitcoin (OpenTimestamps): send a hash, pay per hash with x402, get a proof.
Available components
Last scanned (1 hour ago)
Scores higher than 46% of remote servers
Reachable. Last reached 23 Oct 2026.
Category Crypto and Web3
How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →
Endpoint Security46
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation not fully verified: no authorisation is required to call this server, and 1 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe. See how to fix → View diagnostics → Unverified
- HTTPS enforcement could not be verified: the plaintext port answered with HTTP 405, which proves neither a plaintext path nor enforcement. View diagnostics → Unverified
- HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability71
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 736 tokens (~184/item across 4 items; 4 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management10
- Stability observed for 3 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 4 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 5 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 23 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 7 to 10. That category is still filling its 30-day observation window: 2 days of observed history at the previous scan, 3 at this one. The score rises as the window fills, whether or not the server changes.
- 22 Oct 26 0
- Tool “verify_proof” rewrote its description, which is the text the model reads security
- 21 Oct 26 +1
- Stability: unverified → 0.03 ▲ functional
- 20 Oct 26 59
First indexed and scored.
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 23 Oct 2026 · Probed https://stampthisfile.com/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=stampthisfile.com | CN=WE1,O=Google Trust Services,C=US | 20 Oct 2026 | 18 Jan 2027 | ECDSA 256 | ECDSA-SHA256 | bdaced74c69806d113fa6d86c2bce4fe |
| SANs: stampthisfile.com, www.stampthisfile.com, *.www.stampthisfile.com | ||||||
| CN=WE1,O=Google Trust Services,C=US (CA) | CN=GTS Root R4,O=Google Trust Services LLC,C=US | 13 Dec 2023 | 20 Feb 2029 | ECDSA 256 | ECDSA-SHA384 | 7ff31977972c224a76155d13b6d685e3 |
| CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) | CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE | 15 Nov 2023 | 28 Jan 2028 | ECDSA 384 | SHA256-RSA | 7fe530bf331343bedd821610493d8a1b |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of stampthisfile.com. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| com. | present | 19718 | 13 | Verified |
| stampthisfile.com. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 200 |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://stampthisfile.com/mcp | Verified | 200 | |
| http (plaintext) | http://stampthisfile.com/mcp | Inconclusive | 405 |
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
get_proof Get proof ~84
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.
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | The stamp id (stp_…), as returned by stamp_hashes |
No output schema declared.
No examples provided.
get_stamp Get stamp ~66
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.
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | The stamp id (stp_…), as returned by stamp_hashes |
No output schema declared.
No examples provided.
stamp_hashes Stamp hashes ~274
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.
| Name | Type | Req | Description |
|---|---|---|---|
| hashes | array | yes | 1-100 SHA-256 hashes, each only once (sha256sum file.pdf, shasum -a 256 file.pdf) |
| payment | – | – | Only if your client cannot send _meta["x402/payment"]: the x402 PaymentPayload, as an object or base64 |
| webhook | object | – | Optional webhook; deliveries are always signed with our Ed25519 key (see https://stampthisfile.com/llms.txt) |
No output schema declared.
No examples provided.
verify_proof Verify proof ~140
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.
| Name | Type | Req | Description |
|---|---|---|---|
| hash | string | yes | SHA-256 of the file, 64 hex characters |
| ots | string | yes | The .ots proof, base64 |
No output schema declared.
No examples provided.
How do I install the stampthisfile MCP server?
stampthisfile is a hosted endpoint at https://stampthisfile.com/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
remote · stampthisfile.com
claude mcp add --transport http stampthisfile-mcp 'https://stampthisfile.com/mcp'
What is the stampthisfile MCP server?
stampthisfile is an MCP server listed in the public MCP registry as io.github.stampthisfile/mcp. Timestamp files in Bitcoin (OpenTimestamps): send a hash, pay per hash with x402, get a proof. This page covers its hosted endpoint (https://stampthisfile.com/mcp).
Is the stampthisfile MCP server safe to use?
stampthisfile scores 61 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the stampthisfile MCP server expose?
stampthisfile exposes 4 tools: stamp_hashes, get_stamp, get_proof, verify_proof. Their descriptions and schemas cost roughly 564 tokens of context every time the server is loaded.
Does the stampthisfile MCP server require authentication?
No. We connected to stampthisfile without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the stampthisfile MCP server still maintained?
stampthisfile is still listed as active in the MCP registry. We last reached this channel on 23 October 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.