AvaxOps is an open-source MCP server for Avalanche validator ops. Hook it into Claude or Cursor, give it your NodeIDs, and get real answers from the P-Chain — uptime, expirations, balances. Telegram alerts are on the roadmap.
Live queries against the public Fuji P-Chain API. Node IDs and address shown are examples; the plain-English summary is formatted client-side, not AI.
Running validators on Avalanche still means a deprecated CLI, a beta alert service, Grafana you host yourself, and whatever scripts you've duct-taped together. It works — it's just a lot to keep track of.
ACP-267 moved the Primary Network uptime floor from 80% to 90%. You used to have twice the wiggle room. A node that's slowly degrading will hit you in the wallet now.
Avalanche CLI is in maintenance mode. P-Chain stuff goes through Platform CLI, L1s through Builder Console, metrics through Prometheus + Grafana per node. Avalanche Notify is beta — and the docs literally tell you to run your own alerts on top of it.
Avalanche's official MCP server only searches docs. Snowpeer and VScout help delegators pick validators — not operators running their own. There's no MCP tool that answers "what's expiring this month?" We're fixing that.
They query the public P-Chain API — and your node's local endpoints if you pass a URL. No keys, no signing. Plug into Claude, Cursor, or whatever speaks MCP.
Stake, uptime, connectivity, delegators, end date, days_remaining. Pass your NodeIDs, get a table back.
One validator, full picture. Includes the ACP-267 90% check. Give it your node URL and you also get version, bootstrap status, and health checks.
Which validations end in the next N days. Sorted soonest first so you see what's actually urgent.
P-Chain address balances, or L1 validator fee balances with a rough runway estimate. The fee rate is dynamic — we label it as an estimate.
Quick sanity check — is the server up, which network, what's the P-Chain height.
Not built yet. Plan is log/metrics analysis, top-up estimates, and an L1 config helper. Targeting M3.
No API keys, no account signup. Public P-Chain data just works once you've installed it.
Clone the repo, uv pip install -e mcp-server. Needs Python 3.11+.
One claude mcp add command. Works with Claude Code, Claude Desktop, or Cursor.
"Show me validators expiring in the next 30 days" — you'll get live P-Chain data, not a hallucination.
# 1 — install git clone https://github.com/EMPangolin/avax-ops.git cd avax-ops && uv venv && uv pip install -e mcp-server # 2 — add to your agent claude mcp add avax-ops -e AVAX_NETWORK=mainnet -- \ uv --directory $PWD run avax-ops-mcp # 3 — ask › "which validators expire in the next 30 days?" ✓ avax-ops OK — network=mainnet, P-Chain height=25181545
10-week build for the Team1 Builder Grant. M1 is shipped. Everything else is in progress.
The foundation: query any Avalanche validator straight from your AI agent.
AVAX_NETWORKping, list_validators, expiration_report, validator_health, balance_checkvalidator_healthStop checking manually — get pinged the moment something needs you.
Move from "what's wrong" to "here's how to fix it."
diagnose_node — root-cause triage from node health + Prometheus metricsestimate_topup — AVAX needed to extend a validation to a target datel1_config_helper — generate and validate L1 genesis / config JSONA home for operators who'd rather glance than type.
Scope stays read-only through v0.x — no transaction signing or submission until a dedicated, security-reviewed milestone. Your keys never touch this tool.
MIT licensed, read-only, no accounts. Install it tonight and ask your first question.