Skip to main content
Glama
RodrigoFlorencio86

mcp-mercado-bitcoin

by RodrigoFlorencio86
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Related Servers

Alternatives to mcp-mercado-bitcoin

No user-submitted related servers found.

    Related Servers

    • bybit-mcp

      JohnnyWic
      A
      license
      C
      quality
      D
      maintenance
      MCP server for Bybit exchange enabling 246 tools for trading, market data, account management, and more via natural language.
      100
      2
      MIT

    • coin-mcp

      sweetcornna
      A
      license
      A
      quality
      D
      maintenance
      A comprehensive cryptocurrency market-data MCP server with 49 tools across six data sources, enabling LLMs to answer market questions via natural language.
      49
      MIT

    • mcp-evolution

      billyfranklim1
      A
      license
      B
      quality
      C
      maintenance
      MCP server that integrates Evolution API to enable WhatsApp messaging, chat management, group operations, and instance control through natural language tools.
      54
      1
      MIT

    • Mercury MCP Server

      Fyko
      A
      license
      Not graded
      quality
      D
      maintenance
      MCP server for Mercury Banking API that enables listing accounts and retrieving transactions via natural language.
      7 npm
      MIT
    • Mercado Pago MCP Server by mercadolibre

      Mercado Pago MCP Serverofficial

      mercadolibre
      A
      license
      B
      quality
      D
      maintenance
      Mercado Pago's Official MCP Server offers tools so that developers can easily interact with our API using natural language, which simplifies tasks and product integration. Remotely hosted by Mercadolibre supporting Streamable HTTP Transport. Details on how to connect: https://mcp.mercadopago.com/
      1
      8
      Apache 2.0
    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.8/5.0

    Scored across 20 tools

    Disambiguation5/5

    Each tool targets a distinct resource and operation: market data (orderbook, trades, tickers, candles, symbols), account info (accounts, balances, tier, fees, positions), and order management (place, list, get, cancel, cancel all, list all). There is no overlapping purpose; even similar tools like list_orders vs list_all_orders are clearly distinguished by scope.

    Naming Consistency4/5

    Most tools follow an mb_<verb>_<noun> pattern (get, list, place, cancel), but there are minor deviations: mb_status uses a noun without a verb, mb_internal_transfer uses an adjective-noun construction, and get vs list is used inconsistently for collection-returning tools (e.g., mb_get_trades vs mb_list_orders). Overall the prefix mb_ and predictable object names keep it readable.

    Tool Count3/5

    With 20 tools, this is a substantial surface that could be trimmed by combining related functions (e.g., fees/networks, order listing variants). However, the tools are all meaningful and cover a full exchange API, fitting the 16-25 'heavy' range where some consolidation would help.

    Completeness4/5

    The toolset covers the core lifecycle for trading: market data, account balances, order placement/retrieval/cancellation, and internal transfers. The main gap is external deposit/withdrawal operations, though fee and network information exists, and users cannot move funds in/out of the exchange directly.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues

    Resources