Trust
A token's trust setup — the modules deployed for it, their controls, and the change log — as a holder reads it.
The Trust category is one tool, trust_receipts: the public trust document, as
an agent reads it. It is the same document a holder sees at the public Receipts
page, so use it to check a claim before repeating it.
What it answers
The trust modules deployed for the token, what each module's controls are and what their current values are, the holders and the recipients any fee is split between, the change log, and the version and supersession chain.
Zero modules is a real answer
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. An empty list is not an error and not a placeholder.
Warnings before conclusions
A failed chain read becomes a named entry in warnings and the rest still
renders. So an absent control is not the same as a control that is not set: read
warnings before concluding anything from a field that is missing.
Three refusals, not one
trust_receipts answers a malformed address, an address with no contract behind
it, and a contract that does not implement ERC-20 symbol() as three different
sentences, because they are three different mistakes with three different fixes.
The same resolution runs behind GET /trust/receipts/{chain}/{token} and behind
the rendered page, so a holder reading the page and an agent reading this tool are
looking at the same document.
What this is not
Nothing here is an audit. The document reports what the contracts declare and
what the chain shows. A module being present says nothing about whether it is
well configured, and clearedForMainnet is false on the Verify label the Scan
tool attaches for the same reason: no putty report, of any label, is an external
audit.
social_analytics
Read post analytics for one of the caller's own connected accounts over a window, through the caller's own stored Zernio key. `since` is an inclusive `YYYY-MM-DD` lower bound and Zernio allows at most 366 days. Returns Zernio's `overview` rollup and a `posts` array in Zernio's own shape, because the metric set differs per platform. The account must be on the caller's Zernio profile: an id belonging to someone else answers the same not-found as one that does not exist. Without a stored key the result is `{ code: "integration_required" }` and no call is made.
Receipts
The Receipts MCP tools: `trust_receipts`.