xahau-mcp
Related Servers
Alternatives to xahau-mcp
No user-submitted related servers found.
Related Servers
- AlicenseAqualityAmaintenanceMCP server for local transaction signing across EVM, UTXO, Tron, and XRP blockchains, with no network calls or API keys required.7269 npmMIT
- AlicenseAqualityCmaintenanceMCP server for Stellar that provides tools for accounts, payments, XDR, Horizon/Soroban RPC, AMM liquidity, SEP anchors, and Soroban contract operations.294 npmMIT
- AlicenseNot gradedqualityBmaintenanceA local-first MCP server for the WAX blockchain that enables AI hosts to query accounts, chain state, AtomicAssets, AtomicMarket, Hyperion history, and WAXP prices, as well as prepare unsigned transactions for wallet signing.MIT
- AlicenseNot gradedqualityFmaintenanceMCP server for reverse engineering Windows executables and related binary formats, offering static analysis, Ghidra-assisted function recovery, plugin-driven tooling, and optional isolated Windows runtime execution.10 npm239MIT
- AlicenseAqualityBmaintenanceUnofficial, safety-first MCP server for convenient xRocket market snapshots, with opt-in local account reads and guarded financial workflows.1081 npmMIT
- AlicenseNot gradedqualityDmaintenanceLow-level blockchain interface MCP server for Algorand and Voi networks, providing account/asset/app inspection, transaction search, block retrieval, TEAL compilation, and transaction simulation.MIT
TDQS
Scored across 87 tools
The tool descriptions are unusually precise, but the set has several closely related clusters: analyze_hook/hook_report/classify_hook, execute_hook/simulate_transaction/simulate_hook_trigger, compute_reward/reward_status, and the four quantum tools. An agent will often need to read long descriptions carefully to avoid selecting a sibling tool with a similar name.
The overwhelming majority of tools follow a verb_noun snake_case pattern (get_account_info, decode_tx_blob, build_payment_unsigned, simulate_transaction). A minority use noun-style names (xahau_server_info, reward_status, hndl_exposure, what_if), but there is no camelCase or random style mixing, so the pattern remains readable and predictable.
87 tools is far beyond the well-scoped 3-15 range and above the 50+ extreme threshold. Even for a broad Xahau platform, this is an excessive surface area that could be consolidated or split into purpose-specific servers.
The toolkit covers the Xahau domain deeply: account reads, hook inspection/analysis/simulation, unsigned transaction builders, amendment tracking, rewards, cron, and quantum diagnostics. Minor gaps remain—no generic submit path (by design), no generic ledger-object fetch, and no general TrustSet/AccountSet builder for arbitrary edits—but the major workflows have no dead ends.