Receipts
The Receipts MCP tools: `trust_receipts`.
The Receipts category has 1 tool:
trust_receipts— Read a token's trust setup: the trust modules deployed for it, what each module's controls are and what the current values are, the holders and the recipients any fee is split between, the change log, and the version/supersession chain. FREE, unauthenticated, and it reads the chain but spends nothing of yours — it is the same document a holder sees at the public Receipts page, so use it to check a claim before repeating it. Zero modules is a real answer, not an error: a token whose creator never registered a trust setup has none, and the document says so out loud rather than rendering an empty shell that reads like a broken page. A failed chain read becomes a namedwarningsentry and the rest still renders, so readwarningsbefore treating an absent control as 'not set'. Nothing here is an audit: the document reports what the contracts declare and what the chain shows, and a module being present says nothing about whether it is well configured.
The full request and response shape for each, and a live playground, live on the generated reference at GET /mcp/tools.
Trust
A token's trust setup — the modules deployed for it, their controls, and the change log — as a holder reads it.
trust_receipts
Read a token's trust setup: the trust modules deployed for it, what each module's controls are and what the current values are, the holders and the recipients any fee is split between, the change log, and the version/supersession chain. FREE, unauthenticated, and it reads the chain but spends nothing of yours — it is the same document a holder sees at the public Receipts page, so use it to check a claim before repeating it. **Zero modules is a real answer, not an error**: a token whose creator never registered a trust setup has none, and the document says so out loud rather than rendering an empty shell that reads like a broken page. A failed chain read becomes a named `warnings` entry and the rest still renders, so read `warnings` before treating an absent control as 'not set'. Nothing here is an audit: the document reports what the contracts declare and what the chain shows, and a module being present says nothing about whether it is well configured.