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
Power your agent
Yayıncının kendi URL'si. PlugMCP uç noktası değildir.
Host a copy with our keys and logs.
https://pay.idphantom.com/mcpYukarıdaki Claude düğmesi, ad ve URL doldurulmuş olarak Claude'u açar. Onayı yine orada siz verirsiniz.
claude mcp add --transport http io.github.arbromagency-sato-phantom-mcp-server https://pay.idphantom.com/mcpRun in a terminal.
{ "mcpServers": { "io.github.arbromagency-sato-phantom-mcp-server": { "command": "npx", "args": [ "-y", "mcp-remote", "https://pay.idphantom.com/mcp" ] } }}claude_desktop_config.json
Uzak URL mi, yoksa makinenizde bir komut mu? İki kurulum arasındaki fark
PlugMCP’de çalıştır
A new server you create. It is not this listing's official endpoint. Use the publisher install when you want their URL and their credentials.
BaşlatYayıncıdan
@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
PHANTOM ID MCP payment server: agent-to-agent USDC payments on Base.
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.
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):
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.
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.
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:
POST /v1/registerPOST /v1/intents/:id/authorizePOST /v1/intents/:id/submitGET /v1/register/:referencePOST /v1/register/:reference/claimOn 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
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_..."
}
}
}
Default production policy limits are:
Payments above those limits are rejected by the PHANTOM ID API.
npm publish --access public
PHANTOM ID MCP payment server: agent-to-agent USDC payments on Base.
{ "mcpServers": { "io.github.arbromagency-sato-phantom-mcp-server": { "url": "https://pay.idphantom.com/mcp", "headers": {} } }}Araçlar
Henüz araç listesi yok. Uzak sunucular ilk sağlık kontrolünden sonra bir liste alır.
SSS
Bu sayfadan Cursor, Claude Desktop, Claude Code veya VS Code için http yapılandırmasını kopyalayın. PlugMCP proxy'sini değil, yayıncının kurulumunu kullanır.
Yayıncı şu ortam değişkenlerini listeliyor: PHANTOM_API_URL, PHANTOM_API_KEY.
PHANTOM ID — Agent Payments (USDC On Base) sunucusuna HTTP üzerinden ulaşılır.
Son kontrol: 2026-11-15. PHANTOM ID MCP payment server: agent-to-agent USDC payments on Base.