Related Servers

Tools are mostly distinct by resource+key (header-by-hash vs header-by-topoheight vs last-header; get_info vs get_height vs get_block_count), and composite tools carry explicit PREFER routing that tells agents when to use them over primitives. A few pairs remain confusable — recommend_docs_path vs dero_docs_search, explain_smart_contract vs tela_inspect, and the dero_get_info/get_height/get_block_count trio — but the descriptions mitigate most misselection risk.

The dero_get_* primitives and dero_docs_*/dero_daemon_* sub-groups are highly consistent, but the composite tier mixes conventions: bare verbs (explain_smart_contract, verify_supply, audit_chain_artifact_claim), tela_* forms (tela_inspect, tela_get_doc_content), and prefixed forms (dero_tela_list_apps, dero_forge_demo_proof). All names are readable snake_case, but the prefix pattern is not uniform across the 33-tool surface.

33 tools is heavy for a single MCP server, though the actual domain is broad (daemon RPC reads, bundled docs, TELA app inspection, proof integrity auditing). The count is inflated by composite wrappers (diagnose_chain_health, trace_transaction_with_context, audit_chain_artifact_claim, recommend_docs_path) that duplicate primitive capabilities rather than adding new surface area.

The read-only surface is thorough: chain state, blocks, headers, txs, SC state, encrypted balances, gas estimates, name/dURL resolution, docs search/retrieval, TELA content extraction, supply verification, and end-to-end integrity audits. Write operations (wallet transfers, SubmitBlock) are deliberately excluded with explicit notes, and minor gaps such as batch block fetches or full-block-by-topoheight are workable around via existing tools.