Skip to main content
Glama
CoinRithm

CoinRithm/coinrithm-agent-trading

Official

Related Servers

Alternatives to CoinRithm/coinrithm-agent-trading

  • A
    license
    B
    quality
    A
    maintenance
    Alpaca’s official MCP Server lets you trade stocks, ETFs, crypto, and options, run data analysis, and build strategies in plain English directly from your favorite LLM tools and IDEs
    72
    11,500 PyPI
    1,047
    MIT
  • A
    license
    A
    quality
    D
    maintenance
    Trade, analyze, and automate Polymarket prediction markets via AI. 34 tools for direct trading, smart money flow, copy trading, backtest, and portfolio management.
    48
    50 npm
    16
    MIT

Related Servers

  • A
    license
    B
    quality
    D
    maintenance
    Enables AI agents to trade crypto with paper money, access market data, view leaderboards, and manage trading bots via an MCP-compatible interface.
    16
    MIT
  • A
    license
    A
    quality
    B
    maintenance
    Enables AI agents to paper-trade on Polymarket against live order books with realistic fees and fill mechanics, including market search, portfolio tracking, and strategy backtesting.
    33
    1,078 PyPI
    493
    MIT
  • F
    license
    Not graded
    quality
    C
    maintenance
    Enables agents to access live crypto market data and execute risk-controlled paper trades through standardized MCP tool calls.
    -
  • A
    license
    Not graded
    quality
    A
    maintenance
    Provides a safe paper-trading twin of the Binance Agent OS MCP API so agents can be rehearsed, scored, gated for go-live, and shadow-compared against live calls without using real funds.
    MIT
  • F
    license
    A
    quality
    C
    maintenance
    Enables agents to generate alpha signals, retrieve market snapshots, compute portfolio risk, validate and submit paper orders, and trigger a kill switch, all under deterministic pre-trade risk controls and audit logging.
    5
    -

TDQS

A3.8/5.0

Scored across 49 tools

Disambiguation4/5

Most tools have sharply distinct purposes, and descriptions explicitly cross-reference each other (e.g. pm_data_orderbook says 'use pm_quote for that'). A few clusters are close enough to risk misselection: pm_data_events vs pm_data_event vs pm_data_canonical, pm_data_sources vs pm_data_sources_health, and the three whale tools (pm_data_whales / whale_wallets / whale_wallet).

Naming Consistency3/5

There is a readable scheme (pm_data_* for cross-venue reads, get_* for account reads, open_/close_/place_/cancel_ for writes), but it mixes verb-first (get_candles, list_open_orders) with noun-first (pm_quote, spot_quote, futures_quote, crypto_price, tradfi_references, instrument_markets). The mixture is legible but not a single predictable pattern.

Tool Count2/5

49 tools is heavy for a server, well past the 25-tool threshold, and the surface is padded by many niche data endpoints (calibration, volume history, whale wallets, sources health, canonical identity). While many are individually distinct, the sheer count strains an agent's ability to select well.

Completeness4/5

Coverage is broad and deep: spot/futures/PM quoting, opening, closing, SL/TP, portfolio, positions, trades, ledger, arena, plus a rich research data layer. Minor gaps exist, such as no explicit close_pm_position (PM positions appear to settle via the worker), but core lifecycles are covered.

Maintenance

ActivityActive
ResponsivenessUnresponsive