# phantom-mcp-server [Health: Active]

**Category:** 💰 Finance & Fintech  
**Repository:** https://github.com/Arbromagency-Sato/idphantom-mcp-server  
**GitHub Stars:** 0  
**npm Downloads (last month):** 2132  
**Views:** 0  
**Installs:** 0  
**Upvotes:** 0  
**Directory Page:** https://allmcps.com/mcp/phantom-mcp-server-2

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

## Tools
Capabilities this server exposes over MCP:

- **quote_payment** — ```json
- **authorize_payment** — ```json
- **submit_payment** — ```json
- **verify_payment** — ```json

## Claude Desktop Quick Installation
Install path detected from listing signals. Uses `npx` (confidence: high):

```json
"mcpServers": {
  "phantom-mcp-server": {
    "command": "npx",
    "args": ["@phantomid/mcp-server"],
    "env": {
      "PHANTOM_API_KEY": "",
      "PHANTOM_API_URL": "",
      "PHANTOM_PAYER_PRIVATE_KEY": "",
      "PHANTOM_ROUTER_ADDRESS": "",
      "PHANTOM_ALLOW_CUSTOM_API_URL": ""
    }
  }
}
```

**Requires environment variables:** `PHANTOM_API_KEY`, `PHANTOM_API_URL`, `PHANTOM_PAYER_PRIVATE_KEY`, `PHANTOM_ROUTER_ADDRESS`, `PHANTOM_ALLOW_CUSTOM_API_URL` — the values above are empty placeholders; fill in real credentials before running (see the repository for what each one is for).

## Documentation

## 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:

```sh
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

The documented transport is stdio; the README does not describe an HTTP MCP transport. 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.

_Full upstream README: https://allmcps.com/mcp/phantom-mcp-server-2/readme_