/vendor/phantom/AgentRouting.json or
/vendor/phantom/AgentContext.json directly.
phantom.app
Overview
Does phantom.app support MCP?
Yes. phantom.app has a confirmed MCP implementation. Two distinct official MCP servers: (1) a developer-documentation MCP server that connects AI coding assistants (Cursor, Claude, VS Code) to Phantom Connect SDK reference docs for code generation; (2) a wallet-operations MCP server (@phantom/mcp-server on npm) that allows AI agents to sign/send transactions, transfer tokens, swap/buy tokens, retrieve wallet addresses, and simulate transactions across Solana, Ethereum, Bitcoin, Base, and Sui—using the user's own non-custodial Phantom wallet..
What agentic protocols does phantom.app support?
As of 2026-06-29, phantom.app has confirmed support for MCP and proprietary.
Is phantom.app's API publicly accessible or partner-gated?
Open.
Does phantom.app explicitly prohibit automated access?
Yes. phantom.app's terms of service explicitly prohibit automated or scraper access to the public website without prior written permission.
Is phantom.app agent-ready?
Not currently. No confirmed agent-callable interface was found for phantom.app as of 2026-06-29.
Protocols
Phantom.app (a Solana-based crypto wallet) does not appear among any named A2A launch partners or adopters. The 50+ confirmed partners include Atlassian, Box, Cohere, MongoDB, PayPal, Salesforce, SAP, ServiceNow, and Workday — all enterprise software vendors with no overlap with Phantom's consumer crypto-wallet domain. No vendor-specific evidence connecting phantom.app to A2A was found.
No evidence that phantom.app (a crypto wallet application) appears among any known ACP launch partners or integrators. Named launch partners confirmed from search results include URBN brands (Anthropologie, Free People, Urban Outfitters), Coach, Kate Spade, Revolve, Ashley Furniture, Etsy, and Shopify merchants — all consumer retail commerce vendors, not crypto wallets. Phantom.app operates in the blockchain/crypto wallet space, which is structurally outside the retail commerce focus of ACP. No vendor-specific ACP documentation or integration evidence was found for phantom.app.
No evidence that phantom.app (the Solana-ecosystem crypto wallet) appears in any AP2 launch partner list or any AP2-related announcement. Named AP2 launch partners in the crypto/wallet space include Coinbase, MetaMask, ConsenSys, and Mysten Labs; Phantom is absent from all partner rosters found. This is not_found rather than confirmed_absent because no Phantom-specific statement or deprecation notice was located — they simply do not appear in any discovered AP2 context.
Two distinct official MCP servers: (1) a developer-documentation MCP server that connects AI coding assistants (Cursor, Claude, VS Code) to Phantom Connect SDK reference docs for code generation; (2) a wallet-operations MCP server (@phantom/mcp-server on npm) that allows AI agents to sign/send transactions, transfer tokens, swap/buy tokens, retrieve wallet addresses, and simulate transactions across Solana, Ethereum, Bitcoin, Base, and Sui—using the user's own non-custodial Phantom wallet.
Phantom officially publishes two MCP servers. The developer-docs server is documented at https://docs.phantom.com/resources/mcp-server. The wallet-ops server is published as the npm package @phantom/mcp-server and listed at https://cursor.directory/plugins/phantom-mcp-server; it uses an OAuth2 PKCE flow introduced in the v2.x SDK line. Both are built and maintained by the Phantom team.
No evidence that phantom.app has implemented or announced MPP support. Phantom's developer docs (docs.phantom.com) reference an MCP server for agent wallet interactions but make no mention of MPP. Known MPP launch partners and integrators include Cloudflare, eco.com, and mpp.dev-listed services — Phantom does not appear among them. Choosing not_found rather than confirmed_absent because no Phantom-specific statement or deprecation notice addresses MPP.
No usable finding available for this protocol (no legitimate scan available within the candidate window).
Phantom (phantom.app) is a multi-chain crypto wallet product with no identified connection to the Universal Commerce Protocol (UCP), which is a Google/Shopify-led open standard for agentic commerce checkout flows. Searches across Phantom's developer documentation (docs.phantom.com) and public web presence found no mention of UCP implementation, partnership, or planned support. Phantom's developer surface focuses on blockchain wallet connectivity (Phantom Connect SDK, deeplinks, embedded wallets) with no overlap with the retail commerce checkout discovery mechanism UCP describes. No vendor-specific statement of absence was found; this is a not_found result based on examined material returning no UCP-relevant evidence.
No evidence that phantom.app has implemented or announced WebMCP (the browser-layer window.AICommands protocol co-developed by Google and Microsoft). Phantom's publicly documented agent integration is a traditional MCP server (@phantom/mcp-server) for signing transactions and swaps — a different protocol. WebMCP's known participants are browser/platform vendors; no crypto wallet or phantom.app appears in any launch partner context.
No evidence found linking phantom.app (the Phantom crypto wallet) to the x402 protocol as a launch partner, integration target, or adopter. Named x402 ecosystem participants surfaced include Coinbase, Cloudflare, Stellar, eco.com, and allium.so — Phantom does not appear among them. Phantom's developer documentation and wallet SDK focus on standard wallet-connect and dApp signing flows, with no x402 reference found.
No usable finding available for this protocol (no legitimate scan available within the candidate window).
Browser-injected provider API (window.phantom.solana / window.phantom.ethereum / window.phantom.bitcoin) for dApp integration: connect, sign, and send transactions across Solana, Ethereum, Base, Polygon, and Bitcoin chains via the browser extension or in-app browser. Distinct from the Deeplinks interface (used for mobile app-to-app integration on iOS/Android), the Embedded Wallet SDK (seedless, non-custodial in-app wallets via @phantom/browser-sdk and @phantom/embedded-provider-core for web and React Native), and the Server SDK (backend provisioning with org credentials). Each represents a genuinely distinct integration surface.
Phantom documents four distinct proprietary integration surfaces at https://docs.phantom.com: (1) injected browser provider (window.phantom.*) following EIP-1193 for EVM but with Phantom-specific extensions for Solana and Bitcoin; (2) Deeplinks API for mobile app-to-app communication on iOS/Android; (3) Embedded Wallet SDK (Browser/React Native) for seedless in-app wallets; (4) Server SDK for backend applications requiring org provisioning. All surfaces are publicly documented and openly accessible without gating beyond standard Phantom Portal signup for embedded/server tiers. No named standard (e.g., WalletConnect) underpins the Solana or Bitcoin provider surfaces.
No evidence was found of phantom.app publishing any self-declaration files (llms.txt, agents.md, /.well-known/agent, or similar) at predictable domain paths. Direct HTTP fetch was blocked by sandbox network restrictions, preventing a live path check. Web searches surfaced Phantom's MCP server and developer docs (docs.phantom.com) but no indexed references to any self-declaration discovery file at phantom.app or docs.phantom.com. The not_found status reflects inability to load the paths directly combined with no cached/indexed evidence; unable_to_verify would be appropriate if the domain itself were inaccessible, but search results confirm the domain is publicly reachable — just without these files appearing.
Summary
Has agent interface: false
Monitor phantom.app for any future developer API or MCP server announcements; no agent-callable interface was found in this pass. If agent integration becomes a priority, check phantom.app/developers or any official developer documentation pages directly, as no public API surface was identified.
AgentContext
Verified discrepancies
Vendor claim: Phantom presents itself as a full-featured multi-chain crypto wallet with swap, send, and buy capabilities available to users, without surfacing geographic or account-status restrictions during onboarding or before a user initiates a transaction.
What actually happens: Phantom silently restricts wallet functionality—including the ability to send or swap crypto—based on regional/country restrictions or detected Terms of Service violations. Users only discover the 'Feature is unavailable' or 'Transactions Disabled' state mid-session after attempting a transaction, not at wallet setup or login. Additionally, certain tokens (e.g., those with freeze authority or no real liquidity) cannot be swapped, and this is not disclosed to the user until the swap attempt fails.
Agent guidance: Before initiating any send or swap transaction via Phantom, an agent should: (1) check whether the user's region is subject to Phantom's geographic restrictions by reviewing Phantom's terms and current country list; (2) attempt a dry-run or pre-flight check for token swappability (e.g., check for freeze authority on Solana tokens) before committing to the transaction; (3) surface a warning to the user that Phantom may silently disable transactions mid-session without prior notice if a restriction applies, so the user can choose an alternative wallet or route.
- Phantom's own help article confirms that wallets can be restricted from sending or swapping due to regional restrictions or ToS violations, and that users encounter these limits only when they see a mid-session error message.
- Phantom's swap failure help article states that tokens with freeze authority enabled, no real liquidity, or smart contract sell restrictions will silently fail to swap—this constraint is not surfaced before the swap is attempted.
Human handoff required for
Escalate to a human when a send or swap transaction is blocked mid-session by Phantom's 'Feature is unavailable' or 'Transactions Disabled' message, because the restriction (geographic ban or ToS violation) was not disclosed at onboarding or login and the agent cannot determine programmatically whether the block is temporary, permanent, or reversible without human review of the user's account status and region.
Escalate to a human when a token swap attempt fails because the token has freeze authority, no real liquidity, or smart-contract-level restrictions, since Phantom does not disclose these token-level constraints before the swap is initiated and the agent cannot reliably pre-screen all affected token categories without human judgment on an alternative route or wallet.
Five discrepancy categories were checked for Phantom (phantom.app): (1) Pricing — no hidden fees or deceptive pricing found; Phantom discloses network and platform fees before confirmation. (2) Availability — no evidence of ghost listings or bait-and-switch rates; regional restriction notices are disclosed at point of failure. (3) Identity — no merchant-of-record ambiguity found; Phantom's non-custodial model is consistently represented. (4) Policy — no gap between stated and enforced policies found; on-chain irreversibility and wallet-restriction scope are consistently documented. (5) Undisclosed constraints — a confirmed finding exists: Phantom silently restricts send/swap functionality based on geography or ToS status, and blocks token swaps for freeze-authority or low-liquidity tokens, with both constraints only surfacing mid-transaction rather than at onboarding or initiation. Categories 1–4 were checked via open-web searches and returned no qualifying findings; category 5 is grounded in Phantom's own published support documentation.