io.github.Arbromagency-Sato/phantom-mcp-server
NPM · @PHANTOMID/MCP-SERVER
PHANTOM ID MCP payment server: agent-to-agent USDC payments on Base.
Available components
Last scanned (20 hours ago)
Scores higher than 50% of npm servers
Category Crypto and Web3
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. How we score → Why this is hard to score →
Supply Chain Security74
- No malware found by supply-chain analysis.Pass
- Known CVEs could not be checked: we could not reach the advisory database to check. This is a gap on our side.Unverified
- No install/post-install scripts declared.Pass
- 1 of 9 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency45
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Provenance check failed: no build-provenance attestation is published. See how to fix → View diagnostics → Fail
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 9 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability76
- AI-judged instruction clarity (excellent).Pass
- 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. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management100
- No destabilizing schema changes in the last 30 days.Pass
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
- Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- All 1 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation.Pass
- An AI judge read all 5 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities60
- Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28. See how to fix → Fail
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 4 Nov 26 −8
- Known CVEs: pass → unverified ▼ security
- 31 Oct 26 0
- Security disclosure: unverified → fail ▼ functional
- 30 Oct 26 0
- Security disclosure: fail → unverified ▼ functional
- 28 Oct 26 +1
- Stability: 0.97 → pass security
- 26 Oct 26 +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.
- 24 Oct 26 +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.
- 22 Oct 26 0
- Security disclosure: unverified → fail ▼ functional
- 21 Oct 26 +1
- Security disclosure: fail → unverified ▼ functional
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 4 Nov 2026 · Analysed npm/@phantomid/mcp-server@0.2.1
Provenance No attestation
The registry publishes no build provenance for this version, so there is nothing to verify.
| Result | No attestation |
|---|---|
| Ecosystem | npm |
Background: How many MCP packages publish verified provenance →
Dependencies 9 packages
| Packages resolved | 9 |
|---|---|
| Stale | 1 |
| Tree resolution | Complete |
Background: SBOMs and build attestations, explained →
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
authorize_payment Authorize a payment ~107
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.
| Name | Type | Req | Description |
|---|---|---|---|
| payer_signature | string | yes | EIP-712 signature (0x, 65 bytes) of the PaymentAuthorization typed data, signed by payer_wallet. |
| payment_intent_id | string | yes | Payment intent ID returned by quote_payment. |
| Name | Type | Req | Description |
|---|---|---|---|
| content | array | yes | – |
| isError | boolean | – | True when the API call failed; text carries { error: { code, message } }. |
No examples provided.
pay_url Pay an x402-gated URL ~196
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.
| Name | Type | Req | Description |
|---|---|---|---|
| idempotency_key | string | yes | Unique client-generated key; safe retries return the stored receipt instead of paying again. |
| url | string | yes | The URL to fetch and pay if it responds 402, e.g. https://pay.idphantom.com/v1/demo/premium. |
| Name | Type | Req | Description |
|---|---|---|---|
| content | array | yes | – |
| isError | boolean | – | True when the API call failed; text carries { error: { code, message } }. |
No examples provided.
quote_payment Quote a payment ~292
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.
| Name | Type | Req | Description |
|---|---|---|---|
| amount | string | yes | Token amount in smallest units (6 decimals for USDC), e.g. '2500000' = $2.50. |
| asset_contract | string | yes | ERC-20 token contract to pay with, e.g. USDC on Base: 0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913. |
| chain_id | number | yes | EVM chain ID: 8453 = Base mainnet. |
| idempotency_key | string | yes | 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 | yes | EVM address of the payer wallet (0x..., checksummed). |
| recipient_agent_id | string | – | Optional A2A agent card ID of the recipient. |
| recipient_wallet | string | yes | EVM address of the recipient wallet (0x...). |
| Name | Type | Req | Description |
|---|---|---|---|
| content | array | yes | – |
| isError | boolean | – | True when the API call failed; text carries { error: { code, message } }. |
No examples provided.
submit_payment Submit a payment ~74
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.
| Name | Type | Req | Description |
|---|---|---|---|
| payment_intent_id | string | yes | Authorized payment intent ID to broadcast and settle. |
| Name | Type | Req | Description |
|---|---|---|---|
| content | array | yes | – |
| isError | boolean | – | True when the API call failed; text carries { error: { code, message } }. |
No examples provided.
verify_payment Verify a payment receipt ~103
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.
| Name | Type | Req | Description |
|---|---|---|---|
| payment_intent_id | string | yes | Payment intent ID to verify. |
| receipt_id | string | – | Optional specific receipt ID when several receipts exist for the intent. |
| Name | Type | Req | Description |
|---|---|---|---|
| content | array | yes | – |
| isError | boolean | – | True when the API call failed; text carries { error: { code, message } }. |
No examples provided.
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.
npm · @phantomid/mcp-server
claude mcp add arbromagency-sato-phantom-mcp-server -- npx -y @phantomid/mcp-server
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 75 out of 100 on VerifyMCP. 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 4 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.