mcpField
M
mcp-blockchain-fees

mcp-blockchain-fees

Local
github.com/CryptoAPIs-ioFinance0Updated 5w ago

About mcp-blockchain-fees

mcp-blockchain-fees is a Crypto APIs MCP server for fee recommendations and transaction estimates across UTXO, EVM, XRP, Tezos, and Solana chains. It is for developers estimating fees or gas and compute units for supported transfers and calls.

Key features

  1. 01UTXO fee recommendations and estimation
  2. 02EVM fees, EIP-1559, and gas estimates
  3. 03XRP fee recommendations
  4. 04Tezos transfer fee estimates
  5. 05Solana fee and compute-unit estimates

Use cases

  1. 01Compare slow, standard, and fast fee levels
  2. 02Estimate gas for token or contract operations
  3. 03Estimate Tezos or Solana transfer requirements

MCP support

Exposes Crypto APIs fee recommendations and transaction-estimation operations as tools for MCP clients. A Crypto APIs API key is required.

Configuration

Local server config is the same for every client. Copy it into your client’s MCP config file.

mcp.json · Universal config
{
"mcpServers": {
"cryptoapis-io-mcp-blockchain-fees": {
"command": "npx",
"args": [
"-y",
"@cryptoapis-io/mcp-blockchain-fees"
],
"env": {
"CRYPTOAPIS_API_KEY": "<CRYPTOAPIS_API_KEY>"
}
}
}
}
Run commandnpx -y @cryptoapis-io/mcp-blockchain-fees
Environment variables to set
CRYPTOAPIS_API_KEYSecretCrypto APIs API key

Local servers need a runtime on your machine (e.g. Node.js 18+). Config file locations differ by client; see your client’s docs.

Packages
npm@cryptoapis-io/mcp-blockchain-fees0.5.1

Tools

6

Saved tool list · updated 3w ago

ParameterTypeRequiredDescription
actionenumYesAction to performget-fee-recommendations | estimate-transaction-smart-fee
contextstringNoOptional context for the request - echoed back in response
networkenumYesNetwork namemainnet | testnet
blockchainenumYesBlockchain protocolbitcoin | bitcoin-cash | litecoin | dogecoin | dash | zcash
feeRatePrioritystringNoFee rate priority: ECONOMICAL or CONSERVATIVE (estimate-transaction-smart-fee only)
confirmationTargetintegerNoTarget number of blocks for confirmation (estimate-transaction-smart-fee only)

Details

From the project README

@cryptoapis-io/mcp-blockchain-fees

MCP server for Crypto APIs Blockchain Fees product. Fee recommendations and gas estimates for UTXO, EVM, XRP, Tezos, and Solana blockchains.

API Version: Compatible with Crypto APIs version 2024-12-12

Features

  • UTXO fee recommendations and smart fee estimation (Bitcoin, Bitcoin Cash, Litecoin, Dogecoin, Dash, Zcash)
  • EVM fee recommendations, EIP-1559 fees, and gas estimation for transfers and contract calls
  • XRP fee recommendations
  • Tezos fee recommendations and fee estimation for native XTZ, FA1.2, and FA2 transfers
  • Solana fee recommendations and compute-unit estimation for native SOL transfers, SPL token transfers, and arbitrary program invocations

Prerequisites

Installation

npm install @cryptoapis-io/mcp-blockchain-fees

Or install all Crypto APIs MCP servers: npm install @cryptoapis-io/mcp

Usage

# Run with API key
npx @cryptoapis-io/mcp-blockchain-fees --api-key YOUR_API_KEY

# Or use environment variable
export CRYPTOAPIS_API_KEY=YOUR_API_KEY
npx @cryptoapis-io/mcp-blockchain-fees

# HTTP transport (listens on 127.0.0.1; see "Exposing the server beyond localhost")
npx @cryptoapis-io/mcp-blockchain-fees --transport http --port 3000 --api-key YOUR_API_KEY
Claude Desktop

Add to your Claude Desktop config (~/Library/Application Support/Claude/claude_desktop_config.json on macOS, %APPDATA%\Claude\claude_desktop_config.json on Windows):

{
  "mcpServers": {
    "cryptoapis-blockchain-fees": {
      "command": "npx",
      "args": ["-y", "@cryptoapis-io/mcp-blockchain-fees"],
      "env": {
        "CRYPTOAPIS_API_KEY": "your_api_key_here"
      }
    }
  }
}
Cursor

Add to .cursor/mcp.json (project) or ~/.cursor/mcp.json (global):

{
  "mcpServers": {
    "cryptoapis-blockchain-fees": {
      "command": "npx",
      "args": ["-y", "@cryptoapis-io/mcp-blockchain-fees"],
      "env": {
        "CRYPTOAPIS_API_KEY": "your_api_key_here"
      }
    }
  }
}
MCP Inspector
npx @modelcontextprotocol/inspector npx @cryptoapis-io/mcp-blockchain-fees --api-key YOUR_API_KEY
n8n
  1. Start the server in HTTP mode:
    npx @cryptoapis-io/mcp-blockchain-fees --transport http --port 3000 --api-key YOUR_API_KEY
    
  2. In your n8n workflow, add an AI Agent node
  3. Under Tools, add an MCP Client Tool and set the URL to http://localhost:3000/mcp

