Skip to main content
Glama
ellermanj

coinspot-mcp

by ellermanj
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

Related Servers

Alternatives to coinspot-mcp

No user-submitted related servers found.

    Related Servers

    • Binance MCP

      UpperMoon0
      A
      license
      Not graded
      quality
      B
      maintenance
      Enables secure access to Binance public market data and authenticated account information through a compact set of MCP tools, with optional trading operations that can be explicitly enabled.
      MIT

    • CoinCap MCP Server

      CC3-0
      F
      license
      C
      quality
      C
      maintenance
      Provides access to CoinCap's cryptocurrency market data and technical analysis tools via MCP, supporting assets, exchanges, markets, and more.
      38
      22 npm
      7
      -

    • mcp-cryptocompare

      pipeworx-io
      A
      license
      Not graded
      quality
      D
      maintenance
      Enables fetching cryptocurrency prices, historical OHLC data, and news via CryptoCompare API through an MCP gateway.
      88 npm
      MIT

    • crypto_mcp

      DressPD
      F
      license
      C
      quality
      D
      maintenance
      Provides cryptocurrency market data (prices, symbols) and a gated demo trading flow via MCP tools, with safety defaults like dry-run and confirmation gates.
      6
      -

    • Toss Invest MCP

      takeachangs
      F
      license
      A
      quality
      D
      maintenance
      Enables MCP clients to read Toss Securities market data and account info, and optionally place real-money orders.
      20
      -
    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

    B3.2/5.0

    Scored across 28 tools

    Disambiguation3/5

    Several tools overlap across public, private, and read-only variants, such as get_open_orders, get_my_open_market_orders, and get_readonly_market_open_orders. History tools like get_my_order_history and get_my_market_order_history also have subtle boundaries. Descriptions help, but an agent could still misselect among credential-scoped or history-scoped endpoints.

    Naming Consistency5/5

    All tool names use consistent snake_case with clear verb_noun structure such as get_, check_, and quote_. Prefixes like get_my_ and get_readonly_ are used systematically to indicate credential or account scope. The naming is predictable throughout the set.

    Tool Count2/5

    With 28 tools, the surface is too large for the apparent domain and includes many parallel variants. Public, authenticated, and read-only versions multiply similar operations without enough differentiation. This exceeds the reasonable 3-15 tool range for a coherent MCP server.

    Completeness3/5

    The server covers market data, balances, order history, deposits, withdrawals, and quote generation well. However, it lacks actual trade execution and order cancellation despite having full-access credential checks and buy/sell/swap quote tools. These are notable gaps for a CoinSpot trading-oriented server.

    Resources