# stampthisfile (remote · stampthisfile.com)

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

- Trust score: 61/100 (medium)
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-10-23

## Components

- remote · `stampthisfile.com`: 61/100 (this document), [markdown](https://verifymcp.io/servers/stampthisfile-mcp/stampthisfile.md), [page](https://verifymcp.io/servers/stampthisfile-mcp/stampthisfile)

## Channel facts

- Endpoint: `https://stampthisfile.com/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `0.1.0`

## Trust breakdown

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. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-10-23.

- **Endpoint Security**: 46/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - 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.
  - HTTPS enforcement could not be verified: the plaintext port answered with HTTP 405, which proves neither a plaintext path nor enforcement.
  - HSTS check failed: the Strict-Transport-Security header is absent.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 71/100
  - AI-judged instruction clarity (excellent).
  - 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.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 10/100
  - Stability observed for 3 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% of tool parameters carry a description.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 4 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 5 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.

## Install

### 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.

### Claude

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

### Cursor

```json
{
  "mcpServers": {
    "stampthisfile-mcp": {
      "url": "https://stampthisfile.com/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "stampthisfile-mcp": {
      "type": "http",
      "url": "https://stampthisfile.com/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.stampthisfile-mcp]
url = "https://stampthisfile.com/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "stampthisfile-mcp": {
      "type": "remote",
      "url": "https://stampthisfile.com/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add stampthisfile-mcp --url 'https://stampthisfile.com/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  stampthisfile-mcp:
    url: "https://stampthisfile.com/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "stampthisfile-mcp": {
      "Transport": "http",
      "Url": "https://stampthisfile.com/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add stampthisfile-mcp -t streamable-http -u 'https://stampthisfile.com/mcp'
```

### Other

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

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-10-23 (score 61, +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.

### 2026-10-22 (score 60, 0)

- [security] Tool “verify_proof” rewrote its description, which is the text the model reads

### 2026-10-21 (score 60, +1)

- [functional improvement] Stability: unverified → 0.03

### 2026-10-20 (score 59)

First indexed and scored.

## MCP tools (4)

### `stamp_hashes` (~274 tokens)

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.

Input parameters:

- `hashes` (array, required): 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)

### `get_stamp` (~66 tokens)

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.

Input parameters:

- `id` (string, required): The stamp id (stp_…), as returned by stamp_hashes

### `get_proof` (~84 tokens)

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.

Input parameters:

- `id` (string, required): The stamp id (stp_…), as returned by stamp_hashes

### `verify_proof` (~140 tokens)

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.

Input parameters:

- `hash` (string, required): SHA-256 of the file, 64 hex characters
- `ots` (string, required): The .ots proof, base64

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/stampthisfile-mcp/stampthisfile#diagnostics

## Score history

- 2026-10-23: 61
- 2026-10-22: 60
- 2026-10-21: 60
- 2026-10-20: 59

## Common questions

### 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.

## Links

- Remote endpoint: https://stampthisfile.com/mcp
- Repository: https://github.com/stampthisfile/mcp
- Website: https://stampthisfile.com/
- Changelog RSS feed: https://verifymcp.io/servers/stampthisfile-mcp/stampthisfile.xml
- Changelog JSON feed: https://verifymcp.io/servers/stampthisfile-mcp/stampthisfile.json
- HTML version of this page: https://verifymcp.io/servers/stampthisfile-mcp/stampthisfile