mcp server
Agent Receipts
Issue & verify signed (ed25519), hash-chained, timestamped provenance receipts for agent actions.
Description as published by the maintainer. Source
- version 1.0.1
- active
active — Registry entry last updated 2026-06-22.
What this server can do
3 functions, named and described by the server itself. Parameter names are shown because they say more about what a function does than its name usually does.
issue_receipt(action, inputs, outputs, agent_id, metadata, inputs_hash, outputs_hash)- 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. Required: action.
list_receipts(limit, agent_id)- 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. Required: agent_id.
verify_receipt(id, 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.
Last successful function declaration observed on . Source: https://agent-receipts.dropwatchhq.com/mcp. We list what the server declared; we do not call any of these functions.
Endpoint status observed on . Source: https://agent-receipts.dropwatchhq.com/mcp.
Signals
These are separate measurements of different things. They are deliberately not combined into one score, because a popularity number that mixes website traffic with saves and stars cannot be checked or acted on.
| Signal | Value | What it measures | Window | Observed | Source |
|---|---|---|---|---|---|
| Latest published version | 1.0.1 | Latest version string the maintainer published to the registry. | as of fetch | Model Context Protocol | |
| Registry record last updated | 2026-06-22 | When the registry record was last updated by its maintainer. | point in time | Model Context Protocol | |
| First listed in the MCP Registry | 2026-06-22 | Date this server was first published to the official MCP Registry. Not a usage or quality measure. | point in time | Model Context Protocol | |
| mcp tools declared | 3 tools | Number of functions the server itself declared when asked to list them. This is what the server offers an agent, not a measure of how well any of them work. | as of probe | agent-receipts.dropwatchhq.com | |
| mcp endpoint status | ok | The server listed 3 functions when asked. | as of probe | agent-receipts.dropwatchhq.com |
Where to get it
This record as data
Every field on this page, with its source and observation date, is in the catalog JSON. Fetch the whole kind at once instead of parsing this HTML.
GET /api/v1/entries/mcp_server.json