Skip to content
Menu

Pons MCP

$MCP

Payments · Utility

Researched

Autonomous payments for AI agents. MCP server + SDK for the Machine Payments Protocol. Settlement runs transparently on-chain, in USDG, on Robinhood Chain 4663. Pons MCP bridges AI agents with Stripe's Machine Payments Protocol, enabling autonomous service payments with transparent Robinhood Chain settlement. - MPP Integration Native support for Stripe's Machine Payments Protocol. Agents discover services, interpret 402 responses, and authorize payments. - On-chain Settlement USDG transfers settle transparently on Robinhood Chain (4663). Every payment ends with a verifiable receipt. - Policy Protection Per-transaction and daily caps are enforced before any funds move. Balance is checked before broadcast. - Local Key Control Signing lives in the configured MCP server process — never in the browser, never in third-party code. - pons Intelligence Read pons v1 launch metadata, canonical pools, socials, and live markets directly from agent tool calls. - Receipt Verification A payment is complete only when the on-chain receipt confirms the exact USDG transfer to the merchant.

Read more

What HEY knows

Building
No builder source linkedHEY holds no repository, changelog or feed it can read, so no count here is a measured zero.
FollowCreate alertTerminal previewShare on X

Follow puts Pons MCP on your private watchlist and at the top of “Since you were last here” when you come back. Then pick what HEY should notify you about. Following needs an account; browsing never does.

Without an account:RSS
Email me Pons MCP’s changes

No account and no password. HEY stores the address and what you asked for, sends one confirmation, and nothing else until you confirm. Every email has a one-click unsubscribe that deletes the address.

Known so far
Contract
0x15da…6b8a0x15da2596f4c21227185466066bf0f19d9d526b8a
Deployed
2026-10-02, read from the chain
Launched via
Pons
Token market
Launch pool only$24K fully diluted valuationToken unverifiedHEY found this token through a launchpad record. The declared site does not name the contract, so HEY does not treat it as confirmed by the project. Token discovery alone never establishes ownership.
Contract events
6,709 on 2026-10-03 (UTC), read from the chain 40m ago. Events say the contract is used, not that anyone is building.
Links
WebsiteX
Latest read
HEY last read this project’s records 54m ago.

What HEY can’t verify yet

  • Building activity — No repository, changelog or feed to read.
  • Repositories — No repository the project claims as its own.
  • Releases — No repository, changelog or feed to read.
  • Official docs — Only docs others link to; none the project publishes itself.
  • Official site changes — Its website is not yet confirmed as the project’s own.
  • Verified source — HEY has not read the contract’s published source yet.
  • Contract interface — HEY has not read the contract’s published source yet.
  • Market history — No daily market history recorded yet.
  • Supply distribution — HEY has not mapped this token’s supply yet.

HEY can answer 7 of the 16 research questions that apply · Research coverage

What HEY is researching

  • Still to read: Verified source, Contract interface, Supply distribution.
Compare with…What Terminal access adds →
What HEY checked — why it says this
No builder source linked.
HEY holds no repository, changelog or feed it can read building from, so it cannot say whether anyone is building.
SourceHEY holds no repository, changelog or feed it can read for this project.ReadWhat HEY derivedThe activity rule under hbm-v23 gives UNKNOWN.Not concludedIt says what HEY can read of the building, not how good the project is, who is behind it, or what its token will do. Quiet or unknown is not "abandoned".
Researched.
HEY researched this project; the gate has not found verified building evidence from its own sources.
Source4 registered sources, 3 of them context only.ReadWhat HEY derivedRESEARCHED (QUALIFIED).Not concludedA verified builder is one whose shipping HEY confirmed from public evidence. It does not say who runs the project — that is the ownership claim, a separate check.
Token unverified.
UNVERIFIED: HEY found the token through a launch record or a market listing, and nothing the project published names it.
SourceThe project's own published sources and HEY's check of the contract.What HEY derivedUNVERIFIED (launchpad_record_site_silent).Not concludedIt says whether the project itself names this contract. It is not a safety check, and a token is not the project.
Launch pool only.
The market is active market because launch pool trading.
Source5 readings from HEY's own market tables.ReadWhat HEY derivedClassified ACTIVE_MARKET (launch_pool_trading).Not concludedMarket status is context only. It never changes activity status or Build Momentum, and it is not a view on the price.
Market figures are context only and never change activity status. Methodology
LinksWebsite (context only)XDEX ScreenerRHToolsSources

Research notes

Written by HEY researchers and reviewed before publishing. Commentary with sources — not the project's own claims, and not evidence of shipping.

Know something about Pons MCP? Sign in with GitHub to submit a research note. Notes are reviewed before they appear here.

Research coverage

HEY can answer 7 of the 16 research questions that apply.

7 of 16 applicable dimensions measuredShow each dimension

Identity

  • IdentityMeasuredRead 10h ago.

Building

  • Building activityNo sourceNo repository, changelog or feed to read.
  • RepositoriesNo sourceNo repository the project claims as its own.
  • ReleasesNo sourceNo repository, changelog or feed to read.
  • TimelineMeasured

Official site

  • Official docsNo sourceOnly docs others link to; none the project publishes itself.
  • Official site changesNo sourceIts website is not yet confirmed as the project’s own.

Contracts

  • Contract creationMeasuredRead 54m ago.
  • Contract activityMeasuredRead today.
  • Verified sourceNot enough yetHEY has not read the contract’s published source yet.
  • Contract interfaceNot enough yetHEY has not read the contract’s published source yet.

Market

  • Current marketMeasuredRead 1h ago.
  • Market historyNot enough yetNo daily market history recorded yet.
  • Supply distributionNot enough yetHEY has not mapped this token’s supply yet.
  • LocksMeasuredRead 1h ago.
  • Market checksMeasured

Not applicable here: API description, Repository details, Published packages, Package advisories, Protocol economics.

A count of what HEY has read, never a score: projects are not compared or ordered by it. Unknown is never zero. The same states: coverage API.

Sources

  • Website
    https://ponsmcp.com/Context onlyContext only because HEY reached this site through a launch record or a listing and nothing yet ties it to this token; it counts once the site names the token’s contract, the team submits or claims the project, or a repository HEY verified links to it.
  • Docs
    https://ponsmcp.com/docsContext onlyContext only because HEY reached this site through a launch record or a listing and nothing yet ties it to this token; it counts once the site names the token’s contract, the team submits or claims the project, or a repository HEY verified links to it.
  • GitHub org
    https://github.com/ponsmcpaiContext onlyContext only because a launch record or a listing declared this repository and nothing yet ties it to this token; it counts once the project’s own site links it or the repository names the token’s contract.
  • X
    https://x.com/Pons_MCPFrom a launch or market listing
Contract
0x15da…6b8a0x15da2596f4c21227185466066bf0f19d9d526b8a