Skip to content

satledger timestamp receipt

by satledger.org · remote · no sign-in to list tools · v0.21.0 · published by org.satledger

RFC 3161 timestamps with no account, and a signed agent-ledger workspace. Paid per call over x402.

Changes · 10
CompareRegistry entry

14 tools: 10 change things and 4 only read.

Scanned Oct 21, 2026

No check matched anything in the tool definitions. No finding is not a safety guarantee. How the checks work.

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

Tools

Open a tool for its reasons and full description. Descriptions are the publisher's own words, shown as they are.

14 tools

Changes things 10Claude Code: ask
  • anchor_agentAsk a public RFC 3161 Time-Stamp Authority to sign the agent's current state.No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    Description, as the server wrote it
    Ask a public RFC 3161 Time-Stamp Authority to sign the agent's current state. The one fact here the operator cannot manufacture: a timestamp cannot be issued for a time that has passed. An unchanged state returns the anchor it already has. Costs 100 units. Authenticate with the workspace key in _meta[satledger/api-key].
  • create_agentCreate an agent in your workspace: a named ledger whose every event is ed25519-signed and hash-chained.No findings

    Why it is in this group

    • The name "create_agent" says "create": a word for a change.
    Description, as the server wrote it
    Create an agent in your workspace: a named ledger whose every event is ed25519-signed and hash-chained. `initial_credits` mints supply to the workspace issuer, not to the agent - fund_agent moves credits across when you need usage metering. Costs 1 unit. Authenticate with the workspace key in _meta[satledger/api-key].
  • export_agentBuild the export bundle, run the customer-side verifier over it and return the summary plus the URL of the archive (HTTP, X-API-Key, free).No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    Description, as the server wrote it
    Build the export bundle, run the customer-side verifier over it and return the summary plus the URL of the archive (HTTP, X-API-Key, free). Pass expect_action_head / expect_action_count from state YOU kept to check completeness. Free, permanently. Authenticate with the workspace key in _meta[satledger/api-key].
  • fund_agentMove credits from the workspace issuer to an agent's own account, so record_usage can burn them.No findings

    Why it is in this group

    • The description's first verb is "move": a word for a change.
    Description, as the server wrote it
    Move credits from the workspace issuer to an agent's own account, so record_usage can burn them. Costs 1 unit. Authenticate with the workspace key in _meta[satledger/api-key].
  • provision_workspaceBuy a workspace: a tamper-evident usage and action ledger for your agents, every event ed25519-signed and hash-chained, with an export your own customers verify offline.No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    Description, as the server wrote it
    Buy a workspace: a tamper-evident usage and action ledger for your agents, every event ed25519-signed and hash-chained, with an export your own customers verify offline. Pay over x402 in _meta[x402/payment]: 0.50 USDC for 2,500 units (starter), 15.00 USDC for 100,000 units (block). Every workspace also carries 10,000 free units. Returns an API key once, plus the next calls to make. The ledger operations themselves are HTTP, authenticated with that key.
  • record_actionAppend what an agent did - a tool call, a decision, a message - as a signed, hash-chained entry.No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    Description, as the server wrote it
    Append what an agent did - a tool call, a decision, a message - as a signed, hash-chained entry. This is the thing the workspace is for. Costs 1 unit. Authenticate with the workspace key in _meta[satledger/api-key].
  • record_usageBurn credits from an agent's account, as a signed ledger event.No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    Description, as the server wrote it
    Burn credits from an agent's account, as a signed ledger event. Costs 1 unit. Authenticate with the workspace key in _meta[satledger/api-key].
  • timestamp_receiptSubmit 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…No findings

    Why it is in this group

    • The description's first verb is "submit": a word for a change.
    Description, as the server wrote it
    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. Your first 3 each day are free, no payment needed. Then 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.
  • top_up_workspaceAdd units to a workspace you already hold.No findings

    Why it is in this group

    • The description's first verb is "add": a word for a change.
    Description, as the server wrote it
    Add units to a workspace you already hold. Send its API key in _meta[satledger/api-key] (or the api_key argument) and the payment in _meta[x402/payment]: 0.50 USDC for 2,500 units (starter), 15.00 USDC for 100,000 units (block). The units land in that workspace and nothing new is created; buying a workspace instead gives you an empty ledger under a different key.
  • workspace_balanceUnits remaining and what each operation costs.No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    Description, as the server wrote it
    Units remaining and what each operation costs. Free, so you can plan before you are refused. Authenticate with the workspace key in _meta[satledger/api-key].
Only reads 4Claude Code: allow
  • describe_agentCurrent state: root id, state hash, event count, balance.No findings

    Why it is in this group

    • The name "describe_agent" says "describe": a word for reading.
    Description, as the server wrote it
    Current state: root id, state hash, event count, balance. Free. Authenticate with the workspace key in _meta[satledger/api-key].
  • list_actionsThe agent's action log, with its head hash.No findings

    Why it is in this group

    • The name "list_actions" says "list": a word for reading.
    Description, as the server wrote it
    The agent's action log, with its head hash. Free. Authenticate with the workspace key in _meta[satledger/api-key].
  • list_agentsEvery agent in your workspace.No findings

    Why it is in this group

    • The name "list_agents" says "list": a word for reading.
    Description, as the server wrote it
    Every agent in your workspace. Free. Authenticate with the workspace key in _meta[satledger/api-key].
  • list_anchorsEvery anchor commitment recorded for the agent.No findings

    Why it is in this group

    • The name "list_anchors" says "list": a word for reading.
    Description, as the server wrote it
    Every anchor commitment recorded for the agent. Free. Authenticate with the workspace key in _meta[satledger/api-key].

This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.

Install

Pinned to version 0.21.0. Values in angle brackets are yours to fill in.

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

Run in a terminal.

Claude Code permissions

Allow the reads, ask before a change, deny the deletes. Paste into .claude/settings.json.

.claude/settings.json
{
  "permissions": {
    "allow": [
      "mcp__timestamp-receipt__list_agents",
      "mcp__timestamp-receipt__describe_agent",
      "mcp__timestamp-receipt__list_actions",
      "mcp__timestamp-receipt__list_anchors"
    ],
    "ask": [
      "mcp__timestamp-receipt__timestamp_receipt",
      "mcp__timestamp-receipt__provision_workspace",
      "mcp__timestamp-receipt__top_up_workspace",
      "mcp__timestamp-receipt__create_agent",
      "mcp__timestamp-receipt__record_action",
      "mcp__timestamp-receipt__fund_agent",
      "mcp__timestamp-receipt__record_usage",
      "mcp__timestamp-receipt__anchor_agent",
      "mcp__timestamp-receipt__export_agent",
      "mcp__timestamp-receipt__workspace_balance"
    ],
    "deny": []
  }
}

Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. It assumes the server is installed as timestamp-receipt. Review it before you use it.