About Agent Receipts
Issue & verify signed (ed25519), hash-chained, timestamped provenance receipts for agent actions
Configuration
Remote servers need no local install. Pick your client, then copy the config or install in one click.
https://agent-receipts.dropwatchhq.com/mcpclaude mcp add --transport http com-dropwatchhq-agent-receipts https://agent-receipts.dropwatchhq.com/mcp{"mcpServers":{"com-dropwatchhq-agent-receipts":{"type":"http","url":"https://agent-receipts.dropwatchhq.com/mcp"}}}Open in Cursor{"servers":{"com-dropwatchhq-agent-receipts":{"type":"http","url":"https://agent-receipts.dropwatchhq.com/mcp"}}}Open in VS Code{"mcpServers":{"com-dropwatchhq-agent-receipts":{"type":"http","url":"https://agent-receipts.dropwatchhq.com/mcp"}}}{"mcpServers":{"com-dropwatchhq-agent-receipts":{"serverUrl":"https://agent-receipts.dropwatchhq.com/mcp"}}}Run commands in a terminal; paste JSON into the client’s MCP config and restart. Servers that need sign-in will prompt on first connect.
Tools
3| Parameter | Type | Required | Description |
|---|---|---|---|
| action | string | Yes | What the agent did, e.g. 'sent_payment' or 'approved_refund' or 'tool_call:search'. |
| inputs | any | No | Raw inputs to the action (any JSON). Hashed to a commitment; raw data not stored. |
| outputs | any | No | Raw outputs/result of the action (any JSON). Hashed to a commitment; raw data not stored. |
| agent_id | string | No | Stable identifier for the acting agent (chains group by this). |
| metadata | object | No | Optional small key/value context (model, version, request id, etc.). |
| inputs_hash | string | No | Alternatively, a pre-computed sha256 hex (or 'sha256:<hex>') of inputs. |
| outputs_hash | string | No | Alternatively, a pre-computed sha256 hex (or 'sha256:<hex>') of outputs. |
Details
The maintainer has not added details yet. Check the README in the repository.
Comments
New to MCP?
From what the protocol is to installing your first server, these answers cover most first questions.
An open protocol that defines how AI applications connect to external tools and data in a uniform way. Clients talk to the model; MCP servers provide tools, resources and prompt templates. They exchange standard messages, so one server can be reused by many clients.