Holders
The Holders MCP tools: `community_verify_wallet`.
The Holders category has 1 tool:
community_verify_wallet— Check a wallet against a community's token: read itsbalanceOfand answer with the balance and the holder census. Free — it spends no credits, takes no signature, and posts nothing to any chat. A wallet with a balance of zero is an error, not averified: false. That refusal is the product here, so it comes back as anisErrorcarrying the sentence the chat would have shown, rather than a 200 the caller has to parse. A chain read that could not answer is a SECOND, different error, and the two are deliberately distinguishable: 'you are not a holder' is an answer and 'we could not check' is a failure, and collapsing them would show a member an error where they should have seen a refusal.holdersisnullwhen the census needs an indexed transfer log this deployment does not own — that is NOT the same as"0", which is counted-and-none. The answer is stored against the caller, so a repeated check of the same wallet is not a fresh chain read on every keystroke. This tool does NOT post to Discord or Telegram: running a bot's command dispatcher, posting a countdown, or auto-posting a receipts update all speak to a third party's service on the user's behalf, and those are not actions a tool call may take unasked.
The full request and response shape for each, and a live playground, live on the generated reference at GET /mcp/tools.
Community
Check a wallet against a community's token. Free, and it posts nothing to any chat.
community_verify_wallet
Check a wallet against a community's token: read its `balanceOf` and answer with the balance and the holder census. Free — it spends no credits, takes no signature, and posts nothing to any chat. **A wallet with a balance of zero is an error, not a `verified: false`.** That refusal is the product here, so it comes back as an `isError` carrying the sentence the chat would have shown, rather than a 200 the caller has to parse. A chain read that could not answer is a SECOND, different error, and the two are deliberately distinguishable: 'you are not a holder' is an answer and 'we could not check' is a failure, and collapsing them would show a member an error where they should have seen a refusal. `holders` is `null` when the census needs an indexed transfer log this deployment does not own — that is NOT the same as `"0"`, which is counted-and-none. The answer is stored against the caller, so a repeated check of the same wallet is not a fresh chain read on every keystroke. This tool does NOT post to Discord or Telegram: running a bot's command dispatcher, posting a countdown, or auto-posting a receipts update all speak to a third party's service on the user's behalf, and those are not actions a tool call may take unasked.