Hermes Agent logo

Hermes Agent + GoldRush

By Nous Research. Runs in Terminal, Standalone.

Hermes Agent is an autonomous, self-improving agent from Nous Research that runs on servers, local machines, or cloud hosts. It combines persistent memory, shareable skills, subagents, and code execution so it can learn workflows over time instead of treating every task as stateless. Connected to GoldRush through MCP, Hermes can monitor wallets, build blockchain automations, and run recurring onchain analysis from a single long-lived agent.

Step 2: Enable MCP support

pip install "hermes-agent[mcp]"

Set up Hermes Agent with GoldRush

  1. 1Install Hermes Agent

    curl -fsSL https://raw.githubusercontent.com/NousResearch/hermes-agent/main/scripts/install.sh | bash
  2. 2Enable MCP support

    Install the MCP extras if your current Hermes environment does not already include them.

    pip install "hermes-agent[mcp]"
  3. 3Run the Hermes setup wizard

    Configure your preferred inference provider before you connect external tools.

    hermes setup
  4. 4Add GoldRush MCP server to ~/.hermes/config.yaml

    mcp_servers:
      goldrush:
        command: "npx"
        args: ["-y", "@covalenthq/goldrush-mcp-server"]
        env:
          GOLDRUSH_API_KEY: "YOUR_API_KEY"
  5. 5Start Hermes and assign a blockchain task

    Ask: "Use GoldRush to monitor this wallet, summarize new transfers every hour, and remember the reporting format I prefer"

    hermes

Things to ask Hermes Agent

Once GoldRush is connected, ask in plain words. Hermes Agent picks the calls.

  • “Create a reusable Hermes skill for wallet portfolio analysis with GoldRush”
  • “Spawn subagents to compare token balances across Ethereum, Base, and Arbitrum”
  • “Set up a recurring wallet monitor and notify me when transfers exceed a threshold”
  • “Use GoldRush to build a daily markdown report for this treasury wallet”
  • “Write and execute code that classifies this wallet's recent transactions”
  • “Remember my preferred chain list and reporting layout for future GoldRush tasks”
  • “Investigate suspicious token approvals for this address and summarize the risk”
  • “Run a chain-by-chain analysis and aggregate the results into one report”

Common workflows

  • Persistent wallet monitoring

    1. Configure GoldRush once in ~/.hermes/config.yaml
    2. Ask Hermes to watch a wallet and remember your preferred alert format
    3. Let Hermes call GoldRush on a schedule and store the workflow as a skill
    4. Reuse the same long-running agent instead of rebuilding context each session
  • Parallel multi-chain analysis

    1. Give Hermes a wallet or protocol to analyze
    2. Ask it to spawn subagents for different chains or data domains
    3. Each subagent queries GoldRush independently and reports back
    4. Hermes merges the findings into a single summary or action plan
  • Teach Hermes a GoldRush skill

    1. Solve a real blockchain task end-to-end with Hermes once
    2. Ask it to package the winning approach into a reusable skill
    3. Store the skill so future GoldRush tasks start from working procedure, not scratch
    4. Share that skill across environments if your team reuses the same workflow
  • Server-side blockchain automation

    1. Deploy Hermes on a VPS or server environment
    2. Connect GoldRush through MCP and set the required API key
    3. Run long-lived treasury, whale-tracking, or compliance workflows
    4. Use Hermes memory to keep user preferences and reporting conventions stable

The 37 MCP tools Hermes Agent can call

Each tool is a GoldRush API call or analytics query. Hermes Agent reads the descriptions and picks the tools a request needs.

Cross-chain

  • multichain_balances

    Fetch spot and historical balances for an address on up to 10 EVM chains.

  • multichain_transactions

    Fetch paginated transactions for up to 10 addresses and 10 chains.

  • multichain_address_activity

    Locate chains an address is active on with a single API call.

Balances

  • token_balances

    Get native and ERC20 token balances with spot prices and metadata.

  • historical_token_balances

    Get token balances at a specific block height or date.

  • historical_portfolio_value

    Get daily portfolio balance broken down by token.

  • erc20_token_transfers

    Get transfer-in and transfer-out events with historical prices.

  • token_holders

    Get paginated current or historical holders of a token.

  • native_token_balance

    Get native token balance with current market value.