n8n in Docker: localhost inside the container is not your machine. Start the server with --host 0.0.0.0 and MCP_AUTH_TOKEN set (see Exposing the server beyond localhost), use http://host.docker.internal:3000/mcp as the URL, and add an Authorization: Bearer <token> header to the MCP Client Tool credential.

All servers default to port 3000. Use --port to assign different ports when running multiple servers.

Available Tools

blockchain_fees_utxo

Fee recommendations for UTXO blockchains (Bitcoin, Bitcoin Cash, Litecoin, Dogecoin, Dash, Zcash).

ActionDescription
get-fee-recommendationsGet fee recommendations (slow, standard, fast)
estimate-transaction-smart-feeEstimate smart fee for a target confirmation time
blockchain_fees_evm

Fee recommendations and gas estimation for EVM blockchains.

ActionDescription
get-fee-recommendationsGet fee recommendations (slow, standard, fast)
get-eip-1559-fee-recommendationsGet EIP-1559 fee recommendations (base fee, priority fee)
estimate-native-coin-transfer-gasEstimate gas for native coin transfer
estimate-token-transfer-gasEstimate gas for token transfer
estimate-contract-interaction-gasEstimate gas for contract interaction
blockchain_fees_xrp

Fee recommendations for XRP (mainnet, testnet).

ActionDescription
get-fee-recommendationsGet XRP fee recommendations
blockchain_fees_tezos

Fee recommendations and fee estimation for Tezos (mainnet, shadownet).

ActionDescription
get-fee-recommendationsGet current minimal fee/cost rates from the mempool
estimate-transferEstimate the fee for a native XTZ transfer
estimate-fa12-transferEstimate the fee for an FA1.2 token transfer
estimate-fa2-transferEstimate the fee for an FA2 token transfer
blockchain_fees_solana

Fee recommendations and compute-unit estimation for Solana (mainnet, devnet).

ActionDescription
get-fee-recommendationsGet current priority fee recommendations from the mempool
estimate-native-coin-transfer-compute-unitsEstimate compute units for a native SOL transfer
estimate-token-transfer-compute-unitsEstimate compute units for an SPL token transfer
estimate-program-invocation-compute-unitsEstimate compute units for an arbitrary program instruction call

CLI Arguments

ArgumentDescriptionDefault
--api-keyCrypto APIs API keyCRYPTOAPIS_API_KEY env var
--transportTransport type: stdio or httpstdio
--hostHTTP host (use 0.0.0.0 to accept remote connections — requires an auth token with --api-key)127.0.0.1
--auth-tokenBearer token callers must send (Authorization: Bearer <token>); prefer the MCP_AUTH_TOKEN env varMCP_AUTH_TOKEN env var
--allowed-hostsComma-separated Host header allowlist for non-loopback binds—
--portHTTP port3000
--pathHTTP path/mcp
--statelessEnable stateless HTTP modefalse
HTTP API Key Modes

When using HTTP transport, the server supports two API key modes:

  • With --api-key: The key is used for all requests. x-api-key request headers are ignored.
  • Without --api-key: Each request must include an x-api-key header with a valid Crypto APIs key. This enables hosting a public server where each user provides their own key.
# Per-request key mode (multi-tenant)
npx @cryptoapis-io/mcp-blockchain-fees --transport http --port 3000
# Clients send x-api-key header with each request
Exposing the server beyond localhost

HTTP mode listens on 127.0.0.1 by default, so only processes on the same machine can reach it. To accept connections from other machines or containers, bind explicitly and protect the port:

# Startup-key mode: callers must present the token (the server refuses to start without one)
export MCP_AUTH_TOKEN=$(openssl rand -hex 32)
npx @cryptoapis-io/mcp-blockchain-fees --transport http --host 0.0.0.0 --port 3000 --api-key YOUR_API_KEY \
  --allowed-hosts mcp.internal.example
# Clients send: Authorization: Bearer $MCP_AUTH_TOKEN

# Per-request key mode: no startup key, every request must carry the caller's own x-api-key
npx @cryptoapis-io/mcp-blockchain-fees --transport http --host 0.0.0.0 --port 3000

--allowed-hosts restricts the Host header (DNS rebinding protection) when not bound to loopback. Prefer MCP_AUTH_TOKEN over --auth-token: command-line arguments are visible in the process list.

Stdio transport always requires an API key at startup.

Important: API Key Required

Warning: Making requests without a valid API key — or with an incorrect one — may result in your IP being banned from the Crypto APIs ecosystem. Always ensure a valid API key is configured before starting any server.

Remote MCP Server

Crypto APIs provides an official remote MCP server with all tools available via HTTP Streamable transport at https://ai.cryptoapis.io/mcp. Pass your API key via the x-api-key header — no installation required.

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.