Skip to main content
Glama
dwin-gharibi

ramzinex-mcp

by dwin-gharibi
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

Related Servers

Alternatives to ramzinex-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
      -
    • cdcx by crypto-com

      cdcxofficial

      crypto-com
      A
      license
      Not graded
      quality
      C
      maintenance
      MCP server for the Crypto.com Exchange API, providing 86 dynamically generated tools for market data, trading, account management, and more with real-time WebSocket streaming and safety enforcement.
      40 npm
      25
      Apache 2.0

    • robinhood-mcp

      nirholas
      A
      license
      A
      quality
      B
      maintenance
      An MCP server for the Robinhood Crypto Trading API that enables real trading with 13 synthetic order types, risk controls, and durable background jobs. It provides quotes, holdings, cost basis, and over 70 tools across 8 opt-in modules.
      1
      41 npm
      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

    A4/5.0

    Scored across 45 tools

    Disambiguation5/5

    Every tool has a clearly distinct purpose, targeting different resources or actions. Even similar verbs like 'get_deposits' vs 'get_currency_deposits' vs 'get_deposit' are differentiated by scope and granularity. No two tools overlap in functionality.

    Naming Consistency5/5

    All tools follow the 'ramzinex_[verb]_[noun(s)]' pattern with consistent snake_case. Verbs are uniformly lowercase and descriptive (get, list, place, cancel, submit, confirm, edit, allocate). No mixing of conventions or inconsistent naming styles.

    Tool Count4/5

    45 tools is high but justified given the comprehensive exchange API surface. The count slightly exceeds the typical 'well-scoped' range, yet each tool corresponds to a meaningful endpoint. A few get tools could potentially be merged, but overall the count is reasonable for a full-featured exchange MCP.

    Completeness5/5

    The tool set covers the full lifecycle: public market data, account balances (summary, individual, locked), deposits and withdrawals (list, get, refresh, submit, confirm), orders (list, get, place limit/market, cancel), API key management, and account control. No obvious gaps for core trading and wallet operations.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues

    Resources