ethereum-validator-queue-mcp
Provides real-time monitoring of Ethereum's validator activation and exit queues, enabling tracking of staking dynamics, validator status queries, and network participation trends.
Click on "Deploy Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@ethereum-validator-queue-mcp show me the current validator activation queue status"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
Ethereum Validator Queue MCP
An MCP server that tracks Ethereum’s validator activation and exit queues in real time, enabling AI agents to monitor staking dynamics and network participation trends.
Features
Tools:
get_activation_queue: Retrieves statistics about the Ethereum validator activation queue, including queue length, total active validators, entering validators' balance, and estimated wait time.get_exit_queue: Retrieves statistics about the Ethereum validator exit queue, including queue length, total active validators, exiting validators' balance, and estimated wait time.get_validator_status: Queries the status of a specific validator by its public key, providing details such as status, effective balance, activation epoch, and exit epoch.
Prompt:
analyze_queue: A reusable prompt template for LLMs to analyze validator queue trends, including staking demand, impact on ETH price, and network security.
Related MCP server: etf-flow-mcp
Installation
Prerequisites
Python: Version 3.10 or higher
uv: A fast and modern Python package manager (installation instructions)
Setup
Clone the Repository:
git clone https://github.com/kukapay/ethereum-validator-queue-mcp.git cd ethereum-validator-queue-mcpInstall dependencies:
uv syncInstall to Claude Desktop:
Install the server as a Claude Desktop application:
uv run mcp install main.py --name "Ethereum Validator Queue"Configuration file as a reference:
{ "mcpServers": { "Ethereum Validator Queue": { "command": "uv", "args": [ "--directory", "/path/to/ethereum-validator-queue-mcp", "run", "main.py" ] } } }Replace
/path/to/ethereum-validator-queue-mcpwith your actual installation path.
Usage
Tools and Prompts
Tools:
get_activation_queue(): Returns activation queue stats, e.g., "Current activation queue length: 7189 validators, Total active validators: 1084363, Entering validators balance: 283043.84 ETH, Estimated wait time: Approximately 8.0 days."get_exit_queue(): Returns exit queue stats, e.g., "Current exit queue length: 27152 validators, Total active validators: 1084363, Exiting validators balance: 882528.00 ETH, Estimated wait time: Approximately 30.2 days."get_validator_status(pubkey): Returns validator details for a given public key (48-byte hex string starting with '0x'), e.g., "Validator 0x1234...: Status: active_online, Effective Balance: 32.00 ETH, Activation Epoch: 123456, Exit Epoch: N/A."
Prompt:
analyze_queue(): Generates a prompt for LLMs to analyze queue trends, e.g., "Analyze the current Ethereum validator queues: What do the current queue lengths indicate about staking demand? How might this impact ETH price and network security? Provide historical context if possible."
Example Interaction
Below are examples of natural language prompts you might use in an MCP-compatible client (e.g., Claude Desktop) and the corresponding outputs from the server, based on sample data.
Get Activation Queue Statistics:
Prompt: "Show me the current Ethereum validator activation queue status."
Command:
get_activation_queue()Output:
Current activation queue length: 7189 validators Total active validators: 1084363 Entering validators balance: 283043.84 ETH Estimated wait time: Approximately 8.0 days (assuming ~900 activations per day)
Get Exit Queue Statistics:
Prompt: "What's the status of the Ethereum validator exit queue?"
Command:
get_exit_queue()Output:
Current exit queue length: 27152 validators Total active validators: 1084363 Exiting validators balance: 882528.00 ETH Estimated wait time: Approximately 30.2 days (assuming ~900 exits per day)
Get Validator Status:
Prompt: "Check the status of the validator with public key 0x93247f2f..."
Command:
get_validator_status("0x93247f2f...")Output (assuming sample data from the API):
Validator 0x93247f2f...: Status: active_online Effective Balance: 32.00 ETH Activation Epoch: 123456 Exit Epoch: N/A
Analyze Queue Trends:
Prompt: "Analyze the current Ethereum validator queue trends."
Command:
analyze_queue()Output (prompt sent to LLM for analysis):
Analyze the current Ethereum validator queues: - What do the current queue lengths indicate about staking demand? - How might this impact ETH price and network security? - Provide historical context if possible.LLM Response (example, depends on the LLM):
The current Ethereum validator queues show a significant exit queue (27,152 validators) compared to the activation queue (7,189 validators), indicating a higher number of validators are leaving than joining. This could suggest reduced staking demand, possibly due to market conditions or profitability concerns. The large exiting balance (882,528 ETH) may increase selling pressure on ETH, potentially impacting its price negatively in the short term. However, the network remains secure with over 1 million active validators. Historically, exit queue spikes have occurred during market downturns or after major network upgrades (e.g., Shanghai upgrade). Further analysis of staking rewards and market trends is recommended.
License
This project is licensed under the MIT License. See the LICENSE file for details.
Available Tools
3 toolsget_activation_queueA
Get current Ethereum validator activation queue statistics.
Returns:
A string containing:
- Current activation queue length (number of validators waiting to activate)
- Total active validators
- Total balance of entering validators in ETH
- Estimated wait time (based on ~900 activations per day)
Inputs: no named parameters. Returns: result
get_exit_queueA
Get current Ethereum validator exit queue statistics.
Returns:
A string containing:
- Current exit queue length (number of validators waiting to exit)
- Total active validators
- Total balance of exiting validators in ETH
- Estimated wait time (based on ~900 exits per day)
Inputs: no named parameters. Returns: result
get_validator_statusA
Get status for a specific Ethereum validator by public key.
Args:
pubkey (str): The public key of the validator (48-byte hex string starting with '0x')
Returns:
A string containing:
- Validator public key
- Current status (e.g., active_online, pending, exited)
- Effective balance in ETH
- Activation epoch (if applicable)
- Exit epoch (if applicable)
Inputs: pubkey (required). Returns: result
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
TDQS
Scored across 3 tools
Each tool has a clearly distinct purpose with no overlap: get_activation_queue focuses on activation statistics, get_exit_queue on exit statistics, and get_validator_status on individual validator details. The descriptions clearly differentiate between queue-level and validator-specific operations, eliminating any potential confusion.
All three tools follow a consistent verb_noun pattern with 'get_' prefix and descriptive suffixes (_activation_queue, _exit_queue, _validator_status). The naming is uniform, predictable, and clearly communicates each tool's function without any stylistic deviations.
Three tools is appropriate for the narrow scope of Ethereum validator queue monitoring, covering activation, exit, and individual status queries. While slightly minimal, each tool earns its place by addressing distinct aspects of the domain without redundancy or obvious omissions.
The toolset provides comprehensive read-only coverage for validator queue monitoring, including both aggregate queue statistics and individual validator status. A minor gap exists in the lack of write operations (e.g., initiating validator actions), but this aligns with the server's apparent monitoring focus, and agents can work effectively with the provided tools.
Maintenance
Related MCP Connectors
MCP server connecting AI agents to non-custodial staking data across 130+ networks.
Hosted MCP server for live public-data APIs and Skills for AI agents.
MCP server for building and testing AI agents with multi-model experimentation and insights.
MCP server for Renzo protocol data, including chains, vaults, operators, and ezETH metrics.
Related MCP Servers
- AlicenseNot gradedqualityDmaintenanceAn MCP server for tracking and managing cryptocurrency portfolio allocations, enabling AI agents to query and optimize portfolio strategies in real time.10MIT
- AlicenseAqualityDmaintenanceAn MCP server that delivers crypto ETF flow data to power AI agents' decision-making.19MIT
- AlicenseBqualityDmaintenanceAn MCP server that aggregates live governance proposals from major DAOs enabling AI agents to track, analyze, and act on decentralized decision-making in real time.32MIT
- AlicenseAqualityDmaintenanceAn MCP server that tracks Bitcoin's Unspent Transaction Outputs (UTXO) and block statistics, giving AI agents direct access to essential on-chain data.22MIT