Blocknative MCP Server

Most developer tooling work still happens through a UI a human drives. Blocknative MCP server moves it into the conversation instead. An MCP server that provides real-time gas price predictions across multiple blockchains.

The short version

• predict_gas_price: Fetches gas price predictions for a specified chain (default: Ethereum Mainnet, chain_id=1), including base fee and a table with confidence levels, price, max priority fee, and max fee
• estimate_gas_cost: Estimates transaction costs based on gas limit, confidence level, and chain ID, returning costs in Gwei and ETH
• get_supported_chains: Lists supported blockchains in a table with chain ID, system, and network
• gas_price_query: A prompt template for querying gas prices at a specific confidence level and chain ID
• Asynchronous — Uses httpx for non-blocking HTTP requests to Blocknative's Gas Price and Chains APIs
• Optional API Key — Supports low-frequency access without a Blocknative API key; high-frequency use requires setting BLOCKNATIVE_API_KEY

The tools it exposes

The server publishes 3 tools. What each one is for:

• Example — markdown
• Tools — The Tools tool exposed by this server
• Prompts — The Prompts tool exposed by this server

What it needs from you

Configuration is passed through the environment: BLOCKNATIVE_API_KEY. Treat anything key-shaped as a real credential — scope it to the minimum the server needs, and rotate it if it ever lands in a shared config.

• Python: Version 3.10 - uv: For dependency management and running the project (installation guide) - Blocknative API Key (optional): Required for high-frequency API access. Sign up at Blocknative to obtain a free API key.

Getting it running

Setup follows the usual MCP pattern — install or clone the server, register it in your client's configuration file, restart the client.

How it compares

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. Blocknative's toolset — Example, Tools, Prompts — is a fair guide to whether it matches your workflow. It is maintained by kukapay; worth a glance at recent repository activity before you build anything load-bearing on it.

This entry was verified against Blocknative's own documentation before publication; SyncDev keeps the directory reviewed rather than auto-generated.

Things to watch

• 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.
• Keep per-call confirmation enabled while you learn its behaviour; it is the cheapest safeguard you have.