pons-mcp
Related Servers
Alternatives to pons-mcp
No user-submitted related servers found.
Related Servers
AlicenseNot gradedqualityBmaintenanceEnables MCP hosts to read and trade Robinhood Chain markets, including swaps, launch checks, bonding-curve launches, Arcus and Lighter perps and funding, weekend reopen watch, bridging, and local wallet operations with two-step confirmations.862 npmMIT- AlicenseNot gradedqualityCmaintenanceEnables MCP clients to read multi-chain memecoin launchpad data including coins, burns, staking, fee boards, and read-only perps markets, while calculating quotes and preparing buys, sells, stakes, unstakes, and launches for the user’s own wallet to sign.MIT
- AlicenseNot gradedqualityBmaintenanceEnables coordinated pump.fun buys, sells, and token launches using encrypted local Rust wallets, with previews, simulation, Jito bundle submission, status tracking, and pump.fun API/RPC access through MCP tools.MIT
- AlicenseNot gradedqualityBmaintenanceEnables launching tokens on pump.fun and StonkFun with user-signed transactions, plus a disclosed two-sided quoter for market making.MIT
- AlicenseBqualityCmaintenanceAgent token launchpad on Base: agents launch tokens on bonding curves, anyone trades. Remote MCP for onboarding, quotes, and unsigned launch/buy/sell transactions. Unaudited.24MIT

OpenHooks MCPofficial
AlicenseAqualityCmaintenanceEnables AI agents to discover launchpad tokens trading on Uniswap v4 bonding curves, inspect pools, quotes, balances and protocol stats, and receive unsigned swap transactions the user signs in their own wallet. It runs on Robinhood Chain for Pons tokens, holding no keys and sending nothing itself.6MIT
TDQS
Scored across 20 tools
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.
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.
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.
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.