Developer Tools & Devops · Blocknative + Claude
Blocknative MCP with Claude: Live Mempool Monitoring and Transaction Tracking for Teams
The short answer
Claude connects to Blocknative through the Model Context Protocol (MCP) or Blocknative's direct API, using an API key. Once connected, Claude can read live mempool activity, follow pending transactions, analyse gas fees and report status changes when someone asks in natural language. Consequential actions can be held for human approval.
What is Blocknative?
Blocknative provides real-time mempool monitoring and transaction management for public blockchains. The mempool is the waiting area where transactions sit before they are confirmed on-chain. Blocknative shows teams what is pending, how fees are moving and when a transaction changes state. It is used by blockchain developers, decentralised application teams, trading and operations teams, and businesses that depend on reliable on-chain transactions.
How Claude connects to Blocknative through MCP
The Model Context Protocol is an open standard that lets Claude securely use other software, reading information and taking actions with permissions the organisation controls. Think of it as a universal adapter between Claude and the tool. For Blocknative, this means Claude can work with live transaction data without anyone copying figures by hand.
Once connected, Claude can typically look up pending transactions, check gas fee levels, review how a transaction's status has changed and summarise activity over a period. A team member can ask a question such as which transactions from a given wallet are still waiting, and receive a clear answer in plain English.
Access is controlled by the API key, which can be scoped and rotated by the organisation. Claude works only within the permissions granted. Where a workflow would change something important, such as adjusting a transaction, people approve the step before it happens, and every action is recorded in audit logs so the team stays in charge.
What you can automate
Watching payment settlements
Finance and operations teams often wait for on-chain payments to confirm. Claude can check the status of named transactions in Blocknative and report whether each one is still pending, confirmed or replaced, so staff do not need to refresh dashboards manually.
Gas fee analysis for treasury teams
Teams that send regular blockchain transactions want to avoid overpaying for fees. Claude can review current and recent gas fee levels and summarise when activity tends to be cheaper or busier, helping treasury staff plan when to submit non-urgent transfers.
Monitoring launches and high-traffic events
Product and engineering teams running token sales or new contract launches need to see demand building. Claude can track pending transaction volumes during the event and flag unusual spikes or stuck transactions to the on-call engineer.
Incident triage for developers
When a user reports that a blockchain action has not gone through, developers can ask Claude to find the transaction, show its status history and explain whether it is pending, dropped or failed, cutting the time spent searching through raw data.
Management reporting
Operations leaders often need a regular view of blockchain activity. Claude can pull together a plain-English summary of transaction volumes, fee trends and status changes for a weekly or monthly update, prepared for review before it is shared.
An end-to-end workflow: Payment confirmation and exception alert
TriggerA customer payout is submitted on-chain and a finance analyst asks Claude to track it, or a scheduled check runs every hour.
Claude retrieves the pending transaction from Blocknative using the transaction hash supplied by the payments system.
Claude checks the transaction's status and current gas fee position and records the result.
If the transaction is still pending beyond an agreed threshold, Claude drafts an alert describing the delay and the fee level.
The alert is posted to the finance team's ticketing system, where an analyst reviews it and approves any follow-up action.
Once the transaction is confirmed, Claude updates the payout record in the ERP system and closes the ticket.
OutcomeFinance teams see payment status in one place, delays are caught early, and reconciliation is faster, with a named person approving every follow-up step.
How we set it up
Free automation audit
We review how your team tracks blockchain transactions today and identify the workflows where live Blocknative data would save time or reduce risk.
Secure connection
We connect Claude to Blocknative using your API key, or through the direct API where that suits your setup. The key is stored securely and access is limited to what each workflow needs.
Workflow design
We design the end-to-end process across Blocknative and your other systems such as Microsoft 365, CRM, ERP or ticketing, deciding which steps run automatically and which need human approval.
Testing against real cases
We test the workflow against past transactions and known scenarios to confirm the answers and alerts are accurate before anything goes live.
Launch and training
We launch with monitoring and audit logs in place, then train your team on how to ask questions, review alerts and manage access over time.
Who benefits
- Blockchain developers
- Faster diagnosis of stuck or failed transactions without manual searching through raw mempool data.
- Finance and treasury leads
- Clear, plain-English visibility of payment status and gas fee levels to plan transfers more cost-effectively.
- Operations and support managers
- Quicker answers to customer questions about blockchain transactions, with fewer escalations to engineers.
- IT and security leaders
- Controlled, scoped access through API keys, with audit logs that show what was read and what was done.
Security and control
- API keys are stored securely, scoped to the minimum access needed, and rotated on a schedule your team sets.
- Claude works only within the permissions granted, and read-only access is used wherever it is enough.
- Consequential actions require human approval before they are carried out.
- Every interaction is recorded in audit logs so the team can review what was asked, read and changed.
- Workflows are tested against real cases before launch, and monitored after go-live.
For teams in the US, UK, India and the Middle East
Organisations in the United States and the United Kingdom can host the Claude workflow in their chosen region to meet internal data handling policies. Companies in India must consider the Digital Personal Data Protection Act, 2023, when personal data is involved, and we design with that in mind. Businesses in the Middle East, including the UAE and Saudi Arabia, are subject to local data protection laws, and we choose hosting regions to meet those requirements. Hosting location is always selected during design to match your compliance needs, and we do not guarantee any particular regulatory outcome.
Learn more about Claude and MCP
Anthropic's AI model and assistant.
Secure links between Claude and business tools.
How engineers build and change software with Claude.
Hosted agents that run multi-step work.
The open standard Claude uses to connect to tools.
Frequently asked questions
What does the Blocknative MCP server do?
The Blocknative MCP server is a bridge that lets AI tools such as Claude use Blocknative's data in a controlled way. Through it, Claude can ask about pending transactions, gas fees and status changes using natural language, instead of a team member building queries by hand. Access is limited to the permissions the API key allows.
Is connecting Claude to Blocknative secure?
Security depends on how the connection is set up. We use an API key that can be scoped, stored securely and rotated, and we apply least-privilege access so Claude sees only what each workflow needs. Audit logs record activity, and sensitive actions can require human approval before they run.
What can Claude actually do with Blocknative?
Typically, Claude can monitor mempool activity, look up specific pending transactions, analyse gas fee levels, detect when a transaction's status changes and summarise activity over a period. What it can do in your organisation depends on the permissions and workflows we agree during the audit and design stages.
How long does setup take?
Timing varies with the number of workflows and the systems involved. A focused single workflow often takes a few weeks from audit to launch, including testing and team training. Broader programmes covering several systems take longer. We confirm a realistic timeline during the free automation audit.
Which plan or permissions do I need?
You need an API key from your Blocknative account with access to the data your workflows require. The exact access level depends on what your account allows, so we check this during the audit. Our role is to design the connection around the access you already have, with least-privilege settings.