No user-submitted related servers found.
Scored across 29 tools
Each tool is unambiguously prefixed by its protocol (asa_, arc200_, nt200_, arc72_) and named after a specific action or query, so no two tools appear to target the same operation. Even similar functions like `balance_of` and `has_balance` have distinct meanings and clear descriptions. The grouping by asset type eliminates cross-protocol confusion.
All tool names follow a strict lowercase snake_case pattern with a protocol prefix and a verb_noun or verb_txn suffix. Transaction builders consistently end in `_txn`, while queries use `get_`, `search_`, `has_`, etc., making the naming perfectly predictable across all 29 tools.
With 29 tools, the server significantly exceeds the recommended 3-15 range for well-scoped MCP servers, and is above the 25+ threshold explicitly labeled as 'too many' in the rubric. While each tool serves a distinct purpose and covers multiple token standards, the sheer number is likely to overwhelm agents and increase selection complexity.
The tool set provides comprehensive coverage for each supported asset type: ASA queries, holdings, transfers, opt-in, and close-out; ARC-200 includes metadata, balances, allowances, approvals, transfers, and events; ARC-72 covers ownership, approvals, token URI, supply, transfers, and events. NT200 covers deposit, withdrawal, and balance box creation. Missing operations like asset creation are outside the apparent scope, so there are no critical gaps.
