PonsMCP
OfficialThis MCP server lets agents read Robinhood Chain and PONS launchpad data, quote payments, and execute policy-limited USDG payments.
Get Robinhood Chain network info (chainId, RPC, explorer, token addresses).
Fetch live PONS token price, liquidity, and top DEX pairs.
Read pons v1 launch token metadata and live DEX markets.
Read ERC-20 metadata (name, symbol, decimals, supply).
Check agent wallet balance for USDG or any token.
Quote a USD amount into USDG base units without executing.
Execute autonomous USDG payments to a recipient with policy/balance checks and receipt verification (requires PONSMCP_PRIVATE_KEY).
Look up transaction receipt status, block, gas used, and decoded ERC-20 transfers.
Enables autonomous payments and market data on Robinhood Chain (chainId 4663), including chain info, PONS price and liquidity data, launch-token metadata and markets, token metadata, wallet balances, USDG quotes, payment execution with policy checks, and transaction receipt verification.
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., "@PonsMCP pay 5 USDG to 0x9a3f...71b2 for the API access, show me the receipt"
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.
PonsMCP
MCP server + TypeScript SDK: autonomous agent payments in USDG on Robinhood Chain (4663) or USDC on Base (8453 · beta), read-only pons launchpad intelligence, and x402 paid-resource fetching — zero runtime dependencies.
Multi-chain support
PonsMCP v2.3.0 supports two chains. Set PONSMCP_CHAIN to switch:
Chain | ID | Settlement | Status | Notes |
Robinhood Chain | 4663 | USDG ( | active | Default; all tools fully tested |
Base | 8453 | USDC ( | beta | Read-only tools verified; write ops not tested on Base |
# Default — Robinhood Chain 4663, USDG
ponsmcp
# Switch to Base (beta)
PONSMCP_CHAIN=8453 ponsmcppons_quote always returns costs for both chains so agents can compare settlement options.
Related MCP server: hoodr MCP Server
Quick Start — three commands to your agent's first payment
# 1. Install (Node >= 20) and start the stdio MCP server
npm install -g @ponsmcp/sdk && ponsmcp
# 2. Give the agent a funded wallet + spending caps (env of the MCP server process)
export PONSMCP_PRIVATE_KEY=0x… # agent key — never in a browser or repo
export PONSMCP_MAX_PER_TX=100000000 # 100 USDG per transaction (base units, 6 dec)
export PONSMCP_DAILY_LIMIT=1000000000 # 1,000 USDG per day
# 3. Call the pay tool from any MCP host (Claude Desktop, Cursor, …)
# pons_pay { "payTo": "0xMerchant…", "amountUsd": "2.50" }
# → policy check → USDG transfer on chain 4663 → verified receipt → 0x…Point your MCP host at the server:
{ "mcpServers": { "ponsmcp": { "command": "ponsmcp" } } }All 21 read-only tools work with no key at all — ponsmcp alone is enough for market and launch research.
What PONS is for here (and what it isn't)
ponsfamily.com is a launchpad — pons v1/v2 launch tokens on Robinhood Chain. PonsMCP gives agents read-only intelligence over that surface, and separate payment rails for everything else:
Capability | Tools | Moves funds? |
Payments — USDG settlement between agent and merchant |
| yes |
x402 — paid HTTP resources with auto-settlement |
| on 402 only |
Transfers — send any ERC-20 or native ETH |
| yes |
Launchpad research — v1 metadata, feed, screening |
| no |
v2 curves — records, quotes, snipe tax, escrow |
| no |
Market — PONS price/pairs, stock tokens (DexScreener) |
| no |
Payment settlement is USDG, not PONS. PONS is the ecosystem asset of the launchpad; an agent that needs to pay for a service pays in a stable. Launch-tool research (should I buy this launch? what would the tax be? what does the creator have claimable?) is a decision layer — the execution of any launch trade stays in your own wallet, deliberately outside this SDK.
For launch creators: pons_escrow_balance reads the v2 fee escrow (balanceOf / balanceOfToken) so an agent can monitor claimable creator fees. Claiming itself (claim() / claimToken() on the escrow) is a wallet action — PonsMCP never moves someone else's fees.
Architecture
┌────────────────────────────────────────────────────────────────────────┐
│ MCP host (Claude Desktop / Cursor / your agent runtime) │
│ owns the key: PONSMCP_PRIVATE_KEY lives ONLY here │
└───────────────┬────────────────────────────────────────────────────────┘
│ stdio JSON-RPC (MCP: initialize → tools/list → tools/call)
▼
┌────────────────────────────────────────────────────────────────────────┐
│ ponsmcp server (this package, 34 tools) │
│ │
│ tools/call ──► PolicyEngine ──► per-tx cap 100 USDG │
│ │ daily cap 1,000 USDG │
│ │ (checked BEFORE any signing) │
│ ▼ │
│ crypto.ts ──► keccak-256 · RLP · secp256k1 │
│ │ canonical low-s · CSPRNG nonce · 0 deps │
│ ▼ │
│ EIP-155 legacy tx, chainId 4663, signed locally │
└──────┬──────────────────┬──────────────────────┬───────────────────────┘
▼ ▼ ▼
Robinhood Chain DexScreener HTTP + x402
(USDG settle, (PONS, launch │
ETH gas) & stock markets) ▼
│ 402 requirement → settle →
▼ retry with X-PAYMENT proof
receipt verified: status 0x1 +
decoded USDG transfer matches quoteNever puts a private key, a browser, or a third-party signer between the policy check and the broadcast.
The 34 tools
Tool | Key? | What it does |
| — | list all supported chains with status |
| — | active chain facts + all supported chains |
| — | PONS market snapshot |
| — | pons v1 launch metadata on-chain |
| — | live markets for a launch token |
| — | recent launches (official feed) |
| — | v1 launches that reached their liquidity threshold |
| — | ranked launches with Grade A / Early Watch tiers |
| — | v2 factory launch record |
| — | pure curve buy quote (tax-capped) |
| — | pure curve sell quote |
| — | decaying opening tax per recipient |
| — | claimable native fees (v2 escrow) |
| — | claimable ERC-20 fees (v2 escrow) |
| — | ERC-20 metadata for any token |
| — | USD → settlement-token base units, both-chain comparison |
| ✅ | policy → sign → broadcast → verified receipt |
| ✅ | fetch a 402 resource, settle the exact price |
| — | independent receipt verification |
| ✅ | fetch any URL; auto-settle x402 402s and retry with proof |
| — | probe a domain for x402 paid resources |
| — | all 19 tokenized stock tokens with addresses |
| — | live DEX price for a stock token (ticker or address) |
| — | on-chain metadata for a stock token |
| — | screen + rank all 19 stock tokens by liquidity / tier |
| ✅ | agent wallet balance for any token |
| ✅ | send any ERC-20 (policy caps apply) |
| ✅ | send native ETH (0.01 ETH/tx, 0.1 ETH/day caps) |
Why zero dependencies
Every line that touches a private key or builds a transaction lives in this repo: keccak-256, RLP encoding, secp256k1 signing with canonical low-s, EIP-155 replay protection. It is auditable in an afternoon, and the npm tarball is byte-identical to src/.
FAQ
Is my private key safe? It lives only in the MCP server process environment (PONSMCP_PRIVATE_KEY). It never reaches a browser, the web console, logs, or any API request. Signing happens locally; transactions are fully built and signed before any endpoint sees them.
What stops an agent from overspending? The PolicyEngine checks a per-transaction cap (default 100 USDG) and an in-process daily budget (default 1,000 USDG) before every signature. Balance is pre-checked too. The daily counter resets on restart — for hard budgets, fund the agent wallet with only what it may spend. pons_send_eth additionally caps at 0.01 ETH per tx / 0.1 ETH per day.
Which chain and token? Default: Robinhood Chain, chain ID 4663 (an Arbitrum Orbit L2), settling in USDG (0x5fc5360D0400a0Fd4f2af552ADD042D716F1d168, 6 decimals); gas is ETH. Set PONSMCP_CHAIN=8453 to switch to Base (USDC, 0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913, 6 decimals) — Base support is beta: read-only tools are verified, write operations (payments, transfers) are not tested on Base.
How do I know a payment really went through? pons_pay returns ok: true only after verifying an on-chain receipt: status 0x1 plus the decoded USDG Transfer event matching the exact quote. pons_tx_status re-verifies any hash independently — merchants should use it rather than trusting a caller's claim.
What is x402 support? Agents using the x402 convention (HTTP 402 + X-PAYMENT headers) can call x402_fetch: it fetches a URL, settles a recognized requirement exactly (policy-checked), retries with a signed proof header, and returns the payload. x402_discover finds paid resources on a domain. Details: x402 compatibility.
Does PonsMCP buy or sell launch tokens? No. Curve quotes, snipe-tax reads, and escrow balances are intelligence only. Executing trades or claiming fees stays in your own wallet by design.
Which MCP hosts work? Anything that speaks stdio MCP: Claude Desktop, Cursor, Claude Code, and custom runtimes. Read-only tools need no configuration beyond the server command.
Docs
Full manual (concepts / guides / API / x402): ponsmcp.com/docs — also in ponsmcp-docs.
License
MIT
Available Tools
9 toolspons_balanceB
Get the agent wallet balance for a token (default USDG) on Robinhood Chain.
Inputs: token.
pons_chain_infoA
Get Robinhood Chain network info: chainId, RPC, explorer, and the canonical PONS / USDG / WETH token addresses.
Inputs: no named parameters.
pons_launch_infoA
Read a pons v1 launch token directly onchain: canonical pool, fixed supply, logo, description, and social links. Names/symbols are not identity; use the token address.
Inputs: token (required).
pons_launch_marketB
Get live Robinhood Chain DEX markets, price, liquidity, and 24h change for a pons launch token address.
Inputs: token (required).
pons_payA
Execute an autonomous MPP payment: policy check, then transfer USDG on Robinhood Chain to the payTo address, then verify the on-chain receipt. Requires PONSMCP_PRIVATE_KEY env. Guards: policy limits, balance check, receipt verification.
Inputs: payTo (required), amountUsd (required), waitMs.
pons_priceB
Get the live PONS token price (USD), liquidity, and top DEX pairs on Robinhood Chain via DexScreener.
Inputs: no named parameters.
pons_quoteA
Quote a payment: converts a USD amount into USDG base units (6 decimals) and returns the settlement plan without executing.
Inputs: amountUsd (required).
pons_token_infoA
Read on-chain ERC-20 metadata for any token on Robinhood Chain: name, symbol, decimals, total supply.
Inputs: token (required).
pons_tx_statusA
Look up a transaction receipt on Robinhood Chain: status, block, gas used, and decoded ERC-20 transfers.
Inputs: txHash (required).
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
TDQS
Scored across 9 tools
Most tools target distinct operations such as price lookup, launch info, market data, token metadata, balance, quote, pay, transaction status, and chain info. Minor overlap exists between pons_price and pons_launch_market for DEX price/liquidity data, and between pons_launch_info and pons_token_info for token metadata, but descriptions clarify scope.
All tool names use the same pons_ prefix and snake_case convention, with predictable noun/verb forms like pons_price, pons_token_info, pons_pay, and pons_tx_status. There are no mixed naming styles or confusing deviations.
Nine tools is well-scoped for a Robinhood Chain token and payment server, covering read, quote, execute, and verify workflows without obvious redundancy. Each tool appears to earn its place.
The set covers core token data, market data, balance checks, payment quoting, payment execution, transaction verification, and chain info. Minor gaps remain, such as retrieving the agent wallet address, checking allowances, or viewing payment history, but these are not fatal for the main workflows.
Maintenance
Related MCP Connectors
MCP marketplace: AI agents buy services from other agents per call in USDC, plus a bank cash-out
Pay-per-call MCP tools run by autonomous AI agents, each call paid with x402 in USDC.
Let an AI agent find and pay for x402 APIs and products in USDC on Base, within owner-set limits.
28 agent tools via x402: crypto data, tx checks, web fetch. MCP pays Base USDC; HTTP adds 3 rails.
Related MCP Servers
- AlicenseAqualityDmaintenanceEnables AI agents to interact with Robinhood Chain via USDG payments, offering tools for balance, pricing, trading, and more.1848MIT

hoodr MCP Serverofficial
AlicenseNot gradedqualityCmaintenanceEnables AI agents to trade tokenized stocks (e.g., NVDA, TSLA) on Robinhood Chain via MCP, with non-custodial keys and spending caps.21 npmMIT
aeron-walletofficial
AlicenseAqualityBmaintenanceEnables agents to autonomously pay x402 API requests in USDG on Robinhood Chain while enforcing budget caps and scoped sessions.7411 npmMIT- AlicenseAqualityBmaintenanceEnables AI agents to make non-custodial USDC payments on Base through an MCP endpoint, with server-enforced per-payment and daily caps, human approval bands, and recipient allowlists.739 npmMIT