X (Twitter)LinkedInGitHubDiscordYouTube

How to connect Beaconchain to Claude

Connect Claude Web, Desktop and Cowork to Beaconchain MCP. Check if your ethereum node is syncing, get health status of the beacon chain node, and more using natural language, with authentication handled for you.

Get started for freeGet a demo
Beaconchain logoBeaconchain
Api Key

Beaconchain is a real-time analytics platform for Ethereum 2.0's Beacon Chain. It provides detailed insights into validators, blocks, and overall network performance.

37 Tools

Introduction

Claude is Anthropic's AI assistant, available on the web, in the desktop app, and on mobile. Cowork is its agent for knowledge work, and it runs on all of those surfaces too. Connected to your apps, Claude can work with your files and services to accomplish complex tasks on your behalf.

This guide walks you through the easiest and most secure way to connect your Beaconchain account to Claude via Composio Connect, enabling it to check if your Ethereum node is syncing, get health status of the beacon chain node, fetch details for validator ID 12345, and more such actions on your behalf without compromising your account security.

Setup is the same on Claude Web, Desktop, and Cowork, and you only need to do it once. The connector is tied to your account, so it's available in all three.

Also integrate Beaconchain with

OpenAI Agents SDKClaude Agent SDKClaude CodeCodexOpenClawHermesAtomic AgentGoogle ADKLangChainVercel AI SDKMastra AILlamaIndexCrewAIPydantic AIAutoGen

Connecting Beaconchain to Claude Web, Desktop, and Cowork

Two ways to add the Composio connector. Pick whichever you prefer.

1. Add with one click

Click the button. Claude opens with the Composio connector filled in. Click Add, then go to step 2.

Add to Claude

Add manually

In Claude Desktop, click Customize in the left sidebar, then select Connectors and click the + icon at the top.

Claude Desktop connectors screen with Add custom connector selected

Click Add custom connector and paste in the Composio MCP server URL:

bash
https://connect.composio.dev/mcp
Add custom connector dialog with Composio MCP server URL

2. Authorize in your browser

Click Connect. You'll be redirected to a browser window where you can authorize Composio to continue.

Composio authorization screen for Claude Web, Desktop, and Cowork

3. Connect your Beaconchain account

Back in Claude, ask it to connect to Beaconchain or give it any Beaconchain-related task.

For example, ask Claude to:

  • "Check if your Ethereum node is syncing"
  • "Get health status of the beacon chain node"
  • "Fetch details for validator ID 12345"

It will prompt you to authenticate and authorize access.

That's it. Composio's tools are now available in Claude, and your Beaconchain account is ready to use.

What is the Beaconchain Claude Connector, and what's possible with it?

The Beaconchain MCP server is an implementation of the Model Context Protocol that connects your AI agent and assistants like Claude, Cursor, etc directly to your Beaconchain account. It provides structured and secure access to Ethereum 2.0 Beacon Chain analytics, so your agent can check validator status, monitor node health, analyze network performance, and surface real-time blockchain insights on your behalf.

  • Validator information lookup: Instantly retrieve in-depth details about any specific Ethereum 2.0 validator, including performance, status, and rewards.
  • Node health monitoring: Let your agent check the real-time health status of your node, including readiness, syncing state, and error conditions.
  • Network performance insights: Surface up-to-date statistics on the overall Beacon Chain network, empowering you to make informed decisions.
  • Automated health alerts: Have your agent proactively monitor node status and notify you if any issues or anomalies arise.

Troubleshooting

1. Why does Claude not use the Composio connector for Beaconchain?

The connector can show as connected, but Claude must use it in each Beaconchain conversation.

  • Click + at the lower left of the chat, or type /.
  • Hover Connectors.
  • Turn on Composio.
  • Ask Claude to connect to Beaconchain again.

2. Why does Claude show an MCP server error before Beaconchain connects?

Claude can show Couldn't reach the MCP server or Authorization with the MCP server failed when you add the connector for Beaconchain.

  • Check that the connector URL is https://connect.composio.dev/mcp.
  • Connectors run from Anthropic's cloud, so your device network is usually not the problem.
  • Add the connector again from Customize > Connectors, then ask Claude to connect Beaconchain.
  • If it fails again, send the error and the ofid_ reference id to support@composio.dev.

