Phantom MCP Server logo

Phantom MCP Server

Quotes, authorizes, submits, and verifies agent-to-agent USDC payments on Base through IDPHANTOM.

Install Phantom MCP Server

Pick your client, then add it in one click or paste the config.

STDIONode.js
~/Library/Application Support/Claude/claude_desktop_config.json
claude_desktop_config.json
{
  "mcpServers": {
    "phantom-mcp-server-2": {
      "command": "npx",
      "args": [
        "@phantomid/mcp-server"
      ],
      "env": {
        "PHANTOM_API_KEY": "YOUR_VALUE_HERE",
        "PHANTOM_API_URL": "YOUR_VALUE_HERE",
        "PHANTOM_PAYER_PRIVATE_KEY": "YOUR_VALUE_HERE",
        "PHANTOM_ROUTER_ADDRESS": "YOUR_VALUE_HERE",
        "PHANTOM_ALLOW_CUSTOM_API_URL": "YOUR_VALUE_HERE"
      }
    }
  }
}

Settings → Developer → Edit Config, merge this into mcpServers, then fully quit and reopen Claude Desktop.

Values are written into the snippet above so you can paste it as is. They never leave your browser.

We couldn’t confirm it starts correctly

The install command started, but didn't respond the way we expected when we tried to talk to it.

npx @phantomid/mcp-server

initialize succeeded but no response to tools/list.

This is an experimental automated check and can have false negatives — missing environment variables, a slow cold install, etc. It doesn’t necessarily mean something’s wrong. Last checked 6d ago.

Overview

The phantom-mcp-server MCP server exposes IDPHANTOM payment operations to AI agents through standard MCP tools. It communicates with the IDPHANTOM API over newline-delimited JSON-RPC on stdio, using the production endpoint by default. Agents can request payment quotes, authorize and submit payment intents, and verify receipts. Use it when an agent needs an API-based workflow for USDC payments between wallets on Base.

Use cases

  • Quote agent-to-agent USDC payments
  • Authorize signed payment intents
  • Submit payments on Base
  • Verify payment receipts
  • Register an IDPHANTOM agent

Key features

  • Payment quoting
  • Payment authorization
  • Payment submission
  • Receipt verification
  • Base USDC payment flow
  • stdio JSON-RPC transport

Tools4

What Phantom MCP Server lets your agent do. Expand a tool for its parameters.

Self-reported~22 tokens of context

Security & health

What it can reach and how reliably it runs — from our own checks, not the maintainer’s claims.

ActiveLast checked 1d ago

Recent health check succeeded.

6/6 checks healthy over the last 22d

Supply-chain signal

No high-severity advisories surfaced by our automated scan.

Critical 0High 0Medium 0Low 0

Scanned 9d ago via OSV.dev · @phantomid/mcp-server (npm)

Adoption & maintenance

Factual signals from GitHub, npm, and our automated checks — not a rating.

npm downloads1.8kPackage downloads in the last 30 days.
Last commit24d agoMost recent push to the default branch.
Install checkInconclusiveStarted but did not complete the MCP handshake in our test.
Tools exposed4Callable tools this server registers over MCP.
Directory activity1 viewsConfig copies, upvotes, and views on AllMCPs.

How Phantom MCP Server works

What phantom-mcp-server MCP server does

phantom-mcp-server MCP server connects an MCP-compatible agent to IDPHANTOM payments. It supports an agent-to-agent payment flow using USDC on Base, with separate operations for preparing a quote, authorizing a payment intent, submitting it, and checking the resulting payment.

The production API endpoint is https://pay.idphantom.com. Normal paid API usage requires an API key issued during registration. The repository contains the connector source code; the hosted IDPHANTOM service, payment engine, infrastructure, and related backend systems remain separate proprietary components.

How it works

The server runs as an npm package with npx @phantomid/mcp-server. MCP clients communicate with it over newline-delimited JSON-RPC using stdio. Each operation is invoked through tools/call with a tool name and structured arguments.

