Agent Receipts MCP server
com.dropwatchhq/agent-receiptsdropwatchhq.comstreamable-httpv1.0.1Scanned
Issue & verify signed (ed25519), hash-chained, timestamped provenance receipts for agent actions.
3 tools: 2 change things and 1 only read.
- Reads private data · 0
- Reads text others write · 1
- Can send data out · 0
- No findings
Tools listed without sign-in. Remote posture
With Anlyon
2 tools here change things. Govern them.
- Anlyon lists the tools and adopts none.
- Each tool you adopt gets approvals and receipts.
- Your agent never holds the key.
A tool your agent calls directly is not routed through Anlyon and is not governed by it. Anlyon Radar only lists and labels, and these labels are the same either way.
What the Agent Receipts MCP server can do
The Agent Receipts MCP server is published by dropwatchhq.com, a domain the MCP Registry verified. It has 3 tools. It can create or change data (2 tools: issue_receipt and verify_receipt), but cannot delete data. 1 tool only reads.
1 tool brings in text other people can write (list_receipts).
None of the fixed checks matched anything in its tool definitions. That is not a safety guarantee.
Its remote endpoint lists its tools without sign-in.
Last scanned Nov 13, 2026, version 1.0.1.
Tools
Grouped by what each tool does, most consequential first. Open one for its reasons and full description; descriptions are the publisher's own words.
3 tools
Changes things 2Claude Code: ask
issue_receiptMint a verifiable provenance receipt for an autonomous-agent action.No findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
Description, as the server wrote it 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.
verify_receiptVerify a receipt by id (or by passing the full receipt object).No findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
Description, as the server wrote it 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.
Only reads 1Show 1 read-only tool
list_receiptsList the receipt hash-chain for an agent_id, newest first (id, action, timestamp, sequence, hashes, verifyUrl).Reads text others writeNo findings
Why it is in this group
- The name "list_receipts" says "list": a word for reading.
What it can reach
- untrusted-inputThe description's first sentence says "list" and "url": it reads web pages, which anyone can write.
Description, as the server wrote it 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.
This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.
Exfil surface
Which tools read private data, which read text someone else can write, and which can send data out. One of each is a path a prompt injection can use.
No private-data, untrusted-input, outbound path in this server alone: no tool is tagged private-data or outbound.
- Reads private data0
- Reads files, mail, messages, databases, secrets, calendars or repositories.
- Reads text others write1
- Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
- Can send data out0
- Can carry data to people or systems: it sends, posts or publishes, or takes a recipient, channel or URL.
Other servers in the same agent add their own tools to these paths. Audit your whole setup to see them together.
Remote posture
What anyone on the internet sees at the remote endpoint: an anonymous initialize and tools/list, and the public OAuth metadata.
Looked at Nov 20, 2026, 18:37 UTC, unchanged since Oct 22, 2026. No credentials were sent and no tool was called. What is looked at.
- Reachable
- yes
- HTTP status of an anonymous initialize
- 200
- tools/list served without credentials
- yes
- Tools that change things, listed without credentials
- 2
- Protocol version
- 2024-11-05
- WWW-Authenticate on 401
- not observed
- resource_metadata in WWW-Authenticate
- not observed
- RFC 9728 protected resource metadata
- not observed
- Authorization servers
- not observed
- Legacy HTTP+SSE transport
- no
- Dynamic client registration
- not observed
- Client ID metadata documents
- not observed
- WarnThe whole server
The endpoint served tools/list without credentials, and the list has 2 tools that change things (2 write). Whether a call also works without credentials was not tested: tools are never called.
What this check looks forMatched text
https://agent-receipts.dropwatchhq.com/mcp: tools/list returned 3 tools to an anonymous client, including issue_receipt (write), verify_receipt (write)
Findings
Matches of fixed checks, with the text they matched.
No check matched anything in these tool definitions. That is not a safety guarantee.
History
Changes to its tool definitions and to its remote endpoint, newest first.
No change seen yet. Its tools are rescanned every day, and a remote endpoint is looked at once a week.
Install
Pinned to version 1.0.1. Values in angle brackets are yours to fill in.
claude mcp add --transport http agent-receipts https://agent-receipts.dropwatchhq.com/mcpclaude mcp add --transport http agent-receipts https://agent-receipts.dropwatchhq.com/mcpRun in a terminal.
Claude Code permissions
Allow the reads, ask before a change or a way out, deny the deletes. Paste into .claude/settings.json.
{
"permissions": {
"allow": [
"mcp__agent-receipts__list_receipts"
],
"ask": [
"mcp__agent-receipts__issue_receipt",
"mcp__agent-receipts__verify_receipt"
],
"deny": []
}
}Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. A read that can send data out (it takes a URL, say) asks first too. It assumes the server is installed as agent-receipts. Review it before you use it.
Capability tags behind 1 rule
- mcp__agent-receipts__list_receipts untrusted-input
Pin
Keep the decision: fail CI when the tools change, follow every change, or show a badge.
Pin in CI
Fail a build when the tools you reviewed are not the tools the server serves today.
curl -s "https://radar.anlyon.com/api/v1/servers/com.dropwatchhq/agent-receipts/verify?hash=3c6063538b556d1ff18c1347f4957419bf6f595b1982f0b73aa8d33672ded2af" | jq -e '.changed == false'Pinned hash 3c6063538b55, from Nov 13, 2026, 02:18 UTC.
Watch
Get told when its tools change: a new tool, a new description, a new class.
https://radar.anlyon.com/servers/com.dropwatchhq/agent-receipts/changes.xmlAn Atom feed. Works in any feed reader or Slack's RSS app.
Badge
[](https://radar.anlyon.com/servers/com.dropwatchhq/agent-receipts)Source: MCP Registry. Synced Oct 21, 2026, 17:54 UTC.
Agent Receipts MCP server: questions and answers
Answered from the scan above, not from the publisher's description.
Is the Agent Receipts MCP server safe?
- No scan can promise that. What its definitions show: 3 tools, 2 of which can change, send or delete something, and 0 findings from fixed checks. Allow the reads, ask before each change, and deny the deletes; the permissions block on this page does that.
Can the Agent Receipts MCP server delete data?
- No tool is classed as destructive: going by their definitions, none of them deletes, cancels or revokes anything.
Can the Agent Receipts MCP server do things that cannot be undone?
- No tool is classed as irreversible: none of them sends, pays, publishes or merges, going by their definitions.
What tools does the Agent Receipts MCP server have?
- 3 tools: 2 write, 1 read. issue_receipt, verify_receipt and list_receipts.
Does the Agent Receipts MCP server need sign-in or OAuth?
- Its remote endpoint listed its tools to an anonymous client, without sign-in.
Does the Agent Receipts MCP server send data to outside services?
- None of its tools sends, posts or publishes, or takes a recipient, channel or URL.
Has the Agent Receipts MCP server changed its tools?
- Not since Anlyon Radar started tracking it. Last scanned Nov 13, 2026.