3. Why does the Beaconchain authorization link not work?

The Composio connector is one server. Your Beaconchain account connects separately when Claude asks for it.

  • If the browser does not open, or the link expires, ask Claude to retry the Beaconchain connection.
  • Composio creates a fresh Beaconchain authorization link.
  • Open that link in your browser and finish the Beaconchain sign-in.

4. Why do Beaconchain actions fail after they worked before?

The Beaconchain connection can expire or lose permission.

  • Ask Claude to inspect the Beaconchain connection.
  • If the connection is unhealthy, disconnect it when Claude prompts you.
  • Reconnect the Beaconchain account and retry the action.
  • If Claude shows a permission prompt, approve it before Claude changes data in Beaconchain.
  • If the action still fails with a permission error, check that the connected account has that permission in Beaconchain itself.

5. How do I switch to a different Beaconchain account?

Claude can manage the Beaconchain connection for you.

  • Ask Claude to disconnect or delete the current Beaconchain account.
  • Ask Claude to connect Beaconchain again.
  • Open the new Composio authorization link for Beaconchain.
  • Sign in with the other Beaconchain account in the browser.
  • After the account connects, ask Claude to retry the Beaconchain task.

6. Why is my Beaconchain connection missing in Claude Desktop or on a Team plan?

The connector belongs to your Claude account, so your Beaconchain connection works in Claude Web, Desktop, and Cowork.

  • In Claude Desktop, open Customize > Connectors.
  • Next to Composio, click ⋮ and click Clear cache.
  • If Beaconchain tools still do not appear, click ⋮, disconnect, remove the connector, and add it again.
  • On Team or Enterprise, an Owner or Primary Owner must enable the connector before you can connect Beaconchain.
TOOLS

Supported Tools

Every Beaconchain action and event your agent gets out of the box.

Get Chart

Retrieve chart visualizations from beaconcha.

Get Epoch

Retrieve aggregate metrics and status for a beacon chain epoch.

Get ETH1 Deposits by Transaction Hash

Retrieve all beacon chain validator deposit events associated with a specific execution-layer transaction hash.

Get ETH.Store Daily Aggregates

Retrieve ETH.

Get ERC-20 Token Balances

Retrieve a paginated list of ERC-20 token balances for a specific Ethereum address.

Get Execution Block

Retrieve one or more execution-layer blocks by block number from the Ethereum Beacon Chain.

Get Execution Produced Blocks

Retrieve execution-layer blocks attributed to one or more producers.

Get Latest State

Retrieve the latest known Ethereum Beacon Chain network state.

Get Network Performance

Retrieve aggregated network performance metrics for the Ethereum Beacon Chain.

Get Explorer Health

Check the health status of the beaconcha.

Get Validator Queues

Retrieve current queue metrics for Ethereum Beacon Chain validators.

Get Rocket Pool Validator

Retrieve Rocket Pool-specific metadata for validators including minipool status, node fee, smoothing pool status, and RPL stake metrics.

Get Slot

Retrieve detailed information about an Ethereum Beacon Chain slot.

Get Slot Attestations

Retrieve all attestations included in the beacon block for a specific slot.

Get Slot Attester Slashings

Retrieve all attester slashing operations included in the beacon block for a specific slot.

Get Slot Proposer Slashings

Retrieve all proposer slashing operations included in the beacon block for a specific slot.

Get Slot Voluntary Exits

Retrieve all voluntary exit operations included in the beacon block for a specific slot.

Get Sync Committee

Retrieve the sync committee membership for a given sync period.

Get Validator

Retrieve detailed information about an Ethereum Beacon Chain validator.

Get Validator Attestation Efficiency

Retrieve normalized attestation inclusion effectiveness for one or more validators.

Get Validator Attestations

Retrieve attestations observed for one or more validators within a bounded epoch window.

Get Validator Balance History

