Skip to main content
Glama
Sign In
covalenthq

GoldRush MCP Server

by covalenthq
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Related Servers

Alternatives to GoldRush MCP Server

No user-submitted related servers found.

    Related Servers

    • Ankr Agent RPC

      w3tech
      A
      license
      A
      quality
      B
      maintenance
      Enables AI agents to query blockchain data across EVM chains and Sui through token-efficient MCP tools, including balances, transactions, logs, NFTs, token prices, and Sui objects/events, with optional TORPC tiered ABI decoding.
      25
      MIT

    • 3xpl MCP Server

      exekerey
      A
      license
      Not graded
      quality
      D
      maintenance
      Enables LLMs to interact with blockchain data across 48 networks via the 3xpl JSON API, supporting tools for transactions, addresses, blocks, and more.
      6
      MIT
    • Vike Data MCP Server by vike-io

      Vike Data MCP Serverofficial

      vike-io
      A
      license
      Not graded
      quality
      B
      maintenance
      Enables AI agents to query crypto data through a hosted remote endpoint: on-chain wallet and token analytics across Ethereum, BNB Chain, Base and HyperEVM, Hyperliquid perp positions and market stats, cohort-based long/short positioning, and Polymarket markets and smart-money flows. Connects via OAuth 2.1 or an API key header from Claude, Cursor, VS Code, and other MCP clients.
      MIT

    • Nerve RPC MCP

      NerveNetwork
      F
      license
      Not graded
      quality
      D
      maintenance
      Exposes Nerve blockchain JSON-RPC and REST APIs as MCP tools, enabling AI agents to receive, pay, swap, and query balances with local account management and no gas fees.
      1
      -
    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 27 tools

    Disambiguation3/5

    Several tools have overlapping purposes, e.g., various balance tools (token_balances, historical_token_balances, multichain_balances, native_token_balance) and multiple transaction tools (transaction, transactions_for_address, bitcoin_transactions). While descriptions clarify parameters, an agent could easily misselect the wrong tool for a given task.

    Naming Consistency4/5

    Tool names follow a consistent snake_case pattern with descriptive verb_noun structure. Minor deviations include 'for' prepositions (e.g., transactions_for_address, nft_for_address) but overall naming is predictable and clear.

    Tool Count3/5

    27 tools exceeds the typical well-scoped range (3-15). While the server covers a broad domain (Bitcoin, EVM, NFTs, tokens, blocks, etc.), the count feels heavy and may overwhelm agents. Some consolidation could improve efficiency.

    Completeness4/5

    The tool surface is comprehensive for a read-only blockchain data API, covering balances, transactions, blocks, tokens, NFTs, gas, pools, historical data, and approvals. Missing operations like token price current or write actions are intentional due to the server's purpose, but minor gaps exist (e.g., no dedicated current price endpoint).

    Maintenance

    ActivityInactive
    ResponsivenessNo issues

    Resources