Beaconcha.in MCP integration for AI agents.
Connect AI agents to Beaconcha.in through 5 structured actions, including get network performance, get staking queues, and get validator. Review authenticati…
- ACTION CONTRACTS
- 5
- AUTHENTICATION
- API key
- SOURCE STATUS
- Provider-backed
CATALOG SOURCE REVIEWED AUGUST 23, 2026 / ACTION NAMES AND SCHEMAS DERIVED FROM WORKING MACHINES PROVIDER SOURCE
CAPABILITY PROFILE
What the Beaconcha.in integration exposes
The Beaconcha.in Agent App exposes 5 provider-backed actions for finance and data work. Its current contract lets an authorized agent get aggregated beaconcha.in network performance metrics for a fixed evaluation window, get the current staking queue metrics for the requested beaconcha.in chain, and get the current validator snapshot for a single validator identifier. These operations are called through Working Machines as typed capabilities rather than through browser navigation or copied UI steps.
A connection uses API key. Before execution, the agent can inspect the selected action, its required fields, declared scopes, and expected output contract. Provider credentials remain inside the Working Machines runtime; the calling agent receives the capability and its structured result, not the underlying secret.
For reliable operation, start with the narrowest action that satisfies the task, resolve stable provider identifiers before changing state, and validate the returned object or status after execution. Availability still depends on the connected Beaconcha.in account, granted provider permissions, workspace policy, region, plan, and upstream API behavior.
VERIFIED ACTION SAMPLE
Real Beaconcha.in capabilities.
Showing 5 of 5 actions. Risk labels are conservative signals based on operation names, not substitutes for provider documentation or runtime policy.
get_network_performanceREADGet aggregated Beaconcha.in network performance metrics for a fixed evaluation window.
INPUTS: chain / evaluationWindow
get_staking_queuesREADGet the current staking queue metrics for the requested Beaconcha.in chain.
INPUTS: chain
get_validatorREADGet the current validator snapshot for a single validator identifier.
INPUTS: chain / validatorIdentifier
get_validator_consensus_rewardsREADGet per-validator reward breakdowns for a finalized Beaconcha.in epoch.
INPUTS: chain / validatorIdentifiers / epoch / cursor / pageSize
list_validatorsREADList the current validator snapshots for one or more validator identifiers.
INPUTS: chain / validatorIdentifiers / cursor / pageSize
INPUT CONTRACTS
Know what the action needs before it runs.
get_network_performance
chainOPTIONAL- The Ethereum chain to query.
evaluationWindowREQUIRED- The fixed evaluation window used for network performance aggregation.
get_staking_queues
chainOPTIONAL- The Ethereum chain to query.
get_validator
chainOPTIONAL- The Ethereum chain to query.
validatorIdentifierREQUIRED- A validator identifier accepted by Beaconcha.in.
get_validator_consensus_rewards
chainOPTIONAL- The Ethereum chain to query.
validatorIdentifiersREQUIRED- Ordered list of validator identifiers used to filter the result.
epochOPTIONAL- The finalized epoch used for reward breakdown queries.
cursorOPTIONAL- The pagination cursor returned by a previous call.
pageSizeOPTIONAL- The number of items to return per page.
PROVIDER-SPECIFIC WORKFLOWS
Jobs this Agent App can support
Inspect Get Network Performance
Get aggregated Beaconcha.in network performance metrics for a fixed evaluation window. Use this as a bounded discovery step, retain the returned identifier, and avoid expanding the read beyond the task's stated scope.
get_network_performanceVerify with Get Staking Queues
Get the current staking queue metrics for the requested Beaconcha.in chain. Compare the returned provider state with the intended outcome and preserve stable IDs or canonical links in the run record.
get_staking_queuesSAFETY BOUNDARY
Operate Beaconcha.in with explicit limits
- Authorize Beaconcha.in with API key and grant only the provider access required by the selected actions.
- The current action names appear read-oriented, but returned Beaconcha.in data may still be sensitive and should be minimized before it enters model context.
- Do not infer permission from catalog visibility. Workspace policy, connection identity, and upstream authorization still govern execution.
- No provider scope string is declared on the sampled actions. Verify the connected account's actual permissions in Beaconcha.in rather than assuming unrestricted access.
- After a call, inspect the structured result and execution record before reporting that the Beaconcha.in task completed successfully.
CONNECTION MODEL
API key
Beaconcha.in API key sent with the Authorization Bearer header. Get or manage it in the Beaconcha.in user portal: https://beaconcha.in/user/api-key-management
Working Machines stores provider credentials behind the execution boundary. An agent can use an authorized connection identity, but catalog discovery alone does not reveal OAuth tokens, API keys, or provider secrets.
- READ SIGNALS
- 5
- WRITE SIGNALS
- 0
- HIGH IMPACT
- 0
- REVIEW SIGNALS
- 0
EVIDENCE AND AVAILABILITY
Provider reference
Action names, input fields, authentication types, and counts on this page are generated from the Working Machines provider catalog. Provider behavior, quotas, object semantics, account eligibility, and regional availability remain governed by Beaconcha.in.