Transactions

  • transaction

    Fetch a single transaction with decoded log events.

  • transaction_summary

    Get earliest/latest transactions and count for a wallet.

  • transactions_for_address

    Get paginated transactions with decoded logs for an address.

  • transactions_for_block

    Get all transactions in a block with decoded events.

Bitcoin

  • bitcoin_hd_wallet_balances

    Get balances for child addresses from an HD wallet xpub key.

  • bitcoin_transactions

    Get full transaction history for a Bitcoin wallet.

  • bitcoin_non_hd_wallet_balances

    Get balance for a non-HD Bitcoin address.

NFTs

  • nft_for_address

    Get ERC721 and ERC1155 NFTs held by an address.

  • nft_check_ownership

    Verify NFT ownership within a collection.

  • nft_check_ownership_token_id

    Verify ownership of a specific NFT by token ID.

Pricing

  • historical_token_prices

    Get historical prices for ERC20 and native tokens.

  • pool_spot_prices

    Get spot prices for a Uniswap V2/V3 pool.

Security

  • token_approvals

    Get token approvals categorized by spender with risk levels.

Utility

  • gas_prices

    Get real-time gas estimates for low, medium, and high speeds.

  • block

    Fetch a single block with timestamp, tx count, and miner info.

  • block_heights

    Get block heights within a date range.

  • log_events_by_address

    Get event logs emitted from a contract address.

  • log_events_by_topic

    Get event logs by topic hash across all contracts.

  • resolve_address

    Resolve an ENS, RNS or Unstoppable Domains name to an address.

Protocol analytics

  • list_entities

    List every dataset with live analytics, with its metrics and dimensions.

  • search_catalog

    Find a dataset, metric, dimension or ticker before querying it.

  • get_metadata

    Read what a dataset's metrics measure, how they split and what they can't answer.

  • get_metric

    Get one metric of a dataset as a daily, weekly or monthly series.

  • get_metrics

    Get several metrics of one dataset in a single call.

  • get_breakdown

    Split a metric by a dimension such as chain, asset or market.

  • list_members

    List the values a dimension holds, ranked, to filter on one of them.

  • compare_entities

    Compare two to ten named datasets on one metric.

  • rank_entities

    Rank every dataset that serves a metric.

GoldRush Agent Skills

Agent Skills give your agent the context it needs for every GoldRush endpoint: parameters, response shapes and credit costs. One command installs all of them.

npx skills add covalenthq/goldrush-agent-skills
  • Foundational API

    REST endpoints for historical blockchain data. Balances, transactions, NFTs, token prices, security checks, cross-chain queries across 100+ networks.

  • x402

    Pay-per-request access without API keys. Agents pay with stablecoins using the HTTP 402 protocol. No accounts, no rate limits, no key management.

  • CLI

    Terminal-first blockchain data with native MCP support. 17 commands that work for both humans and AI agents.

Tips

  • Keep GoldRush in the Hermes YAML config so long-running agents can restart without losing tool access
  • Teach Hermes one good wallet-analysis pattern and convert it into a reusable skill quickly
  • Use subagents for per-chain or per-wallet fanout instead of forcing one conversation to do all analysis serially
  • Hermes is strongest when it stays alive over time, so prefer server deployment for recurring blockchain automation

Troubleshooting

Hermes is not showing any MCP tools
Make sure the MCP extras are installed and that the mcp_servers section is valid YAML. If needed, run pip install "hermes-agent[mcp]" again in the same environment Hermes uses.
GoldRush MCP tool calls time out
Increase the MCP timeout in ~/.hermes/config.yaml, paginate large blockchain queries, and avoid asking Hermes to fetch huge multi-chain datasets in one call.
Hermes cannot start the GoldRush server
Ensure Node.js and npx are installed on the host where Hermes runs. Test npx -y @covalenthq/goldrush-mcp-server manually to confirm the binary and API key are available.

More agents

  • Claude Code

    Anthropic's agentic coding tool that lives in your terminal and understands your codebase end-to-end.

  • Codex

    OpenAI's cloud-native coding agent that runs tasks in a sandboxed environment with full autonomy.

  • Gemini CLI

    Google's open-source terminal AI agent powered by Gemini models with built-in MCP support and a file-based skill system.

See every agent

Hermes Agent and GoldRush FAQ

Yes. Hermes supports MCP servers through the mcp_servers section in ~/.hermes/config.yaml, so GoldRush can be exposed as a first-class tool without custom glue code.