Skip to main content
Glama
fyllepo

qubic-mcp

by fyllepo
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

Related Servers

Alternatives to qubic-mcp

No user-submitted related servers found.

    Related Servers

    • QuantXData MCP Server

      appydam
      A
      license
      B
      quality
      D
      maintenance
      MCP server that exposes QuantXData's institutional crypto market data APIs to AI assistants, enabling natural language queries for trades, order books, OHLCV, options, and more across 120+ exchanges.
      12
      MIT

    • Crypto MCP Server

      rex-automata
      A
      license
      A
      quality
      D
      maintenance
      The first blockchain & cryptocurrency MCP server that connects AI agents to Ethereum, Solana, Bitcoin, and cryptocurrency markets.
      9
      15 npm
      MIT

    • btc-mcp-srv

      lightphon
      A
      license
      Not graded
      quality
      C
      maintenance
      An MCP server that enables AI agents to send and receive Bitcoin over the Lightning Network using NWC or LND backends.
      MIT

    • bybit-trading

      Vanszs
      A
      license
      Not graded
      quality
      D
      maintenance
      MCP server for cryptocurrency trading across multiple exchanges (Bybit, Binance, KuCoin, etc.) with real-time price data, comparison, and natural language query support. Integrates with AI assistants via the Model Context Protocol.
      MIT
    Deploy Server
    One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

    TDQS

    A3.6/5.0

    Scored across 27 tools

    Disambiguation3/5

    Several tools have overlapping purposes, such as get_tick_info and get_network_status both returning tick data, and query_smart_contract vs query_contract both dealing with contract queries. Descriptions help distinguish them, but the boundaries are not always clear, especially for agents choosing between the two contract query tools.

    Naming Consistency4/5

    Most tools use a consistent verb_noun pattern (e.g., save_wallet, list_wallets, get_balance). Minor deviations include the confusing similarity between query_smart_contract and query_contract, and the use of 'qu_usd' instead of a more standard naming convention, but overall the pattern is predictable.

    Tool Count2/5

    With 27 tools, the server exceeds the threshold for a heavy tool set (25+). While the breadth covers many Qubic features, the count feels excessive and could be consolidated, such as merging the two contract query tools or reducing the number of local config tools.

    Completeness3/5

    The server covers a wide range of read-only Qubic operations: balances, transfers, network status, mining, DEX orderbooks, and smart contract queries. However, there is no ability to send transactions or perform any on-chain write, which is a notable gap for a wallet and network management server, even if intentional for security.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues

    Resources