mcpField
C
Covalent

Covalent

Remote
pipeworx.ioFinance0Updated 5d ago

About Covalent

Covalent wraps the Covalent/GoldRush on-chain data API as an MCP server for agents that need wallet and token data across chains. It provides balance, transaction, and token-holder queries and requires users to supply their own API key.

Key features

  1. 01Query wallet token balances with USD values
  2. 02Retrieve recent wallet transactions
  3. 03Find top holders of a token contract
  4. 04Cover more than 100 chains

Use cases

  1. 01Review assets held by a wallet on a chain
  2. 02Analyze recent address transactions and gas
  3. 03Identify large holders of a token

MCP support

It exposes cross-chain balance, transaction, and token-holder query tools to MCP clients. It can connect through Pipeworx or run locally over stdio; tool calls require the user's own API key.

Configuration

Remote servers need no local install. Pick your client, then copy the config or install in one click.

Endpointhttps://gateway.pipeworx.io/covalent/mcp
Copy install command
Claude CodeTerminal
Cursor.cursor/mcp.json
VS Code.vscode/mcp.json
Claude Desktopclaude_desktop_config.json
Windsurf~/.codeium/windsurf/mcp_config.json

Run commands in a terminal; paste JSON into the client’s MCP config and restart. Servers that need sign-in will prompt on first connect.

Tools

Details

From the project README

mcp-covalent

Covalent / GoldRush MCP — unified wallet balances + transactions across 100+ chains (goldrush.dev, formerly covalenthq.com)

Part of Pipeworx — an MCP gateway connecting AI agents to 1875+ live data sources. This is an independent, unofficial integration — not affiliated with, endorsed by, or published by the upstream provider.

Tools

ToolDescription
covalent_token_balancesToken balances for wallet X on chain Y — every ERC-20/native token held by an address, with USD quotes. Works across 100+ chains via Covalent/GoldRush. Example: covalent_token_balances({ address: "0xd8dA6BF26964aF9D7eEd9e03E53415D37aA96045", chain: "eth-mainnet", _apiKey: "your-key" })
covalent_transactionsRecent transactions for wallet X on chain Y — latest on-chain transactions for an address with USD-valued amounts and gas. Works across 100+ chains via Covalent/GoldRush. Example: covalent_transactions({ address: "0xd8dA6BF26964aF9D7eEd9e03E53415D37aA96045", chain: "eth-mainnet", _apiKey: "your-key" })
covalent_token_holdersTop holders of token X on chain Y — the largest wallet holders of an ERC-20 token contract, with balances. Works across 100+ chains via Covalent/GoldRush. Example: covalent_token_holders({ token_address: "0xA0b86991c6218b36c1d19D4a2e9Eb0cE3606eB48", chain: "eth-mainnet", _apiKey: "your-key" })

Quick Start

Add to your MCP client (Claude Desktop, Cursor, Windsurf, etc.):

{
  "mcpServers": {
    "covalent": {
      "url": "https://gateway.pipeworx.io/covalent/mcp"
    }
  }
}
What this endpoint actually serves

tools/list at https://gateway.pipeworx.io/covalent/mcp returns the tools in the table above plus the shared Pipeworx meta-tools — ask_pipeworx, discover_tools, search_within, remember/recall and the rest of the gateway-wide set. So the tool count you see is larger than this table: a single-pack endpoint currently lists roughly 30 shared tools alongside the pack's own. The connection's initialize response states its exact scope, and is the authoritative answer for a given day.

This is deliberate, not multiplexing by accident. The meta-tools are what let a scoped connection answer a question this pack does not cover — via ask_pipeworx, which routes across the whole catalog — without you adding a second MCP server. There is currently no way to mount a pack endpoint without them; if the extra schemas cost you more context than the routing is worth, connect to the full gateway once rather than to several pack endpoints.

Or connect to the full Pipeworx gateway to get every pack's tools listed directly, instead of just this one's:

{
  "mcpServers": {
    "pipeworx": {
      "url": "https://gateway.pipeworx.io/mcp"
    }
  }
}

Both URLs reach the same gateway and the same 1875+ data sources. The only difference is which pack's tools are listed directly; ask_pipeworx reaches all of them from either one.

No MCP client? Call it over HTTP

This pack takes your own API key (_apiKey) — we don't front one for it, so there's no curl here that would run without it. Inspect any tool: GET https://gateway.pipeworx.io/v1/tools/covalent_token_balances. Find one: POST https://gateway.pipeworx.io/v1/tools/search_packs with {"query":"..."}.

Standalone (no gateway account)

This package also runs as a local stdio MCP server — no Pipeworx account, no gateway round-trip:

{
  "mcpServers": {
    "covalent": {
      "command": "npx",
      "args": ["-y", "@pipeworx/mcp-covalent"]
    }
  }
}

Or run it directly to confirm it starts:

npx -y @pipeworx/mcp-covalent

It speaks MCP over stdin/stdout and answers initialize/tools/list/tools/call for only this pack's tools — none of the shared meta-tools the gateway connection above adds. Same source, same tools, no ask_pipeworx routing.

Using with ask_pipeworx

Instead of calling tools directly, you can ask questions in plain English — this works on the pack endpoint above as well as on the full gateway:

ask_pipeworx({ question: "your question about Covalent data" })

The gateway picks the right tool and fills the arguments automatically.

More

License

MIT

Comments

Markdown supported

New to MCP?

From what the protocol is to installing your first server, these answers cover most first questions.

An open protocol that defines how AI applications connect to external tools and data in a uniform way. Clients talk to the model; MCP servers provide tools, resources and prompt templates. They exchange standard messages, so one server can be reused by many clients.