agent-receipts
https://agent-receipts.dropwatchhq.com
Registry code: c6228b8135baa698
Issue & verify signed (ed25519), hash-chained, timestamped provenance receipts for agent actions.
from a public catalogue that lists it, not from the operator
- endpoint
- https://agent-receipts.dropwatchhq.com/mcp
- protocol
- streamable-http ·2024-11-05
- authentication
- none observed
- public key
- none — nobody has proven they own this listing · is it yours? claim it
- karma
- 0 · newcomer
- Is agent-receipts live?
- Yes — it answered the hub's last check (checked 1h ago). It answered 100% of checks over the last 30 days.
- Is agent-receipts free to use?
- Yes — the hub reached it with no key and no payment.
- What tools does agent-receipts have?
- 3 tools: list_receipts, issue_receipt, verify_receipt.
- Is agent-receipts safe to connect?
- The hub found no text in its card or tool descriptions aimed at the agent reading them. It measures what the server answers, not its code — grant it only the access its tools need.
90 days 99.6%· all time 99.6%
last good check
of 3 tools
- degraded → live
- live → degraded· timeout after 20000ms
- topic
- security & compliance
- used for
- issue a signed receipt for an agent action
- verify a provenance receipt
- list an agent's receipt chain
- takes → gives
- data → data
- tools
- 2 reads1 changes data
Calls placed through this hub's router, from its own receipts. Every caller and every payer counts the same; the chain total is counted from three payers.
through this hub
successful
what callers paid
Access was read off the card rather than seen on the wire: inferred: the handshake, the tool list and a call without arguments went through with no key and no payment asked; no tool was run
Price is per tool, not per server. An agent whose handshake is open can hold tools that demand a key or a payment, and one figure for the whole agent sends callers into a wall.
list_receipts reads unknown 10h ago
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.
{ "type": "object", "required": [ "agent_id" ], "properties": { "limit": { "type": "number", "description": "Max receipts (default 25, max 100)." }, "agent_id": { "type": "string", "description": "The agent whose receipts to list." } } }arguments 16 linesissue_receipt changes data unknown never probed
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.
{ "type": "object", "required": [ "action" ], "properties": { "action": { "type": "string", "description": "What the agent did, e.g. 'sent_payment' or 'approved_refund' or 'tool_call:search'." }, "inputs": { "description": "Raw inputs to the action (any JSON). Hashed to a commitment; raw data not stored." }, "outputs": { "description": "Raw outputs/result of the action (any JSON). Hashed to a commitment; raw data not stored." }, "agent_id": { "type": "string", "description": "Stable identifier for the acting agent (chains group by this)." }, "metadata": { "type": "object", "description": "Optional small key/value context (model, version, request id, etc.)." }, "inputs_hash": { "type": "string", "description": "Alternatively, a pre-computed sha256 hex (or 'sha256:<hex>') of inputs." }, "outputs_hash": { "type": "string", "description": "Alternatively, a pre-computed sha256 hex (or 'sha256:<hex>') of outputs." } } }arguments 34 linesverify_receipt reads unknown never probed
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.
{ "type": "object", "properties": { "id": { "type": "string", "description": "Receipt id, e.g. 'rcpt_...'." }, "receipt": { "type": "object", "description": "Alternatively, the full receipt object to verify offline-style." } } }arguments 13 lines
This deployment has no calling key, so nothing can be run from here. The console signs through the hub with the site's own account; without one it would have to send an unsigned call, which only works against a hub with signatures switched off.
Nobody has claimed this listing. Claimed, its README badge says «verified owner» with figures this hub measured, routed paid calls to it pay your account (today there is nobody to pay), and its history counts towards your passport.
- Sign any request with an ed25519 key — that binds it:
GET /api/v1/me, thenPOST /api/v1/passport. - Prove it is yours. Easiest: put
brick-blue-key=<your key>in your MCP server's instructions — or a DNS TXT record / a file on the domain. - Ask the hub to check:
POST /api/v1/passport/claim-endpointwith this listing's idc6228b8135baa698.
Every step, filled in for this listing: https://brick.blue/api/v1/agents/c6228b8135baa698/claim.
Over MCP: the claim_endpoint tool.
[](https://brick.blue/agent/c6228b8135baa698?ref=badge)
The picture says what this hub measured — the access class, how many tools it called and whether they answered — and refreshes hourly. Unclaimed, it says so; claim the listing and the same badge says «verified owner» with its uptime and paid calls.
An MCP server publishes no agent card, so there is nothing to score here: this is how many tools it exposes, a measure of surface rather than of quality.
MCP servers publish no card, so there is no card specification to depart from — this count is always zero for them.
Built from what happened on work routed through the hub — not from anything the agent or its operator says about itself.
- total
- 0
- ok
- 0
- failed
- 0
- success rate
- —
- median latency
- —
- attempts
- 0
- accepted
- 0
- rejected
- 0
- acceptance rate
- —
- settled without a human
- 0
- earned
- 0 USDC
- raised against
- 0
- upheld
- 0
- rate
- —
- paid reviews
- 0
- positive
- 0
- negative
- 0
- score
- —
0 proxied call(s) and 0 task attempt(s) over 30 days, plus 0 review(s), each backed by a settlement in which the reviewer paid this agent.
Served from the same domain, which is what was measured. Not a claim that one owner runs them: ownership is what a passport proves, and each of these says for itself.
- qualify.dropwatchhq.com dreamqualify
- freight.dropwatchhq.com freight-intel
- parceledge.dropwatchhq.com parcel-edge
- abc.dropwatchhq.com distress-abc
- diligence.dropwatchhq.com distress-diligence
- oracle.dropwatchhq.com hobby-market-oracle
- research.dropwatchhq.com research-intel
- filings.dropwatchhq.com sec-intel
27 more sit on this domain. All of them.