Skip to main content
Glama
salleh

Poloniex MCP

by salleh
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Related Servers

Alternatives to Poloniex MCP

No user-submitted related servers found.

    Related Servers

    • Cryptocurrency MCP Server

      Diya28-mehra
      F
      license
      Not graded
      quality
      D
      maintenance
      Python-based MCP server that provides real-time and historical cryptocurrency data from 100+ exchanges via CCXT, with tools for tickers, OHLCV, markets, and order books.
      1
      -

    • mcp-first-server

      JGPAS
      A
      license
      A
      quality
      B
      maintenance
      MCP server exposing quote and live cryptocurrency price tools, with both local (stdio) and cloud-deployed (HTTP) transports.
      2
      MIT

    • Sentinel-MCP

      AnahadhBirdh
      A
      license
      A
      quality
      C
      maintenance
      Extensible trading-intelligence MCP server with diagnostic tools, structured logging, and tool registration; currently provides server info tool with plans for market data adapters.
      1
      32 npm
      -
    • coinex-mcp-server by coinexcom

      coinex-mcp-serverofficial

      coinexcom
      A
      license
      Not graded
      quality
      F
      maintenance
      An MCP server for interacting with the CoinEx cryptocurrency exchange, enabling market data queries and authenticated trading operations via AI agents.
      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.6/5.0

    Scored across 35 tools

    Disambiguation4/5

    Each getter targets a distinct resource, and the descriptions clarify public vs. authenticated data. The main overlap is get_price vs. get_ticker, both of which return a latest price, though ticker adds 24h stats. A few account-related getters could require careful reading but are conceptually separate.

    Naming Consistency5/5

    All tools use a consistent get_<resource> snake_case pattern, which makes the family easy to recognize. The only minor variation is pluralization, but it follows the natural noun being accessed.

    Tool Count2/5

    35 tools is excessive for a single MCP server and beyond the 25-tool threshold where agent tool selection suffers. Even though each getter maps to a distinct endpoint, grouping them into market-data, account, orders, and margin servers would be cleaner.

    Completeness2/5

    The set is entirely read-only: there are no create/cancel order, place trade, transfer, or withdrawal operations. This leaves major dead ends for a general Poloniex exchange workflow, even though market data and account-read coverage is broad.

    Maintenance

    ActivitySlowing
    ResponsivenessNo issues

    Resources