PonsMCP
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| PONSMCP_MAX_PER_TX | No | Optional maximum USDG spend per transaction, in micro-units (e.g. 100000000 = 100 USDG). | |
| PONSMCP_DAILY_LIMIT | No | Optional maximum USDG spend per day, in micro-units (e.g. 1000000000 = 1000 USDG). | |
| PONSMCP_PRIVATE_KEY | Yes | Agent wallet private key. The wallet should be funded with a little ETH for gas and USDG for payments. |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| pons_chain_infoA | Get Robinhood Chain network info: chainId, RPC, explorer, and the canonical PONS / USDG / WETH token addresses. |
| pons_priceB | Get the live PONS token price (USD), liquidity, and top DEX pairs on Robinhood Chain via DexScreener. |
| 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. |
| pons_launch_marketB | Get live Robinhood Chain DEX markets, price, liquidity, and 24h change for a pons launch token address. |
| pons_token_infoA | Read on-chain ERC-20 metadata for any token on Robinhood Chain: name, symbol, decimals, total supply. |
| pons_balanceB | Get the agent wallet balance for a token (default USDG) on Robinhood Chain. |
| pons_quoteA | Quote a payment: converts a USD amount into USDG base units (6 decimals) and returns the settlement plan without executing. |
| 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. |
| pons_tx_statusA | Look up a transaction receipt on Robinhood Chain: status, block, gas used, and decoded ERC-20 transfers. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
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.