Skip to main content

PHANTOM ID — agent payments (USDC on Base)

io.github.Arbromagency-Sato/phantom-mcp-serverVersion 0.3.2

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

Status

Responds295 msAnswered our handshake without sign-in.

Registry data may be out of date

We could not refresh it, so this page shows the last copy.
Last checked
Nov 14, 2026, 14:35 UTC
Latency
295 ms
Remotes responding
1 of 1
Sign-in
No sign-in
Hosting
Hosted outside the EU (detected)
Registry data as of
Nov 14, 2026, 22:14 UTC

Data from the official MCP Registry, checked by run.zero. How we check

Connect

Streamable HTTP
https://pay.idphantom.com/mcpResponds295 ms
No sign-in

Claude Code

claude mcp add --transport http phantom-mcp-server https://pay.idphantom.com/mcp

Claude Desktop and claude.ai

Settings > Connectors > Add custom connector
Name: phantom-mcp-server
Remote MCP server URL: https://pay.idphantom.com/mcp

Cursor

{
  "mcpServers": {
    "phantom-mcp-server": {
      "url": "https://pay.idphantom.com/mcp"
    }
  }
}

VS Code

code --add-mcp '{"name":"phantom-mcp-server","type":"http","url":"https://pay.idphantom.com/mcp"}'
Streamable HTTP
npm: @phantomid/mcp-server 0.3.2
Package only

npm (npx)

claude mcp add phantom-mcp-server -e 'PHANTOM_API_KEY=<YOUR_PHANTOM_API_KEY>' -- npx -y @phantomid/mcp-server@0.3.2

Replace <YOUR_PHANTOM_API_KEY> before running.

Built your own server? run.zero hosts MCP servers on European infrastructure.

Host your own MCP server on run.zero

Tools

7 tools

Tools of PHANTOM ID — agent payments (USDC on Base)
Read-only
Idempotent
Open world
authorize_paymentAttach 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.NoNoYesYes
phantom_authorize_budgetFunder-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 locally. Policy templates: 'micro' ($1/tx, $5/day, 30d) and 'subscriptions' ($2/tx, $5/day, 30d) — pilot caps kept deliberately low; explicit max_units/daily_cap_units/expires_in_days override any template. The account's own api_key is sent as authentication (first binding requires it).NoNoNoYes
phantom_bind_identityRegisters 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 private key never leaves this process, only the signature is sent. Idempotent: replaying the same bind returns the existing binding. attestation_address comes from GET /.well-known/phantom-identity.json of the PHANTOM deployment (field attestation_address) — pass it here together with the chain_id so the local signature domain matches the server's. Key rotation is NOT exposed here (it needs the old AND new keys); call POST /v1/identity/rotate directly instead.NoNoYesYes
phantom_registerOne-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 shown exactly ONCE in this response — store it as PHANTOM_API_KEY immediately. Without a payer key configured, pass payer_wallet to get manual instructions instead.NoNoNoYes
quote_paymentCreate 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.NoNoYesYes
submit_paymentBroadcast 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.YesNoYesYes
verify_paymentVerify 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 receipts.NoYesYesYes

Details

Registry status
Active
Published
Nov 8, 2026
Updated
Nov 8, 2026
Categories (suggested)
Finance and paymentsSuggested categories are assigned automatically from the registry text and may be wrong. Verified operators can correct them.
GDPR
Not declared

Are you the operator? Claim this listing