Skip to main content
Glama
aibtc-mcp-server
by aibtcdev

Related Servers

Alternatives to aibtc-mcp-server

No user-submitted related servers found.

    Related Servers

    TDQS

    C2.8/5.0

    Scored across 387 tools

    Disambiguation1/5

    Many tools appear to do the same thing: pillar_boost vs pillar_direct_boost, pillar_supply vs pillar_direct_supply, pillar_send vs pillar_direct_send, the parallel pillar_dca_* and pillar_direct_dca_* families, and explicit aliases like sbtc_withdraw for sbtc_initiate_withdrawal and sbtc_withdraw_status for sbtc_withdrawal_status. The thirteen deprecated news_* tools duplicate the legion_* surface and remain callable, and multiple DEX/market/rune-balance/inbox tools overlap heavily. An agent cannot reliably choose among these without reading long descriptions.

    Naming Consistency2/5

    Names are uniformly snake_case, but the conventions are inconsistent at the domain level: some families use a get_/list_ verb-first prefix, others use domain-first prefixes (runes_get_*, tenero_*, pillar_*), and there are explicit alias pairs (sbtc_withdraw / sbtc_withdraw_status) plus a split pillar_ vs pillar_direct_ convention. Deprecated news_* names coexist with their legion_* replacements, making the surface unpredictable.

    Tool Count1/5

    387 tools is an extreme mismatch for any coherent server purpose. The surface is far beyond the 15-tool well-scoped range and includes entire deprecated families and duplicate aliases that inflate the count without adding capability.

    Completeness3/5

    Coverage is very broad across wallets, DeFi, ordinals, runes, NFTs, BNS, Nostr, x402, identity, reputation, lightning, and prediction markets, so few core domains are entirely missing. However, dead deprecated news_* tools, alias-only withdrawal operations, and gaps in lifecycle operations (e.g., limited bounty update/delete paths) mean the surface is not cleanly complete.

    Maintenance

    ActivityActive
    ResponsivenessUsually handled