satledger timestamp receipt MCP Server

by satledger Your server? Claim it

answering

satledger timestamp receipt is answering right now. Last checked 2 min ago. It exposes 14 tools.

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

Uptime history 21 days of history · worst day 99%

21 days agonow

100.0%

Uptime 24h

92 of 92 checks

Tools

read from the server

183 ms

Response time

average over 24h

open, no key

Access

streamable-http

What changed 37

Every tool that appeared, vanished or quietly changed what it asks for. Recorded since 13 October 2026. No other catalogue keeps this.

1 Nov a tool changed version2 times that day

21 Oct a tool changed version

20 Oct 13 tools appeared anchor_agent, create_agent, describe_agent and 10 more

20 Oct a tool changed version5 times that day

20 Oct a tool changed the parameters it asks for top_up_workspace

20 Oct a tool description was rewritten top_up_workspace

19 Oct a tool changed version6 times that day

19 Oct a tool description was rewritten2 times that day timestamp_receipt

19 Oct a tool changed the parameters it asks for timestamp_receipt

17 Oct a tool changed version

and 15 more, back to 13 October 2026

Nothing serious here today

Today is the operative word: we check satledger timestamp receipt every 15 minutes and re-read its code on every release. Watch it and you find out the day that stops being true.

Connect this server

Endpoint below is the one we actually reach during checks — not the one copied from a README. Last verified 2 min ago.

Claude Code Claude Desktop Codex Cursor VS Code

run in your terminal

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

Settings → Connectors → Add custom connector, then paste this address

https://api.satledger.org/mcp

~/.codex/config.toml

[mcp_servers.timestamp-receipt]
url = "https://api.satledger.org/mcp"

.cursor/mcp.json

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

.vscode/mcp.json

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

Available tools 14

Read directly from the server with tools/list, grouped by what they act on. If a tool disappears, we record the date.

record

record_action

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_usage

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

actions

list_actions

The agent's action log, with its head hash. Free. Authenticate with the workspace key in _meta[satledger/api-key].

agent

create_agent

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

agents

list_agents

Every agent in your workspace. Free. Authenticate with the workspace key in _meta[satledger/api-key].

anchor

anchor_agent

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

anchors

list_anchors

Every anchor commitment recorded for the agent. Free. Authenticate with the workspace key in _meta[satledger/api-key].

describe

describe_agent

Current state: root id, state hash, event count, balance. Free. Authenticate with the workspace key in _meta[satledger/api-key].

export

export_agent

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

fund_agent

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

provision_workspace

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.

timestamp

timestamp_receipt

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

top_up_workspace

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

workspace_balance

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

Endpoints

URL	Transport	State	Latency	Checked
https://api.satledger.org/mcp	streamable-http	answering	158 ms	2 min ago

Alternatives to satledger timestamp receipt

same job, measured the same way

402cron

by 402cron

Paid cron for AI agents: we call your https URL on schedule, signed. No account, paid with x402.

16 tools answering

Mnemos — memory as a service

by virohanalife

Bi-temporal memory-as-a-service and paid agent labor. Pay-per-call USDC via x402; signed receipts.

15 tools answering

Ausca

by ausca

Pay-per-call APIs and MCP services for agents, no accounts or keys, with verifiable receipts.

425 installs/wk 17 tools answering

Agoreum (read only, no account)

by agoreum

Search agents and services, and buy Agoreum's checks per call over x402. No account.

14 tools answering

Tabularium

by sqlazy

Agent memory and a signed spending ledger: pay any x402 API, keep a provable receipt.

2 132 installs/wk local only

Ailabra Agent Profit Ledger

by jsjfin

Determine autonomous-agent profit and cash flow with x402-paid MCP tools and signed reports.

8 tools answering

Occultron

by luckyjupiter

Crypto-paid uncensored LLM inference with signed execution receipts. No account.

local only

402post

by 402post

Paid classifieds for AI agents: post a listing over MCP, pay with x402. No account.

7 tools answering

satledger timestamp receipt — questions

Answers built from our own checks of this server.

What can satledger timestamp receipt do?

It exposes 14 tools, read directly from the server on our last check. Among them: anchor_agent, create_agent, describe_agent, export_agent, fund_agent, list_actions and 8 more. The full list with descriptions is on this page — we take it from the server itself via tools/list, not from a README. How MCP servers expose tools in the first place →

Is satledger timestamp receipt working right now?

We send a real MCP handshake every 15 minutes. Over the last 24 hours 92 of 92 checks got a reply (100.0%), average response time 183 ms. The bar chart above shows every period we have measured.

How do I connect satledger timestamp receipt?

Copy the ready config from this page. We generate it for Claude Code, Claude Desktop, Codex, Cursor and VS Code, each in the form that client actually reads. It is a remote server, so there is nothing to install — the client connects to the address.

Does satledger timestamp receipt need an API key?

No. satledger timestamp receipt completed a full MCP handshake with us as an anonymous client and listed its tools without asking for anything. All 14 of them are readable on this page. This is what we observed, not what the docs claim.

How fast is satledger timestamp receipt?

It answers our handshake in 183 ms on average, which is faster than 75% of all working MCP servers we measure. That puts it in the quick quarter of the ecosystem. The comparison comes from our own checks across the whole registry, every 15 minutes.