MCP servers · arbromagency-sato

PHANTOM ID agent payments (USDC on Base)

An MCP server that exposes PHANTOM ID payment operations as tools so an AI agent can quote, authorize, submit and verify USDC payments between agents on Base.

This text was machine-translated from the publisher's own information and has not been checked by a human editor. The publisher's original text is the reference.

This resource was imported automatically from the sources listed below and has not been reviewed by the AI Gate team yet. The description is the publisher's own, as published. Check the repository before installing.

What it does

The server exposes PHANTOM ID payments as standard MCP tools: quote_payment, authorize_payment, submit_payment and verify_payment. An AI agent can use them to make agent-to-agent payments in USDC on Base. It communicates over newline-delimited JSON-RPC on stdio and writes one JSON line per onboarding event to stderr, covering install, registration, first payment and repeat payment, so the flow can be tracked separately from internal test traffic.

A developer would reach for it to give an agent the ability to pay other agents in USDC on Base within set spending caps. It also suits teams that want to measure how users move from installation to registration and first payment.

Setup means configuring the server command and environment in an MCP client. Registration is self-serve and costs $2 USDC on Base mainnet; the setup CLI signs locally. Signing keys are read only from environment variables, not command-line flags. The API key returned at registration must be stored as PHANTOM_API_KEY for paid usage. Optional variables set the PhantomRouter contract address and tag traffic as internal or external.

Limitations and requirements

Registration costs $2 USDC on Base mainnet. Paid API usage requires a PHANTOM_API_KEY obtained after registration. Registration with automatic payment needs a payer private key in the environment, and budget authorization needs a funder private key. Keys must never be passed as command-line flags. Default production limits are 50 USD per payment and 500 USD per day; payments above these limits are rejected by the PHANTOM ID API.

Safety

Our team has not reviewed this resource. Only automated rules checked it; resources with high-risk signals are not published. These are signals, not a guarantee that installing it is safe. Try it in a sandbox project first.

  • Runs code or changes an assistant's behaviour

Sources

  • Official MCP Registry first seen 13 Nov 2026 · last seen 13 Nov 2026 · its page on the source
    PHANTOM ID — agent payments (USDC on Base)

    PHANTOM ID MCP payment server: agent-to-agent USDC payments on Base.

    v0.3.2
    As shown on registry.modelcontextprotocol.io when we last read it
MCP servers
cloudflare

Cloudflare MCP servers

Cloudflare's hosted MCP servers for its products: documentation search, sandbox containers, browser rendering, Radar internet data, logs and analytics, Workers and more.

4.5K GitHub starsCloud & DevOpsSoftware development
Updated 17 Nov 2026
MCP servers
redis

Redis MCP Server

Redis's official MCP server that lets an AI assistant store, read and search data in a Redis database, including streams, JSON documents and vector indexes.

642 GitHub starsData & databasesSoftware development
Updated 17 Nov 2026
MCP servers
microsoft

Playwright MCP (browser automation)

Microsoft's MCP server that lets an AI assistant open web pages, click, type and read them through a real browser, using the page structure instead of screenshots.

39.6K GitHub starsTesting & QAWeb, search & browser
Updated 17 Nov 2026
MCP servers
hashicorp

Terraform MCP Server (HashiCorp)

HashiCorp's MCP server that gives an assistant current Terraform Registry information on providers, modules and policies, and can manage HCP Terraform workspaces.

1.6K GitHub starsCloud & DevOpsSoftware development
Updated 17 Nov 2026