# io.github.Arbromagency-Sato/phantom-mcp-server (npm · @phantomid/mcp-server)

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

- Trust score: 83/100 (high trust)
- Change this week: 0
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-05

## Components

- npm · `@phantomid/mcp-server`: 83/100 (this document), [markdown](https://verifymcp.io/servers/arbromagency-sato-phantom-mcp-server/phantomid-mcp-server.md), [page](https://verifymcp.io/servers/arbromagency-sato-phantom-mcp-server/phantomid-mcp-server)

## Channel facts

- Registry: `npm`
- Package: `@phantomid/mcp-server`
- Version: `0.2.1`
- Transport: `stdio`

## Trust breakdown

How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-11-05.

- **Supply Chain Security**: 99/100
  - No malware found by supply-chain analysis.
  - No known CVEs affecting this package version or its production dependencies.
  - No install/post-install scripts declared.
  - 1 of 9 dependencies flagged as unhealthy.
- **Provenance & Transparency**: 45/100
  - Source repository is publicly reachable at the declared URL.
  - Provenance check failed: no build-provenance attestation is published.
  - Clear OSI-approved license (MIT).
  - Actively maintained (last published 10 days ago).
  - Disclosure check failed: no security disclosure policy was found in the source repository.
- **Schema Quality & AI Usability**: 76/100
  - AI-judged instruction clarity (excellent).
  - Context-footprint check failed: tool/resource definitions use about 772 tokens (~154/item across 5 items; 5 tools + 0 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 100/100
  - No destabilizing schema changes in the last 30 days.
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% of tool parameters carry a description.
  - Structured output schemas are declared (100% of tools); any adoption earns full credit.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - All 1 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation.
  - An AI judge read all 5 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 60/100
  - Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28.

## Install

### How do I install the io.github.Arbromagency-Sato/phantom-mcp-server server?

io.github.Arbromagency-Sato/phantom-mcp-server runs locally as an npm package, launched with npx -y @phantomid/mcp-server. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

### Claude

```bash
claude mcp add arbromagency-sato-phantom-mcp-server -- npx -y @phantomid/mcp-server
```

### Cursor

```json
{
  "mcpServers": {
    "arbromagency-sato-phantom-mcp-server": {
      "command": "npx",
      "args": [
        "-y",
        "@phantomid/mcp-server"
      ]
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "arbromagency-sato-phantom-mcp-server": {
      "command": "npx",
      "args": [
        "-y",
        "@phantomid/mcp-server"
      ]
    }
  }
}
```

### Codex

```bash
codex mcp add arbromagency-sato-phantom-mcp-server -- npx -y @phantomid/mcp-server
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "arbromagency-sato-phantom-mcp-server": {
      "type": "local",
      "command": [
        "npx",
        "-y",
        "@phantomid/mcp-server"
      ],
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add arbromagency-sato-phantom-mcp-server --command npx --arg -y --arg @phantomid/mcp-server
```

### Hermes

```yaml
mcp_servers:
  arbromagency-sato-phantom-mcp-server:
    command: "npx"
    args: ["-y", "@phantomid/mcp-server"]
```

### Netclaw

```json
{
  "McpServers": {
    "arbromagency-sato-phantom-mcp-server": {
      "Transport": "stdio",
      "Command": "npx",
      "Arguments": [
        "-y",
        "@phantomid/mcp-server"
      ]
    }
  }
}
```

### Vellum

```bash
assistant mcp add arbromagency-sato-phantom-mcp-server -t stdio -c npx -a -y @phantomid/mcp-server
```

### Other

```json
{
  "mcpServers": {
    "arbromagency-sato-phantom-mcp-server": {
      "command": "npx",
      "args": [
        "-y",
        "@phantomid/mcp-server"
      ]
    }
  }
}
```

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-11-05 (score 83, +8)

- [security improvement] Known CVEs: unverified → pass

### 2026-11-04 (score 75, −8)

- [security regression] Known CVEs: pass → unverified

### 2026-10-31 (score 83, 0)

- [functional regression] Security disclosure: unverified → fail

### 2026-10-30 (score 83, 0)

- [functional regression] Security disclosure: fail → unverified

### 2026-10-28 (score 83, +1)

- [security] Stability: 0.97 → pass

### 2026-10-26 (score 82, +1)

No change was recorded against any check on this day. Stability & Change Management went from 90 to 93. That category is still filling its 30-day observation window: 27 days of observed history at the previous scan, 28 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-10-24 (score 81, +1)

No change was recorded against any check on this day. Stability & Change Management went from 83 to 87. That category is still filling its 30-day observation window: 25 days of observed history at the previous scan, 26 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-10-22 (score 80, 0)

- [functional regression] Security disclosure: unverified → fail

## MCP tools (5)

### `quote_payment` (~292 tokens)

Quote a 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.

Input parameters:

- `amount` (string, required): Token amount in smallest units (6 decimals for USDC), e.g. '2500000' = $2.50.
- `asset_contract` (string, required): ERC-20 token contract to pay with, e.g. USDC on Base: 0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913.
- `chain_id` (number, required): EVM chain ID: 8453 = Base mainnet.
- `idempotency_key` (string, required): Unique client-generated key; safe retries return the same quote instead of duplicating it.
- `metadata` (object): Optional free-form key/value object attached to the quote (surfaced in receipts).
- `payer_agent_id` (string): Optional A2A agent card ID of the payer, for discovery and audit.
- `payer_wallet` (string, required): EVM address of the payer wallet (0x..., checksummed).
- `recipient_agent_id` (string): Optional A2A agent card ID of the recipient.
- `recipient_wallet` (string, required): EVM address of the recipient wallet (0x...).

Output parameters:

- `content` (array)
- `isError` (boolean): True when the API call failed; text carries { error: { code, message } }.

### `authorize_payment` (~107 tokens)

Authorize a 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.

Input parameters:

- `payer_signature` (string, required): EIP-712 signature (0x, 65 bytes) of the PaymentAuthorization typed data, signed by payer_wallet.
- `payment_intent_id` (string, required): Payment intent ID returned by quote_payment.

Output parameters:

- `content` (array)
- `isError` (boolean): True when the API call failed; text carries { error: { code, message } }.

### `submit_payment` (~74 tokens)

Submit a 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.

Input parameters:

- `payment_intent_id` (string, required): Authorized payment intent ID to broadcast and settle.

Output parameters:

- `content` (array)
- `isError` (boolean): True when the API call failed; text carries { error: { code, message } }.

### `verify_payment` (~103 tokens)

Verify a payment receipt

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 receipts.

Input parameters:

- `payment_intent_id` (string, required): Payment intent ID to verify.
- `receipt_id` (string): Optional specific receipt ID when several receipts exist for the intent.

Output parameters:

- `content` (array)
- `isError` (boolean): True when the API call failed; text carries { error: { code, message } }.

### `pay_url` (~196 tokens)

Pay an x402-gated URL

Pay any URL that demands HTTP 402 payment (x402 protocol, USDC on Base): the IDPHANTOM API detects the challenge (v1/v2), validates it against your account policy (allowed domains, per-payment cap, daily cap), signs the EIP-3009 authorization server-side and retries with the payment header. The agent never handles x402 itself. Retries with the same idempotency_key return the stored receipt instead of paying again. The payment is funded by the IDPHANTOM x402 payer wallet under per-domain caps and a global daily cap; per-account ledger billing is planned as a follow-up.

Input parameters:

- `idempotency_key` (string, required): Unique client-generated key; safe retries return the stored receipt instead of paying again.
- `url` (string, required): The URL to fetch and pay if it responds 402, e.g. https://pay.idphantom.com/v1/demo/premium.

Output parameters:

- `content` (array)
- `isError` (boolean): True when the API call failed; text carries { error: { code, message } }.

## Diagnostics

Captured diagnostic sections: Provenance, Dependencies. The full working is on the page: https://verifymcp.io/servers/arbromagency-sato-phantom-mcp-server/phantomid-mcp-server#diagnostics

## Score history

- 2026-11-05: 83
- 2026-11-04: 75
- 2026-11-03: 83
- 2026-11-02: 83
- 2026-11-01: 83
- 2026-10-31: 83
- 2026-10-30: 83
- 2026-10-29: 83
- 2026-10-28: 83
- 2026-10-27: 82
- 2026-10-26: 82
- 2026-10-25: 81
- 2026-10-24: 81
- 2026-10-23: 80
- 2026-10-22: 80
- 2026-10-21: 80
- 2026-10-20: 79
- 2026-10-19: 79
- 2026-10-18: 78
- 2026-10-17: 78
- 2026-10-16: 77
- 2026-10-15: 77
- 2026-10-14: 76
- 2026-10-13: 39
- 2026-10-12: 39
- 2026-10-11: 39
- 2026-10-04: 72
- 2026-10-03: 72
- 2026-10-02: 71
- 2026-10-01: 25

## Common questions

### What is the io.github.Arbromagency-Sato/phantom-mcp-server server?

io.github.Arbromagency-Sato/phantom-mcp-server is listed in the public MCP registry as io.github.Arbromagency-Sato/phantom-mcp-server. PHANTOM ID MCP payment server: agent-to-agent USDC payments on Base. This page covers its npm package (@phantomid/mcp-server).

### Is the io.github.Arbromagency-Sato/phantom-mcp-server server safe to use?

io.github.Arbromagency-Sato/phantom-mcp-server scores 83 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 5 November 2026. It declares no install or post-install scripts. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

### What tools does the io.github.Arbromagency-Sato/phantom-mcp-server server expose?

io.github.Arbromagency-Sato/phantom-mcp-server exposes 5 tools: quote_payment, authorize_payment, submit_payment, verify_payment, pay_url. Their descriptions and schemas cost roughly 772 tokens of context every time the server is loaded.

### Is the io.github.Arbromagency-Sato/phantom-mcp-server server still maintained?

io.github.Arbromagency-Sato/phantom-mcp-server is still listed as active in the MCP registry. We last reached this channel on 5 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

### What licence is the io.github.Arbromagency-Sato/phantom-mcp-server server under?

io.github.Arbromagency-Sato/phantom-mcp-server declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.

## Links

- npm package: https://www.npmjs.com/package/@phantomid/mcp-server
- Socket report: https://socket.dev/npm/package/@phantomid/mcp-server
- Repository: https://github.com/Arbromagency-Sato/idphantom-mcp-server
- Changelog RSS feed: https://verifymcp.io/servers/arbromagency-sato-phantom-mcp-server/phantomid-mcp-server.xml
- Changelog JSON feed: https://verifymcp.io/servers/arbromagency-sato-phantom-mcp-server/phantomid-mcp-server.json
- HTML version of this page: https://verifymcp.io/servers/arbromagency-sato-phantom-mcp-server/phantomid-mcp-server