Skip to main content
Glama
Hryhorii77

aero-allocator

by Hryhorii77
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Related Servers

Alternatives to aero-allocator

No user-submitted related servers found.

    Related Servers

    • aero-vote-radar

      araxis33
      A
      license
      Not graded
      quality
      B
      maintenance
      An 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.
      9 npm
      2
      MIT

    • base-defi

      Br0ski777
      A
      license
      Not graded
      quality
      B
      maintenance
      MCP server to fetch DeFi yield opportunities on Base chain, including Aerodrome LP and Moonwell lending, with pay-per-call via x402 micropayments.
      MIT

    • MAIN MCP

      asdener123
      A
      license
      Not graded
      quality
      D
      maintenance
      MCP (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

    • x402farm-mcp

      laurenthalbrun
      A
      license
      Not graded
      quality
      C
      maintenance
      MCP 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.
      1 npm
      MIT

    • orcatrace-mcp

      jcislo
      A
      license
      A
      quality
      C
      maintenance
      MCP server for OrcaTrace, a pay-per-call Polymarket intelligence feed for AI agents. It provides tools to track smart money, whale entries with calibration, market repricings, and digests across 42K prediction markets, with payments settled via x402 on Base.
      13
      6 npm
      MIT
    Deploy Server
    One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

    TDQS

    A4.2/5.0

    Scored across 6 tools

    Disambiguation5/5

    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.

    Naming Consistency4/5

    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.

    Tool Count5/5

    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.

    Completeness5/5

    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

    ActivityActive
    ResponsivenessNo issues

    Resources