GoldRush MCP Server

GoldRush MCP server is a locally run integration for AI assistants that speak the Model Context Protocol. Blockchain data across 100+ chains — wallet balances, token prices, transactions, DEX pairs, and more. REST API, real-time WebSocket with OHLCV price feeds, CLI, and x402 pay-per-request.

What you get

Model Context Protocol (MCP) is a message protocol for connecting context or tool-providing servers with LLM clients. This server allows an LLM client to:

• Call Covalent GoldRush API endpoints as MCP Tools
• Read from MCP Resources that give chain info, quote currencies, chain statuses, etc
• Flexible Transport Support — Unified server supporting both STDIO and HTTP transports
• Command-line Interface — Easy configuration via CLI arguments
• Fully testable with Vitest for testing each group of tools
• Modular architecture where each service is implemented as a separate module, making the codebase easier to maintain and extend

Setting it up

@covalenthq/goldrush-mcp-server on npm is all you need. Most clients run it directly, so configuration is a few lines and a restart.

Configuration and credentials

You will need 2 environment variables: GOLDRUSH_API_KEY, YOUR_GOLDRUSH_API_KEY. The server will not start without them, which is usually why the tools fail to appear on a first run. Keep credentials in your client's env block or a secrets manager rather than in a file you might commit.

Choosing this one

Among the developer tooling options, the useful question is rarely "what can it do" but "what does it cost you to run" — permissions, credentials, and how much of your context its toolset consumes.

SyncDev reviews every entry in this directory against the project's own documentation before publishing, and revisits them as servers change.

Before you rely on it

• It runs with your machine's permissions. That is convenient and also the reason to think about what you point it at before you approve a tool call.
• Missing credentials fail quietly in some clients — if no tools show up, check the environment block first.
• MCP clients confirm each tool call by default. Leave that on until you have watched what the goldrush mcp server does with a few real requests.