pons Launchpad (Robinhood Chain)

io.github.hoodly-agentPublished by GitHub account hoodly-agentv0.1.0Updated Oct 24, 2026

Dual-version MCP for pons token launches on Robinhood Chain: v1 trading, v2 curve reads (plan-only).

The publisher's own server: Agent.chain.tokyo Address Contracts

VerifiedStreamable HTTPWeb executableFinanceSecurity & Monitoring

Overview

AI-generated overview

Remote MCP server for the pons token launchpad on Robinhood Chain, letting an assistant spot launches, check tokens, preview trades and trade with approval.

What you can do
Discover new token launches as they happen and check whether a token genuinely came from pons or is a copycat using a similar name or logo. Track a token's price and how close it is to graduating to a full exchange listing, and see recent buying and selling activity. Preview a trade with expected price, cost and outcome before anything happens. Create a dedicated wallet for the assistant and carry out a trade only after review and approval. Show details of the newer curve-pricing version and prepare trades on it in advance, without completing real trades there.
When to use it
Useful if you follow token launches on Robinhood Chain and want an assistant to monitor new tokens, verify authenticity, watch prices and activity, and prepare or execute small trades under your approval.
Requirements
A remote MCP endpoint reached over streamable HTTP; no package, environment variables or headers are declared. Trading must be switched on before the assistant can trade, and a daily spending limit is set by you.
Before you install
Trading moves real funds once enabled; new wallets start in a simulated practice mode until you turn that off. The assistant's wallet is separate from your personal wallet, and it will reveal that wallet's private key if you explicitly ask. Trades require your review and approval, and the newer version is still being audited, so real trades there are not completed.

Installation

In SourceWeft

  1. Open pons Launchpad (Robinhood Chain) in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.

Use with an agent

Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.

Read https://sourceweft.com/mcp/io.github.hoodly-agent%2Fmcp-pons/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config.

{
  "mcpServers": {
    "pons-launchpad-robinhood-chain": {
      "type": "http",
      "url": "https://mcp-pons.hoodly.ai/mcp"
    }
  }
}

README

pons-hoodly MCP Server

This project connects an AI assistant (like Claude) to pons, a token launchpad on Robinhood Chain — so your assistant can look things up, keep watch, and trade on your behalf, always with your permission.

MCP is simply the connection that lets an AI assistant use real, live tools instead of guessing or making things up. Once connected, your assistant can reach directly into pons instead of relying on outdated or secondhand information.

What your assistant can do once connected

  • Spot new token launches as they happen
  • Check whether a token genuinely came from pons, or is a copycat using a similar name or logo
  • Track a token's price and how close it is to graduating to a full exchange listing
  • See recent buying and selling activity on a token
  • Preview a trade — expected price, cost, and outcome — before anything happens
  • Create a dedicated wallet just for the assistant to use
  • Carry out a trade, but only after you've reviewed and approved it

Built-in safety

  • Trading is switched off by default. You have to turn it on before your assistant can trade at all.
  • New wallets start in a safe practice mode where trades are simulated, not real, until you turn that off.
  • You set a daily spending limit, so the assistant can never spend more than you're comfortable with.
  • The assistant's wallet is separate from your personal wallet. Your own funds and keys are never touched.
  • The assistant will only reveal a wallet's private key if you explicitly ask it to.

A note on the newest version

pons is rolling out a new version with features like automatic bonding-curve pricing and graduation to a new exchange. That version is still being audited and hasn't officially launched yet, so your assistant can show you everything about it and prepare trades in advance, but won't complete a real trade on it until pons confirms it's ready.

Source: README.md at commit f7bd6fe

Tools

0
SourceWeft has not read this server's tools yet.

Version history

1
  1. v0.1.0LatestSep 16, 2026

Score

40% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 daysRequired25 pts

    Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.

  • Auth declaredRequired10 pts

    Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.

  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts
  • License10 pts

    Declare a license in the repository or the registry entry.

Other Chain integrations