mcpbeat

Agent Receipts MCP Server

com.dropwatchhq/agent-receipts
answering

Agent Receipts is answering right now. Last checked 3 min ago. It exposes 3 tools.

Issue & verify signed (ed25519), hash-chained, timestamped provenance receipts for agent actions.

Uptime history 39 hours of history
39 hours agonow
100.0%
Uptime 24h
92 of 92 checks
3
Tools
read from the server
70 ms
Response time
average over 24h
open, no key
Access
streamable-http

Connect this server

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

run in your terminal
claude mcp add agent-receipts --transport http https://agent-receipts.dropwatchhq.com/mcp
~/Library/Application Support/Claude/claude_desktop_config.json
{
  "mcpServers": {
    "agent-receipts": {
      "url": "https://agent-receipts.dropwatchhq.com/mcp"
    }
  }
}
~/.codex/config.toml
[mcp_servers.agent-receipts]
url = "https://agent-receipts.dropwatchhq.com/mcp"
.cursor/mcp.json
{
  "mcpServers": {
    "agent-receipts": {
      "url": "https://agent-receipts.dropwatchhq.com/mcp"
    }
  }
}
.vscode/mcp.json
{
  "mcpServers": {
    "agent-receipts": {
      "url": "https://agent-receipts.dropwatchhq.com/mcp"
    }
  }
}

Available tools 3

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

issue
issue_receipt
Mint a verifiable provenance receipt for an autonomous-agent action. Returns a signed (ed25519), content-hashed (SHA-256), server-timestamped receipt that is hash-chained to this agent's prior receipts (tamper-evident audit trail). Pass the raw inputs/outputs (we hash them — raw data is never stored) OR pre-computed sha256 hashes. Use for compliance, audit trails, and dispute resolution of agentic actions. PAID: $0.01 USDC/call via x402.
receipts
list_receipts
List the receipt hash-chain for an agent_id, newest first (id, action, timestamp, sequence, hashes, verifyUrl). Use to audit everything a given agent has attested. FREE.
verify
verify_receipt
Verify a receipt by id (or by passing the full receipt object). Recomputes the content hash, confirms the id commits to the body, and checks the ed25519 signature. Returns the verification checks plus the provenance record (action, agent, input/output hashes, timestamp, chain position). FREE.

Endpoints

URLTransportStateLatencyChecked
https://agent-receipts.dropwatchhq.com/mcp streamable-http answering 56 ms 3 min ago

Agent Receipts — questions

Answers built from our own checks of this server.

What can Agent Receipts do?
It exposes 3 tools, read directly from the server on our last check. Among them: issue_receipt, list_receipts, verify_receipt. 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 Agent Receipts 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 70 ms. The bar chart above shows every period we have measured.
How do I connect Agent Receipts?
Copy the ready config from this page — we generate it for Claude Code, Claude Desktop, Codex, Cursor and VS Code, each with the file path that client actually reads. It is a remote server, so there is nothing to install — the client connects to the address.
Does Agent Receipts need an API key?
No. Agent Receipts completed a full MCP handshake with us as an anonymous client and listed its tools without asking for anything. All 3 of them are readable on this page. This is what we observed, not what the docs claim.
How fast is Agent Receipts?
It answers our handshake in 70 ms on average, which is faster than 93% 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.