A typical payment workflow starts with quote_payment. The caller supplies payer and recipient wallets, an asset contract, an amount, chain ID, an idempotency key, and optional agent identifiers. The returned payment intent can then be passed to authorize_payment with a payer signature. submit_payment sends the authorized intent for processing, while verify_payment checks the intent together with a receipt ID.

The included initialization flow registers an agent and completes the associated payment steps through the IDPHANTOM API. It then retrieves the registration result and claims the account, printing the account ID and API key once. The returned key should be stored as PHANTOM_API_KEY.

Setup and configuration

Install or run the package with:

Terminal
npx @phantomid/mcp-server

Configure the MCP client command with npx, the package name, and environment variables. PHANTOM_API_URL may be omitted when using production. PHANTOM_API_KEY is required for normal paid API requests.

Registration uses PHANTOM_PAYER_PRIVATE_KEY and PHANTOM_ROUTER_ADDRESS. The payer key must be supplied through the environment rather than a command-line flag. Registration costs $2 USDC on Base mainnet, and the CLI signs locally without printing the private key.

Custom or self-hosted API endpoints require PHANTOM_ALLOW_CUSTOM_API_URL=1 or the equivalent command-line option. Without that override, the client accepts only trusted IDPHANTOM domains, localhost, and loopback addresses before sending credentials.

Tools and capabilities

phantom-mcp-server MCP server provides four payment tools:

  • quote_payment creates or retrieves a payment quote.
  • authorize_payment authorizes a payment intent with a payer signature.
  • submit_payment submits an authorized payment intent.
  • verify_payment checks a payment intent and receipt.

The default production policy rejects payments above $50 per transaction or $500 per day. These limits are enforced by the IDPHANTOM API.

Limitations and notes

Production limits may prevent larger transfers even when the tool arguments are otherwise valid. The repository's MIT license applies to the connector source code only, not to IDPHANTOM's hosted APIs or backend services.

Use the custom endpoint override carefully because it changes the list of destinations to which credentials may be sent. Keep the payer private key out of flags, shell history, and process listings by providing it only through the environment.

Reviews

No reviews yet — be the first to share how it worked for you.

Frequently Asked Questions about Phantom MCP Server

phantom-mcp-server is an MCP server that connects AI agents to the IDPHANTOM payment API for agent-to-agent USDC payments on Base. Its main tools quote payments, authorize payment intents, submit authorized payments, and verify payments with receipt IDs over a standard stdio MCP connection.

Install it by running `npx @phantomid/mcp-server` and configuring that command in your MCP client. Set `PHANTOM_API_KEY` for normal paid API usage; `PHANTOM_API_URL` is optional when using the production endpoint.

Register an agent by setting `PHANTOM_PAYER_PRIVATE_KEY` and `PHANTOM_ROUTER_ADDRESS`, then running `npx @phantomid/mcp-server init --name my-agent`. The flow costs $2 USDC on Base mainnet and prints the API key once after successful registration.

Yes, but custom endpoints require `PHANTOM_ALLOW_CUSTOM_API_URL=1` or the `--allow-custom-api-url` option. Without that override, the client accepts trusted IDPHANTOM origins, localhost, and 127.0.0.1.

The default production limits are $50 per payment and $500 per day. Payments exceeding either limit are rejected by the PHANTOM ID API.

Related MCP servers

Add a badge to your READMEShow it’s listed — live SVG, Markdown or HTML.

AllMCPs Directory Badge

Full Badge Customizer

Showcase your server listing on GitHub or your project documentation. Embed this dynamic SVG badge to highlight official listing status and live engagement.

Badge Style:
Live Dynamic SVG PreviewPhantom MCP Server AllMCPs Directory Badge
Markdown (GitHub README)
[![AllMCPs](https://allmcps.com/api/badge/phantom-mcp-server-2?style=directory)](https://allmcps.com/mcp/phantom-mcp-server-2)
HTML Embed
<a href="https://allmcps.com/mcp/phantom-mcp-server-2"><img src="https://allmcps.com/api/badge/phantom-mcp-server-2?style=directory" alt="Phantom MCP Server on AllMCPs" /></a>