Prototype · Preview: every server in the official registry, synced every 30 minutes. Reviews and accounts come in a later step.
PopNx MCPMCP servers for people who use AI · explained in plain words

PHANTOM ID — agent payments (USDC on Base)

by Arbromagency-Satoversion 0.3.2i★ –iComputer or cloud
Registry nameio.github.Arbromagency-Sato/phantom-mcp-server

Install

Overview

Description from the maker (original English)

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

PopNx MCP’s three pillars

These three are never merged into one score: opinions, measurements and popularity are different things.

What you can do with it

We have not written a plain-language summary for this one yet. Below are the facts we read from the registry.

  • Connection: Computer or cloud
  • Transport: stdio, Streamable HTTP
  • Category: Online shops & payments
  • You need to fill in: PHANTOM_API_KEY

Install

Pick the AI app you use, then copy the settings.

Before you install

  • Basic checks: 3 of 3 passed
  • Runs on the maker’s server: what you ask it goes through their server.
  • Can do 7 things (tools) phantom_register, phantom_authorize_budget, phantom_bind_identity, quote_payment …
  • You fill in yourself: PHANTOM_API_URL, PHANTOM_API_KEY, Authorization

Values marked secret are keys to your account. Never share them or paste them into a chat.

You need

  • Runs in the cloudNothing to install; it connects over the internet
  • npmNode.js installed (for the npx command)

Which app do you use?

Pick your app above. We remember it, so next time the button says “Install in …”.

This address needs a key in a request header, which the add-connector menu cannot set. Use Claude Code, Cursor or VS Code instead.

Or run it on your computer

Open Claude Desktop → Settings → Developer → Edit Config, and paste this into claude_desktop_config.json

{
  "mcpServers": {
    "phantom": {
      "command": "npx",
      "args": [
        "-y",
        "@phantomid/mcp-server"
      ],
      "env": {
        "PHANTOM_API_URL": "your-value",
        "PHANTOM_API_KEY": "your-value"
      }
    }
  }
}

Run this in your terminal

claude mcp add --transport http phantom https://pay.idphantom.com/mcp --header 'Authorization: Bearer {PHANTOM_API_KEY}'

Or run it on your computer

claude mcp add phantom --env PHANTOM_API_URL=your-value --env PHANTOM_API_KEY=your-value -- npx -y @phantomid/mcp-server

Fill in the empty values before running it.

Open in Cursor

Or copy the settings yourself

Paste into .cursor/mcp.json in your project, or ~/.cursor/mcp.json

{
  "mcpServers": {
    "phantom": {
      "url": "https://pay.idphantom.com/mcp",
      "headers": {
        "Authorization": "Bearer {PHANTOM_API_KEY}"
      }
    }
  }
}

Or run it on your computer

Open in Cursor

Or copy the settings yourself

Paste into .cursor/mcp.json in your project, or ~/.cursor/mcp.json

{
  "mcpServers": {
    "phantom": {
      "command": "npx",
      "args": [
        "-y",
        "@phantomid/mcp-server"
      ],
      "env": {
        "PHANTOM_API_URL": "your-value",
        "PHANTOM_API_KEY": "your-value"
      }
    }
  }
}

Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.

Open in VS Code

Or copy the settings yourself

Paste into .vscode/mcp.json in your project

{
  "servers": {
    "phantom": {
      "type": "http",
      "url": "https://pay.idphantom.com/mcp",
      "headers": {
        "Authorization": "Bearer {PHANTOM_API_KEY}"
      }
    }
  }
}

Or run it on your computer

Open in VS Code

Or copy the settings yourself

Paste into .vscode/mcp.json in your project

{
  "servers": {
    "phantom": {
      "type": "stdio",
      "command": "npx",
      "args": [
        "-y",
        "@phantomid/mcp-server"
      ],
      "env": {
        "PHANTOM_API_URL": "your-value",
        "PHANTOM_API_KEY": "your-value"
      }
    }
  }
}

Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.

This address needs a key in a request header, which the add-connector menu cannot set. Use Claude Code, Cursor or VS Code instead.

Your choice stays on this device in a cookie; no account needed.

