No user-submitted related servers found.
Scored across 36 tools
Most tools target a distinct resource-and-action combination, and the major domains (accounts, agreements, registry/reputation, messaging, guardian) are clearly separated. The only mild ambiguities are near-duplicate pairs like pay/smart_pay and update_service/update_service_batch, but their intended differences are explicit.
Names overwhelmingly follow azeth_<verb>_<noun> in snake_case, with get/list/create/update used predictably. A few outliers (azeth_accounts, azeth_balance, azeth_history, azeth_guardian_approve/status) break the strict verb-first pattern, but they are still readable and not chaotic.
36 tools is a heavy surface for a single MCP server, well beyond the 25-tool threshold in the rubric. Several tools could be consolidated (agreement queries, service update vs batch update, whitelist token vs protocol, guardian approve/status), so the set feels bloated even though the underlying platform is broad.
The toolkit covers the full smart-account lifecycle, payment agreements, trust-registry/reputation, messaging, and guardian interactions with no dead-end workflows. Minor gaps remain—no service deregistration, no agreement amendment, and no guardrail-limit editing—but agents can accomplish the core platform tasks.