aero-allocator
This is an Aerodrome/Base MCP server for analyzing pools, forecasting fee demand, recommending veAERO vote allocations, and preparing unsigned vote calldata.
Scan gauge-enabled Aerodrome pools on Base with live TVL, staked TVL, fee tier, and emissions, sorted by staked TVL.
Fetch per-epoch pool history including votes, AERO emissions, trading fees, and bribes/incentives.
Predict next-epoch trading-fee demand and compare it with current vote allocation to find predictive edge or voter ROI.
Recommend pool allocations for either protocol efficiency or voter ROI, with weights summing to 100% and a 25% concentration cap.
Build unsigned
Voter.vote()calldata for a veAERO NFT and chosen pool weights; it never signs or sends.Check whether the direct Predictive Allocation submission path is wired to live contracts.
Provides tools for forecasting next-epoch demand and allocating incentives across Velodrome (Optimism) liquidity pools, including vote recommendations, bribe placement, and calldata preparation for veVELO voters.
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., "@aero-allocator predict demand for top 5 Aerodrome pools"
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.
aero-allocator
https://aeroallocator.app is the sAERO allocator for Aero (the merged Aerodrome and Velodrome, live since 2026-10-22): which gauges pay the most per day for your amount of sAERO, what your positions earn, and an allocate / return-to-idle flow signed in your own wallet. It is free, has no accounts, and never holds keys. Figures are estimates from recent on-chain fee releases, not financial advice.
This repository holds:
web/: the Next.js site above, plus its free and paid (x402) APIs. This is the live product. Start with The site.skills/: two agent skills (re-allocate a position only when it is worth it; check or prepare a veAERO to sAERO upgrade). See Agent skills.scripts/: the CI audit gate. (The weekly-vote MCP engine that used to live insrc/was removed after Aero replaced weekly voting; it is in git history, last present in commit1f94d77.)
The site
What it does (all in web/, one page):
Gauges: every Aero gauge on Base (and the other Aero chains) ranked by what your amount earns per day after it dilutes the gauge, with an estimated APR, a "power flow" column (which gauges are gaining or losing share of the allocation weight), a Steady column (how evenly a gauge paid), flags for gauges whose incentives just appeared, and a per-gauge history chart (6-hour bars, plus a per-day chart from a 90-day record). The best split across up to six gauges is solved for you.
Your positions: paste an address or connect a wallet. Positions are read in the browser over public RPC, so the address never reaches our server. Each shows size, lock, how much is allocated, the 47-hour wait (with a "remind me" calendar file, built in the browser), what it earns now vs the best split and so what staying costs per day, and the trading fees it has earned and not claimed. Allocating simulates the transaction on-chain before your wallet is asked to sign.
Notes it keeps honest: the 47-hour wait belongs to each position, an existing position can't be split, a position with no AERO staked is usually an Aero Autopilot key, and fee figures are a recent pace, not a promise.
How the numbers are made: gauge weight is read from Aero's contracts; fees come from the fee releases (NotifyFeesAmount logs) over
the last 48 hours, with each gauge's first release left out; incentives are the streaming programs on each gauge. A yield per gauge is
(fees + incentives) × amount / (weight + amount). Against Aero's own pages, total allocation matched and APR was within about a point
or two on the pools compared.
APIs
Free, rate limited, no key. Described for agents at /llms.txt (plain text) and /openapi.json (OpenAPI 3.1, including the paid routes' 402 behaviour):
Endpoint | |
| Every gauge on a chain with weight, caps and incentives; the Base list also carries |
| Estimated fees per day per gauge, the hours of history behind each figure, a steadiness figure, and a |
| One gauge's fees per 6 hours, weight snapshots, steadiness, and per-day points from the 90-day record |
| How each gauge's share of the allocation weight moved over the last day, and gauges whose incentives just appeared |
| best split of an amount over every chain, after the ETH each extra chain costs (read-only) |
| ETH cost on Base of sending power to another chain |
| USD prices for up to 12 token addresses on one Aero chain, Base by default (lets the page value earned fees and incentives without sending a position anywhere) |
| The 1200×630 share card (also the link preview) |
Aero’s app now calls a position’s power Allocation Power (formerly voting power). The site uses that word; the API fields, the MCP tools and the agent skills keep power, votingPower and weight, so agents built on them keep working.
Paid (x402), below: Paid API (x402).
Running it
cd web && npm install && npm run devOpen http://localhost:3000. Checks, in web/: npx tsc --noEmit, npm run lint, npm test, npm run build; in the root: npm install && npm run typecheck && npm test (the skills' and the audit gate's tests), and npx tsx scripts/audit-gate.ts . and ... web (CI runs all of them; the audit gate fails on any advisory except the one accepted advisory listed in scripts/audit-gate.ts).
History is kept by Vercel Cron: six crons (one per chain, web/vercel.json) call /api/gauge-fees/ingest every 30 minutes, which
extends the fee record (4 days), takes a weight snapshot (3 days) and, once a UTC day has finished, adds it to the daily record
(90 days). On Base the same cron also writes down, once a UTC day, the split the site would recommend for 10,000 sAERO (track-record-8453.json), so /api/track-record can show later how that advice compared with what the gauges paid. All of these live in private Vercel Blobs. The route requires CRON_SECRET as a bearer token (Vercel Cron sends
it by itself); a deployed site without it refuses every call, so history stays empty until it is set.
Environment (web/)
Var | ||
| optional | A dedicated RPC, and a second one for failover. Without them public nodes are used, which works but is slower and rate limited |
| needed for history | Vercel Blob token for the fee, weight and daily records. Without it the site works but shows no history |
| needed for history | Locks |
|
| Public address, for the link-preview image |
| unset | Free Reown Cloud project id (the domain must be on its allowlist). Enables WalletConnect; without it that connector is left out because its relay socket would hang the tab |
| for the paid routes | See Paid API (x402) |
| for "notify me" | The key pair for the "your wait is over" browser notifications; make one with |
Deploying to Vercel
The site lives in web/, which Vercel's zero-config detection doesn't find at the repo root, so the project needs a couple of non-default settings:
Setting | Value | Why |
Root Directory |
| Vercel's Next.js detection checks this directory's |
Install Command |
| Must be a real install, not a no-op: Vercel checks the installed Next.js version immediately after this step, before running Build Command |
Build Command | default ( | The project may still carry the older |
Output Directory | default ( | Resolved relative to Root Directory: do not prefix with |
Root Directory isn't exposed as a vercel CLI flag; set it via the dashboard (Project Settings →
General) or the API (PATCH /v9/projects/{id} with {"rootDirectory": "web"}). Env vars (see the table above) go in Project
Settings → Environment Variables, per environment (Production/Preview), and take effect on the next deployment. A dedicated RPC (Alchemy,
Infura) is strongly recommended over the public default — it's the difference between a ~20s and a
~1min cold snapshot build, which matters against Vercel's function timeout (60s ceiling on Hobby).
Vercel's Deployment Protection (an SSO auth wall) is on by default for all deployments including
production. To make production public while keeping preview deployments protected, set
ssoProtection.deploymentType to "preview" via the API (also not a dashboard toggle at the time of
writing).
Rate limits: two Vercel Firewall rules (not stored in this repo; they live in the project's Vercel config) cap each IP at 300 requests a minute across /api, and at 30 a minute on the routes that read several chains or logs (all-chains-split, top-gauges, v1/cross-chain-plan, gauge-history, allocation-fee); beyond that Vercel answers 429 with an x-vercel-mitigated header, and the IP is let back in within about a minute. They add a limit shared across servers to the per-route, per-instance limiter in web/lib/rate-limit.ts. Set up 2026-10-31 with the CLI: vercel firewall rules list shows them, vercel firewall rules inspect "<name>" the details, vercel firewall rules disable|remove "<name>" then vercel firewall publish undoes one; to recreate them: vercel firewall rules add "Rate limit: whole API" --condition '{"type":"path","op":"pre","value":"/api"}' --action rate_limit --rate-limit-requests 300 --rate-limit-window 60 --rate-limit-keys ip --yes, the same with one --condition per route joined by --or and 30 requests for the second, then vercel firewall publish. A busy shared IP (an office, a mobile carrier) could hit the 300 limit; raise it then.
Preview builds are skipped: web/vercel.json has an ignoreCommand that exits 0 only when VERCEL_ENV is preview (anything else, or an unset variable, builds), because every pull request's preview and its merge build both cost build minutes and the October bill's biggest line was Build CPU. GitHub's CI still builds and tests each pull request. Delete the ignoreCommand line to get previews back.
Related MCP server: aero-vote-radar
Agent skills
Two skills in skills/, for agents that act on a sAERO position. Neither signs or sends anything; the owner's wallet layer does.
Skill | What it does |
Once the wait is over, checks a position and re-allocates it only for a real, steady gain (never a one-off fee burst), checks the unsigned | |
Checks a wallet's old veAERO locks against Aero's migration contract (what each becomes, what blocks it) and, only after the owner confirms each lock, prepares the unsigned |
The root SKILL.md is the overview of the APIs for agents. The skills are in this public repo, so no separate publishing is needed; install them with the skills CLI (the root skill hides the others unless you pass --full-depth):
npx skills add Hryhorii77/aero-allocator # the overview skill
npx skills add Hryhorii77/aero-allocator --full-depth --skill saero-allocator-automator # re-allocate when it is worth it
npx skills add Hryhorii77/aero-allocator --full-depth --skill veaero-to-saero-upgrade # check and prepare an upgradeReview a skill before you use it: it runs with your agent's permissions.
Free MCP server (packages/mcp)
aeroallocator-mcp is a dependency-free MCP server (stdio, Node 22+) over the site's free, read-only APIs: top_gauges, best_split_all_chains, power_flows, gauge_history, allocation_fee and track_record. top_gauges also takes chain: "all" for every chain ranked and merged. It never signs or sends anything and needs no key. Published on npm (0.2.0, 2026-10-31, which adds chain: "all"). Add it to an MCP client with { "mcpServers": { "aeroallocator": { "command": "npx", "args": ["-y", "aeroallocator-mcp"] } } }. See packages/mcp/README.md.
Releases are manual and need the owner's npm login with 2FA: bump version in packages/mcp/package.json, then cd packages/mcp && npm publish (a version can't be re-published; tests run in the root npm test). From a clone: node packages/mcp/bin/aeroallocator-mcp.mjs.
Paid API (x402)
Three pay-per-call sAERO endpoints on the site's own deployment, in USDC on Base via the x402 protocol, settled by
Coinbase's CDP facilitator only after a successful answer (a 400/404/422 is never charged). The free site is unaffected.
All three are listed in Coinbase's x402 Bazaar (and so agentic.market): position and allocate-plan since their first settled payments on 2026-10-26, cross-chain-plan since its first on 2026-10-28 (the call that took three attempts: see the 500-character description limit in CLAUDE.md). They are described for agents at /llms.txt and /openapi.json.
Endpoint | Price | What it answers |
| $0.05 | Where does this sAERO position stand: power, lock, idle vs allocated, the 47-hour re-allocation wait, what it earns per day now vs the best split of Base gauges for its own size, and a stay / switch / allocate / unknown recommendation. |
| $0.10 | The unsigned, already-simulated |
| $0.25 | The ordered, unsigned |
These answer something the free /api/gauges and /api/gauge-fees reads can't: a chain read keyed to one position, and calldata that
satisfies the Voter's rules (full overwrite per chain, exact total, ascending addresses). The old weekly-vote /api/v1/forecast earned
almost nothing because the free site served the same payload; keep new paid routes on the "free can't do this" side.
Requires three env vars to activate; without all three each paid route serves a clean 501 rather than accepting payment:
Var | ||
| Base address you control | Where payments land: never generated or held by this codebase |
| Coinbase Developer Platform API key | |
| Same place | Paired secret |
Roadmap
sAERO allocator: ranked gauges, best split, positions read in the browser, allocate and return-to-idle from your wallet
Fee pace measured from on-chain releases, with weight snapshots, power flow, steadiness, new-incentive flags and a 90-day daily record
Paid x402 endpoints for agents (
v1/position,v1/allocate-plan,v1/cross-chain-plan),/llms.txtand/openapi.json, listed in the x402 BazaarTwo agent skills: re-allocate a position only when it is worth it, and check or prepare a veAERO to sAERO upgrade (read-only, irreversible, verified against Aero's contracts)
A gauge whose fee pace is a burst is marked spiky and its APR shown as a range
Per-position wait explanation, calendar reminder, earned-fees read, Autopilot-key handling, and what staying costs per day
Allocating a position across chains (best split or your own percentages), returning power, moving it between chains and picking gauges inside a chain, each step simulated first; Arc is a seventh chain
A paid cross-chain plan for agents (
v1/cross-chain-plan)Claiming rewards: not built, because Aero's claim is callable only by a position's operator or Aero's orchestrator
A move-or-stay backtest: prototyped and dropped, the record was too short and fees too lumpy; retry with more of the daily record
Disclaimer
Figures are estimates from recent onchain fee releases, not forecasts or financial advice. Always review a transaction in your wallet before signing it.
Available Tools
6 toolspool_historyA
Per-epoch history for one Aerodrome pool: votes, AERO emissions, trading fees (USD) and bribes/incentives (USD) per weekly epoch, newest first (first row is the in-progress epoch).
Inputs: pool (required), epochs.
predict_demandA
Forecast next-epoch trading-fee demand for top Aerodrome pools and compare it with current vote allocation. Key output: predictiveEdgePct — pools with positive edge are under-incentivized relative to predicted demand (the signal Predictive Allocation rewards). Data is cached ~5 min.
Inputs: limit, sortBy, refresh.
predictive_allocation_statusA
Status of the direct Predictive Allocation submission path (Aerodrome's July 2026 mechanism replacing weekly gauge voting). Reports whether live contracts are wired into this server.
Inputs: no named parameters.
prepare_vote_calldataA
Build unsigned transaction calldata for Aerodrome Voter.vote() from an allocation (veAERO NFT id + pool weights). Returns { to, data, value } for the host wallet (e.g. Base MCP send/send_calls) to review, sign and submit — this server never signs. Note: votes can only be cast once per epoch per veNFT, and not in the final hour before epoch flip.
Inputs: veNftId (required), allocations (required).
recommend_allocationA
Produce a concrete incentive-allocation recommendation across Aerodrome pools. objective=protocol_efficiency allocates proportional to predicted next-epoch fee demand (the Predictive Allocation ideal); objective=voter_roi maximizes expected reward per veAERO vote with a 25% per-pool concentration cap. Returns weights that sum to 100%.
Inputs: refresh, maxPools, objective.
scan_poolsA
Scan Aerodrome (Base) gauge-enabled pools with live TVL, staked TVL, fee tier and emissions. Sorted by staked TVL. Use this for a market overview before predicting demand.
Inputs: limit, minTvlUsd.
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
TDQS
Scored across 6 tools
Each tool targets a distinct aspect of Aerodrome allocation: history, demand prediction, mechanism status, vote calldata preparation, allocation recommendation, and pool scanning. There is no overlap; descriptions clearly differentiate their purposes.
Most tool names follow a clear verb_noun pattern (predict_demand, scan_pools, prepare_vote_calldata, recommend_allocation), but two are noun phrases (pool_history, predictive_allocation_status). The naming style remains consistent with snake_case and descriptive terms.
With 6 tools, the server is well-scoped for its domain. Each tool serves a necessary function in the allocation workflow, neither too few to be incomplete nor too many to be unwieldy.
The tool set covers the full lifecycle: scanning for overview, historical data, demand prediction, allocation recommendation, and vote calldata construction. There are no obvious gaps for the intended purpose of optimizing Aero vote allocation.
Maintenance
Related MCP Connectors
Real-time crypto & tokenized equity intelligence MCP over x402 USDC on Base mainnet.
131MCP server connecting AI agents to non-custodial staking data across 130+ networks.
23-in-1 MCP server: EVM tx simulator, funding rate arb, macro radar, swap calldata & security.
MCP server for Boson Protocol — on-chain agentic commerce for physical & digital goods.
Related MCP Servers
- AlicenseNot gradedqualityDmaintenanceMCP (Model Context Protocol) server for the MAIN DEX on Base. Provides AI agents (Claude, Cursor, etc.) with tools to interact with the protocol: swap tokens, manage liquidity, enter/exit ALM strategies(10% APY), and more.MIT
- AlicenseNot gradedqualityBmaintenanceAn MCP server + CLI that reads live on-chain data from Aerodrome Finance (Base) to rank pools by veAERO vote efficiency, and recommends a vote allocation that accounts for self-dilution.16 npm3MIT
- AlicenseNot gradedqualityCmaintenanceMCP server to fetch DeFi yield opportunities on Base chain, including Aerodrome LP and Moonwell lending, with pay-per-call via x402 micropayments.MIT
- AlicenseNot gradedqualityDmaintenanceMCP server that provides AI agents with pay-per-call access to a suite of tools (honeypot check, token market, DeFi yields, etc.) via USDC on Base using the x402 protocol.MIT