Values you fill in

  • PHANTOM_API_URL env
    PHANTOM API base URL (default https://pay.idphantom.com)
  • PHANTOM_API_KEY secret required env
    PHANTOM API key for the agent account (create via POST /v1/register or /admin/accounts)
  • Authorization HTTP header
    PHANTOM API key of the agent account

These settings are generated from the maker’s registry entry. If the README says otherwise, follow the README.

What it can do

Tool names and descriptions exactly as the server reported them on Nov 10, 2026. The maker wrote them, not us; we show them as plain text.

  • phantom_register

    One-line onboarding: creates an IDPHANTOM account for the configured payer wallet, pays the $2 USDC registration with a locally-signed EIP-712 authorization and returns the api_key. Requires PHANTOM_PAYER_PRIVATE_KEY and PHANTOM_ROUTER_ADDRESS in the environment. The api_key is s

  • phantom_authorize_budget

    Funder-signed EIP-712 AgentWalletAuthorization: lets an account spend up to max_units of USDC (6-decimal units, e.g. '1000000' = $1) with an optional daily cap, without giving away the wallet. Requires PHANTOM_FUNDER_PRIVATE_KEY in the environment; the signature is produced local

  • phantom_bind_identity

    Registers an agent_id as a portable identity for this account via POST /v1/identity/bind. The proof-of-possession is an EIP-712 IdentityBinding signature produced LOCALLY with PHANTOM_IDENTITY_PRIVATE_KEY (environment variable only, never a command-line flag — AGP-057); the priva

  • quote_payment

    Create an IDPHANTOM payment quote with transparent platform fee (0.5%, min $0.01 USDC). Returns a payment intent ready for the payer's EIP-712 signature. Free: quoting never moves funds.

  • authorize_payment

    Attach the payer's EIP-712 PaymentAuthorization signature to a quoted payment intent. The signature is produced locally by the payer's wallet; it authorizes up to maximumTotalAuthorized, expiring at expiresAt. No funds move until submit_payment.

  • submit_payment

    Broadcast an authorized payment intent through IDPHANTOM. The platform relays the on-chain transaction; exactly one broadcast per intent is enforced server-side (retries return the already-submitted transaction hash). This is the step that settles funds.

  • verify_payment

    Verify an IDPHANTOM payment receipt: cryptographic checks (EIP-712 signature, payer recovery), expiry, and the on-chain state of the authorization (free/used/cancelled). Free for receipts of payments the caller participated in; paid via the receipt-verifier for third-party receip

Basic checksi

We check information anyone can see; we have not read the code. Checks that do not apply are left out of the count. · Checked Nov 10, 2026

  • ✓ Pass

    Maker matches the repo

    The registry name was verified with the GitHub account Arbromagency-Sato, which owns the repo

  • … Not checked yet

    Still maintained

    We have not read this repo from GitHub yet

  • … Not checked yet

    Has a licence

    We have not read this repo from GitHub yet

  • ✓ Pass

    Endpoint responds

    Responded in 128 ms (HTTP 200)

  • – Not applicable

    Sign-in with OAuth

    No sign-in needed

  • ✓ Pass

    No hidden instructions in tool descriptions

    Read 7 tool descriptions and found no hidden instructions to the AI

Compared with others in Online shops & paymentsi

  • More stars than 0% of the other 2635 servers in this category
  • Published to the registry more recently than 96% of the other 2635 servers in this category
  • Basic checks equal to or better than 100% of the other 2635 servers in this category

Compared with every active server in this category in the registry. Stars count only when the publisher owns the repo.

Common questions

Is PHANTOM ID — agent payments (USDC on Base) safe?

It passed 3 of 3 applicable basic checks. We have not read the code. Before adding a key or token, see what access the server asks for and use a key with only the permissions you need.

What keys or codes does it need?

You need to fill in: PHANTOM_API_KEY

Does it run on my computer or in the cloud?

Either way works: install it on your computer or connect to the cloud version.

Is it still maintained?

The GitHub repo last changed –, and the latest version (0.3.2) reached the registry yesterday.

Which apps can use it?

Apps that support MCP, such as Claude Desktop, Claude Code, Cursor and VS Code. It connects by URL, so apps that accept remote MCP servers work too, such as ChatGPT in developer mode.

What can I use instead?

In the same category: Spree Commerce: open-source B2B and marketplace ecommerce, Stripe MCP, MCP Cn Commerce

Alternatives

Servers in the same category from other makers, sorted by stars.

Reading a card:↓ Downloads per weeki★ GitHub starsiThree pillars: reviews · checks · usageiUpdated = latest version published to the registryi

Stripe MCP

Stripe’s official server lets AI view and manage customers, products, payments and invoices. Connect to Stripe’s cloud and sign in with OAuth.

by stripeWidely used★ 2KUpdated 13 months ago

Runs in the cloud✓ stripe.com

MCP Cn Commerce

8 read-only MCP platform entries; support is operation-specific; merchant live acceptance pending

by TonyWang-hubEarly↓ 73/wk★ 96Updated 30 days ago

Runs on your computer

README from the maker

Open the README

Copied from the maker’s repo as written. PopNx MCP has not reviewed or endorsed it. HTML, images and scripts are removed. Links lead off this site.

IDPHANTOM MCP Server

@phantomid/mcp-server exposes IDPHANTOM payments as standard MCP tools so an AI agent can quote, authorize, submit, and verify agent-to-agent payments through IDPHANTOM.

Production defaults to:

https://pay.idphantom.com

Install

npx @phantomid/mcp-server

For MCP clients, configure the server command and environment:

{

"mcpServers": { "phantom-id": { "command": "npx", "args": ["@phantomid/mcp-server"], "env": { "PHANTOM_API_URL": "https://pay.idphantom.com", "PHANTOM_API_KEY": "pk_live_..." } } } }

PHANTOM_API_URL is optional when using production. PHANTOM_API_KEY is required for normal paid API usage after registration.

Self-serve tools environment (AGP-100)

The MCP tools phantom_register and phantom_authorize_budget read their signing keys only from the environment (never from command-line flags — argv leaks into shell history and process listings):

VariableUsed byPurpose
PHANTOM_PAYER_PRIVATE_KEYphantom_register (auto mode)Pays the $2 USDC registration; signs locally, never leaves the process.
PHANTOM_FUNDER_PRIVATE_KEYphantom_authorize_budgetHuman funder's key for the EIP-712 AgentWalletAuthorization.
PHANTOM_ROUTER_ADDRESSbothPhantomRouter verifying contract of the EIP-712 domain.
PHANTOM_FUNNEL_SOURCEfunnelinternal for dogfood/QA traffic (reported separately — wash volume prohibited); default external.

Without PHANTOM_PAYER_PRIVATE_KEY, phantom_register runs in manual mode: pass payer_wallet and it returns the registration challenge plus step-by-step signing instructions.

Funnel events (AGP-100 F1.4)

The server emits one JSON line per event on stderr, prefixed with [funnel]:

[funnel] {"event":"install","ts":"...","source":"external",...}

Events: install → register_start → register_complete → first_pay → repeat. Scrape these lines to build the onboarding funnel (install → register → first pay → repeat). Traffic tagged PHANTOM_FUNNEL_SOURCE=internal must be aggregated separately from external volume.

Connect Your Agent In 5 Minutes

Registration is self-serve and costs $2 USDC on Base mainnet. The CLI signs locally and never prints the private key.

export PHANTOM_PAYER_PRIVATE_KEY="0x..."

export PHANTOM_ROUTER_ADDRESS="0x..." npx @phantomid/mcp-server init --name my-agent

The init flow calls:

  1. POST /v1/register
  2. POST /v1/intents/:id/authorize
  3. POST /v1/intents/:id/submit
  4. GET /v1/register/:reference
  5. POST /v1/register/:reference/claim

On success it prints the account id and the API key once. Store the returned key as PHANTOM_API_KEY.

Flags are supported for non-sensitive options. The payer key is environment-only (never a flag — command lines leak into shell history and process listings):

export PHANTOM_PAYER_PRIVATE_KEY="0x..."

npx @phantomid/mcp-server init \ --api-url https://pay.idphantom.com \ --router-address 0x... \ --name my-agent

Tools

The server supports newline-delimited JSON-RPC over stdio.

quote_payment
{

"jsonrpc": "2.0", "id": 1, "method": "tools/call", "params": { "name": "quote_payment", "arguments": { "payer_wallet": "0x...", "recipient_wallet": "0x...", "asset_contract": "0x...", "amount": "1000000", "chain_id": 8453, "idempotency_key": "quote-001", "payer_agent_id": "buyer-agent", "recipient_agent_id": "seller-agent" } } }

authorize_payment
{

"jsonrpc": "2.0", "id": 2, "method": "tools/call", "params": { "name": "authorize_payment", "arguments": { "payment_intent_id": "pi_...", "payer_signature": "0x..." } } }

submit_payment
{

"jsonrpc": "2.0", "id": 3, "method": "tools/call", "params": { "name": "submit_payment", "arguments": { "payment_intent_id": "pi_..." } } }

verify_payment
{

"jsonrpc": "2.0", "id": 4, "method": "tools/call", "params": { "name": "verify_payment", "arguments": { "payment_intent_id": "pi_...", "receipt_id": "rcpt_..." } } }

Limits

Default production policy limits are:

  • 50 USD maximum per payment
  • 500 USD maximum per day

Payments above those limits are rejected by the PHANTOM ID API.

Publish

npm publish --access public
Ask PopNx