Retrieve per-epoch balance history for one or more Ethereum Beacon Chain validators.

Get Validator BLS Changes

Retrieve on-chain BLS-to-execution credential change messages (EIP-4881) for validators.

Get Validator Consensus Rewards

Retrieve consensus-layer rewards for one or more validators over multiple lookback windows.

Get Validator Daily Stats

Retrieve per-day statistics for a single Ethereum Beacon Chain validator by index.

Get Validator Deposits

Retrieve execution-layer deposit events for one or more validators.

Get Validator Execution Rewards

Retrieve execution-layer rewards (priority fees and MEV payments) for one or more validators.

Get Validator Income History

Retrieve a per-epoch income breakdown for one or more validators.

Get Validator Leaderboard

Retrieve the current top 100 validators ranked by 7-day consensus-layer rewards.

Get Validator Proposals

Retrieve beacon chain blocks proposed by one or more validators within a bounded epoch window.

Get Validators by Deposit Address

Retrieve validators that have made deposits from a specific execution-layer address.

Get Validators by Withdrawal Credentials

Retrieve validators whose withdrawal credentials match the provided value or execution-layer address.

Get Validators Proposal Luck

Retrieve proposal luck statistics for one or more Ethereum Beacon Chain validators.

Get Validators Queue

Retrieve current queue metrics for validators on the Ethereum Beacon Chain.

Get Validator Withdrawals

Retrieve withdrawal operations attributed to one or more validators within a bounded epoch window.

Post Validators

Retrieve validator information using a JSON request body for multiple validators.

Resolve ENS Name or Address

Resolve ENS (Ethereum Name Service) names to addresses and vice versa.

FRAMEWORKS

How to build Beaconchain MCP Agent with another framework

OpenAI Agents SDK logo

OpenAI Agents SDK

Use Beaconchain MCP with OpenAI Agents SDK

Claude Agent SDK logo

Claude Agent SDK

Use Beaconchain MCP with Claude Agent SDK

Claude Code logo

Claude Code

Use Beaconchain MCP with Claude Code

Codex logo

Codex

Use Beaconchain MCP with Codex

OpenClaw logo

OpenClaw

Use Beaconchain MCP with OpenClaw

Hermes logo

Hermes

Use Beaconchain MCP with Hermes

Atomic Agent logo

Atomic Agent

Use Beaconchain MCP with Atomic Agent

Google ADK logo

Google ADK

Use Beaconchain MCP with Google ADK

LangChain logo

LangChain

Use Beaconchain MCP with LangChain

Vercel AI SDK logo

Vercel AI SDK

Use Beaconchain MCP with Vercel AI SDK

Mastra AI logo

Mastra AI

Use Beaconchain MCP with Mastra AI

LlamaIndex logo

LlamaIndex

Use Beaconchain MCP with LlamaIndex

CrewAI logo

CrewAI

Use Beaconchain MCP with CrewAI

Pydantic AI logo

Pydantic AI

Use Beaconchain MCP with Pydantic AI

AutoGen logo

AutoGen

Use Beaconchain MCP with AutoGen

FAQ

Frequently asked questions

With a standalone Beaconchain MCP server, the agents and LLMs can only access a fixed set of Beaconchain tools tied to that server. However, with the Composio Tool Router, agents can dynamically load tools from Beaconchain and many other apps based on the task at hand, all through a single MCP endpoint.

Yes, you can. Claude Cowork fully supports MCP integration. You get structured tool calling, message history handling, and model orchestration while Tool Router takes care of discovering and serving the right Beaconchain tools.

Yes, absolutely. You can configure which Beaconchain scopes and actions are allowed when connecting your account to Composio. You can also bring your own OAuth credentials or API configuration so you keep full control over what the agent can do.

All sensitive data such as tokens, keys, and configuration is fully encrypted at rest and in transit. Composio is SOC 2 Type 2 compliant and follows strict security practices so your Beaconchain data and credentials are handled as safely as possible.

Start with Beaconchain.It takes 30 seconds.

Managed auth, hosted MCP servers, and every Beaconchain tool your agent needs.Free to start.

Start building