Other · Local MCP server
Agent Receipts MCP
EU AI Act-ready audit trail: signed, tamper-evident receipts proving what your AI agents did.
What the MCP Registry states
The entry as published to the official MCP Registry (read 2026-10-04), latest version.
- Registry name
io.github.dhanushs1912-svg/agent-receipts-mcp- Version
- 0.1.2
- Status
- Active
- Category
- other
- Transport
- stdio (local process)
- Package
- npm
- Published
- 2026-07-17
- Updated
- 2026-07-17
- Publisher
- dhanushs1912-svg (GitHub)
- Repository
- github.com/dhanushs1912-svg/agent-receipts-mcp
- Source
- Registry API entry
Packages
| Registry | Package | Version | Transport |
|---|---|---|---|
| npm | agent-receipts-mcp | 0.1.2 | stdio |
How to connect Agent Receipts MCP
Agent Receipts MCP runs locally from a Node.js package published to the npm registry: agent-receipts-mcp version 0.1.2. It speaks MCP over stdio, so the client starts it as a program and talks to it through standard input and output. It needs Node.js; clients usually start it with npx — the usual command is npx -y agent-receipts-mcp@0.1.2. It reads the environment variable AGENT_RECEIPTS_DATA; set it in the client's configuration for this server.
In the mcpServers JSON format that many desktop and editor MCP clients read, the entry looks like this (placeholders in angle brackets):
{
"mcpServers": {
"agent-receipts-mcp": {
"command": "npx",
"args": [
"-y",
"agent-receipts-mcp@0.1.2"
],
"env": {
"AGENT_RECEIPTS_DATA": "<value>"
}
}
}
}Derived from the registry entry, not tested here. What the server does, and on what terms, is set by its publisher; check its repository or website before giving it access to your accounts or files. How to add an MCP server to an assistant · Before you connect
More other servers
| Server | Runs |
|---|---|
| Agent ReadyScan any URL for AI agent readability — Vercel Spec, llmstxt.org, and agent-protocol manifests. | Remote & Local · HTTP, stdio |
| Agent Ready KitAgent-readiness scanner (0-5 score), robots.txt + llms.txt generators, managed agent enablement. | Remote · HTTP |
| Agent Ready Website CheckCheck whether a website is readable by AI agents: robots, llms.txt, sitemap, HTML. Bounded. | Remote · HTTP |
| Agent ReceiptsIssue & verify signed (ed25519), hash-chained, timestamped provenance receipts for agent actions. | Remote · HTTP |
| Agent RelayAgent Relay MCP: invite-based channels, agent contracts and per-side human approvals. | Local · stdio |
| Agent RelayEnd-to-end encrypted inbox where AI agents deliver files and request human approval. | Local · stdio |
| Agent ReputationComplaint registry for paid agent transactions - check a seller before you pay, or file your own. | Remote · HTTP |
| Agent RescueCross-session idempotency, URLs as schema-validated JSON, and a record of missing capabilities. | Remote · HTTP |