Skip to main content
Glama
ponsmcp

pons-mcp

by ponsmcp
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

Related Servers

Alternatives to pons-mcp

No user-submitted related servers found.

    Related Servers

    • labs

      koynlabs
      A
      license
      Not graded
      quality
      B
      maintenance
      Enables launching tokens on pump.fun and StonkFun with user-signed transactions, plus a disclosed two-sided quoter for market making.
      MIT

    • pons-mcp

      mesutgulecen
      A
      license
      Not graded
      quality
      A
      maintenance
      Enables agents to interact with the Pons launchpad on Robinhood Chain, providing live protocol data, token launch, trading, and wallet operations through a read-only default with explicit signing opt-in.
      24 npm
      MIT

    • robinhood-chain-mcp

      ExpertVagabond
      A
      license
      C
      quality
      A
      maintenance
      Provides read-only access and unsigned transaction building for the Robinhood Chain Arbitrum Orbit L2, including NFT, ERC-20, stock tokens, oracles, and EIP-3009 tooling.
      100
      15 npm
      MIT

    • Hoodly GMGN Robinhood Research

      hoodly-agent
      F
      license
      Not graded
      quality
      C
      maintenance
      Read-only MCP server for Robinhood chain launchpad discovery and token due diligence using GMGN data.
      -

    • mcp-server

      arcadia-finance
      A
      license
      A
      quality
      C
      maintenance
      Manage Uniswap and Aerodrome liquidity positions with leverage, automated rebalancing, and yield optimization on Base and Unichain.
      35
      155 npm
      5
      AGPL 3.0
    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

    A3.7/5.0

    Scored across 20 tools

    Disambiguation4/5

    Tools are largely distinct and prefixed by domain, with clear separation between V1/V2, quotes, scans, and fee tools. A few pairs (recent_launches vs creator_launches, get_token vs v1_get_token) could be confused at a glance but descriptions resolve the boundaries.

    Naming Consistency4/5

    All names share the pons_ prefix and snake_case style, which makes the surface predictable. The mix of noun-phrase and verb-style names plus the v1_get_token ordering is a minor inconsistency but not confusing.

    Tool Count3/5

    20 tools is on the heavy side and sits in the 16–25 range that starts to feel bulky. The protocol's V1/V2, quoting, scanning, and fee surface justifies most of them, but a few scan/list tools could potentially be consolidated.

    Completeness5/5

    The set covers protocol parameters, token state, launch eligibility, launch/graduation history, creator history, curve trades, snipe tax, supply, gas costs, launch previews, buy/sell/swap quotes, fee changes, fee balances, and legacy V1 data. For a read-only protocol analysis server there are no obvious dead ends.

    Resources