Skip to main content
Glama
ponsmcppayment

PonsMCP

by ponsmcppayment
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Related Servers

Alternatives to PonsMCP

No user-submitted related servers found.

    Related Servers

    • r0x-os

      nhevers
      A
      license
      A
      quality
      F
      maintenance
      Enables AI agents to interact with Robinhood Chain via USDG payments, offering tools for balance, pricing, trading, and more.
      18
      58
      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.
      99 npm
      MIT

    • pons-hoodly MCP Server

      hoodly-agent
      F
      license
      Not graded
      quality
      C
      maintenance
      Enables 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.
      -

    • veyra-mcp

      zapxlabs
      A
      license
      A
      quality
      B
      maintenance
      Enables 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.
      7
      57 npm
      MIT
    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.8/5.0

    Scored across 9 tools

    Disambiguation5/5

    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.

    Naming Consistency5/5

    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.

    Tool Count5/5

    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.

    Completeness4/5

    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

    ActivityMaintained
    ResponsivenessNo issues

    Resources