satledger timestamp receipt MCP Server

Install satledger timestamp receipt MCP server

claude mcp add --transport http timestamp-receipt https://api.satledger.org/mcp

{
  "mcpServers": {
    "timestamp-receipt": {
      "url": "https://api.satledger.org/mcp"
    }
  }
}

{
  "mcpServers": {
    "timestamp-receipt": {
      "command": "npx",
      "args": [
        "-y",
        "mcp-remote",
        "https://api.satledger.org/mcp"
      ]
    }
  }
}

{
  "servers": {
    "timestamp-receipt": {
      "type": "http",
      "url": "https://api.satledger.org/mcp"
    }
  }
}

{
  "mcpServers": {
    "timestamp-receipt": {
      "serverUrl": "https://api.satledger.org/mcp"
    }
  }
}

Context tax

Connecting this server adds ~258 tokens of tool definitions to every model turn (lean, 1 tool). Measured 2026-10-19 via its hosted endpoint; o200k tokenizer, worst case for clients that load all tools up front. How we measure

Input prices as of 2026-10-06. Excludes your own prompt and output.

Tools (1)

• timestamp_receipt256 tok

  Submit a SHA-256 digest and receive a Time-Stamp Authority's signed RFC 3161 token over it: evidence that the data you hashed existed at that time, verifiable against the authority without trusting or contacting this service. Hash your data yourself - it never leaves your side. 0.05 USDC for one, or 0.50 for up to 10 in a single call and a single payment, bound to one timestamp by a Merkle root. Paid over x402. No account, nothing stored here afterwards.

Freshness

Active — last maintenance signal 6d ago. The newest of the signals below sets the band.

1. Last commit (default branch)

   no data · GitHub

2. Latest release

   no data · GitHub

3. Package published

   no data · npm/PyPI

4. Registry entry updated

   2026-10-13 · 6d ago · official registry · v0.15.4