PonsMCP
Integrates with Robinhood Chain (chainId 4663) for autonomous on-chain MPP payments, including quoting, executing, and verifying USDG transfers, checking agent wallet balances, fetching chain info, retrieving token metadata, and checking transaction status on the Robinhood Chain network.
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 check my PONS price and USDG balance"
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 + SDK
Model Context Protocol server for autonomous MPP payments with PONS on Robinhood Chain (chainId 4663).
What is this?
@ponsmcp/sdk ships an MCP server (ponsmcp binary) plus a TypeScript client that lets AI agents pay for services autonomously using Stripe's Machine Payments Protocol semantics — settled on-chain in USDG on Robinhood Chain, with the PONS token as the ecosystem asset.
Everything is real: live RPC calls, real ECDSA signing, real receipt verification. No mocks.
Related MCP server: pons-hoodly MCP Server
Tools exposed to the agent
Tool | What it does |
| Chain facts: RPC, chainId 4663, explorer, canonical token addresses |
| Live PONS price, liquidity, top pairs (DexScreener) |
| Verified onchain pons v1 launch metadata, canonical pool, and social links |
| Live Robinhood Chain markets for a pons launch-token address |
| On-chain ERC-20 metadata for any token |
| Agent wallet balance (USDG by default) |
| USD → USDG settlement plan (no execution) |
| Execute a payment: policy → transfer → receipt verification |
| Receipt lookup with decoded transfers |
Quick start (as an MCP server)
npm install -g @ponsmcp/sdk
export PONSMCP_PRIVATE_KEY=0x... # agent wallet (funded with a little ETH for gas + USDG)
export PONSMCP_MAX_PER_TX=100000000 # optional: 100 USDG cap per tx (micro-units)
export PONSMCP_DAILY_LIMIT=1000000000 # optional: 1000 USDG daily cap
ponsmcpThen register in any MCP client:
{
"mcpServers": {
"ponsmcp": {
"command": "ponsmcp",
"env": { "PONSMCP_PRIVATE_KEY": "0x..." }
}
}
}Quick start (as a library)
import { PonsMCPClient } from '@ponsmcp/sdk'
const client = new PonsMCPClient({ privateKey: process.env.PONSMCP_PRIVATE_KEY })
// Quote
const q = await client.quote('5.00') // → 5_000_000 USDG micro-units
// Pay: policy check → ERC-20 transfer → receipt verification
const result = await client.pay({
payTo: '0x...',
amountUsd: '5.00',
})
console.log(result.stage) // 'confirmed'
console.log(result.txHash)
console.log(result.explorer)Network
Setting | Value |
Chain | Robinhood Chain (Arbitrum Orbit L2) |
Chain ID |
|
RPC |
|
Explorer |
|
PONS |
|
USDG |
|
Safety model
Policy engine — hard per-tx and daily caps (env-tunable), checked before any broadcast
Balance pre-check — refuses to broadcast when funds are insufficient
Receipt verification — a payment is "confirmed" only when the on-chain receipt is status
0x1with the expected USDG Transfer eventDeterministic signing — canonical low-s ECDSA signatures, EIP-155 replay protection (chainId 4663)
Architecture
src/
├── mcp.ts # MCP stdio server (tools/list, tools/call)
├── index.ts # PonsMCPClient: quote → policy → sign → broadcast → verify
├── chain.ts # Robinhood Chain JSON-RPC + ABI helpers
├── erc20.ts # ERC-20 reads
├── dexscreener.ts # PONS / pons launch-token live market data
├── pons.ts # pons v1 launch-token metadata + canonical pool reads
├── policy.ts # spending-policy engine
└── crypto.ts # keccak256 + RLP + secp256k1 (zero deps, live-tested)License
MIT — see LICENSE.
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
Each tool targets a distinct resource or action: chain info, PONS price, launch metadata, launch market data, generic token metadata, wallet balance, payment quote, payment execution, and transaction status. The potential overlap between pons_price and pons_launch_market is resolved by scope (PONS token vs. arbitrary launch token address), and pons_launch_info vs. pons_token_info is resolved by launch-specific metadata vs. generic ERC-20 metadata.
All tools use a consistent pons_ prefix with lower snake_case, making the surface predictable and readable. Although some names are noun phrases and others are verbs, the convention is uniform and the specific pattern does not hinder discovery.
Nine tools are well-scoped for a Robinhood Chain payment and token-inspection server. Each tool has a clear role, and the count avoids both thinness and bloat.
The surface covers the core lifecycle: chain info, token data, market data, balance checks, payment quote, payment execution, and receipt lookup. Minor gaps exist, such as no tool to list or discover launch tokens and no explicit wallet-address lookup, but these are workable around external data.
Maintenance
Related MCP Connectors
Agent-to-agent escrow on Robinhood Chain. Post quests with ETH/USDG bounties and settle on-chain.
Token swaps and honeypot/rug checks for AI agents on 8 chains, paid per-call in USDC via x402.
Wallet and payments for AI agents: auto-pay x402 APIs in USDC on XDC, within on-chain limits.
USDC wallets, payment links and x402 payments on Solana for AI agents.
Related MCP Servers
- AlicenseAqualityDmaintenanceEnables AI agents to interact with Robinhood Chain via USDG payments, offering tools for balance, pricing, trading, and more.1848MIT
- AlicenseNot gradedqualityDmaintenanceEnables AI assistants to interact with the pons token launchpad on Robinhood Chain for token discovery, verification, price tracking, and trading with built-in safety controls and user approval.MIT
- AlicenseNot gradedqualityCmaintenanceEnables 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.32 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