{"passport":{"unfragile":{"@version":"1.0","version":"2026-05","artifact":{"id":"npm_npm-phantommcp-server","slug":"npm-phantommcp-server","name":"@phantom/mcp-server","type":"mcp","url":"https://www.npmjs.com/package/@phantom/mcp-server","page_url":"https://unfragile.ai/npm-phantommcp-server","categories":["mcp-servers"],"tags":[],"pricing":{"model":"open_source","free":true,"starting_price":null},"status":"active","verified":false},"capabilities":[{"id":"npm_npm-phantommcp-server__cap_0","uri":"capability://tool.use.integration.solana.wallet.transaction.signing.via.mcp.protocol","name":"solana wallet transaction signing via mcp protocol","description":"Enables Claude and other MCP clients to request transaction signatures from Phantom Wallet through a standardized Model Context Protocol server interface. The server acts as a bridge between LLM agents and the Phantom wallet extension, handling serialization of transaction objects, routing signature requests to the wallet's browser extension via postMessage API, and returning signed transactions back to the client with cryptographic proof of authorization.","intents":["Build an AI agent that can autonomously sign and submit Solana transactions on behalf of a user","Create a Claude plugin that integrates wallet functionality without exposing private keys to the LLM","Enable multi-step DeFi workflows where an agent needs to sign multiple transactions in sequence"],"best_for":["AI agent developers building Solana-native applications","Teams integrating wallet functionality into Claude-powered workflows","Developers prototyping autonomous trading or portfolio management agents"],"limitations":["Requires Phantom Wallet browser extension to be installed and unlocked on the host machine","Only supports Solana blockchain — no cross-chain transaction signing","No built-in transaction simulation or dry-run capability — all requests go directly to wallet for user approval","Depends on postMessage API availability — cannot work in pure Node.js environments without browser context"],"requires":["Phantom Wallet extension v0.9.0 or higher installed in browser","Node.js 16+ for running the MCP server","MCP client implementation (e.g., Claude Desktop with MCP support)","Active Solana wallet connection in Phantom"],"input_types":["transaction objects (Solana Transaction or VersionedTransaction format)","instruction arrays (Solana Instructions)","wallet address strings"],"output_types":["signed transaction bytes (base64 or hex encoded)","signature strings (base58 format)","transaction confirmation receipts"],"categories":["tool-use-integration","blockchain-wallet-integration"],"confidence":0.5,"matches":0,"success_rate":0},{"id":"npm_npm-phantommcp-server__cap_1","uri":"capability://tool.use.integration.mcp.compliant.wallet.connection.state.management","name":"mcp-compliant wallet connection state management","description":"Manages the lifecycle of connections between the MCP server and Phantom Wallet, handling wallet discovery, connection establishment, account enumeration, and network switching. The server maintains state about which wallet is connected, which accounts are available, and the current Solana network (mainnet, devnet, testnet), exposing this state as queryable MCP resources that clients can poll or subscribe to for real-time updates.","intents":["Check which Solana wallet is currently connected before attempting transactions","List all available accounts in the connected wallet to let users select which to use","Detect network changes (mainnet to devnet) and adapt transaction routing accordingly","Verify wallet connection status before executing multi-step workflows"],"best_for":["Multi-account Solana applications requiring account selection UI","Agents that need to adapt behavior based on network context (mainnet vs testnet)","Workflows that must verify wallet availability before committing to transaction sequences"],"limitations":["State is ephemeral — no persistence across server restarts without external storage","Network switching detection relies on Phantom's event emissions — may have slight latency","Cannot force wallet connection — only detects and reports existing connections","No built-in account filtering or permission scoping — exposes all accounts equally"],"requires":["Phantom Wallet extension installed and initialized","MCP client with resource subscription support","Active browser context for postMessage communication"],"input_types":["connection requests (implicit via MCP resource queries)","network preference parameters (optional)"],"output_types":["wallet address (base58 string)","account list (array of public keys)","network identifier (mainnet-beta, devnet, testnet)","connection status boolean"],"categories":["tool-use-integration","memory-knowledge"],"confidence":0.5,"matches":0,"success_rate":0},{"id":"npm_npm-phantommcp-server__cap_2","uri":"capability://tool.use.integration.solana.instruction.composition.and.transaction.building.via.mcp.tools","name":"solana instruction composition and transaction building via mcp tools","description":"Exposes MCP tool definitions that allow clients to construct Solana instructions and transactions without direct blockchain interaction. The server provides schema-based tool definitions for common Solana operations (token transfers, program invocations, system instructions), validates instruction parameters against Solana's IDL specifications, and returns properly formatted instruction objects that can be batched into transactions for signing.","intents":["Build complex multi-instruction transactions (e.g., swap + stake + transfer) through Claude's natural language","Validate transaction structure before sending to wallet for signing","Compose SPL token operations without requiring the agent to understand Solana's binary instruction format"],"best_for":["Non-expert developers building Solana agents with Claude","Workflows requiring complex multi-instruction transactions","Teams wanting to abstract Solana's low-level instruction encoding from LLM agents"],"limitations":["Limited to pre-defined instruction types — custom program instructions require manual schema definition","No built-in instruction optimization or reordering — agents must understand dependency ordering","Validation is schema-based only — does not simulate execution or check account state","No automatic fee estimation — agents must specify or use default fee parameters"],"requires":["Solana Web3.js library or equivalent for instruction serialization","MCP client with tool-calling support","Knowledge of Solana instruction parameters (even if abstracted by schema)"],"input_types":["instruction type identifiers (string)","instruction parameters (structured objects matching Solana IDL)","account lists (public key arrays)"],"output_types":["serialized instruction objects (JSON representation of TransactionInstruction)","transaction objects (ready for signing)","validation error messages"],"categories":["tool-use-integration","code-generation-editing"],"confidence":0.5,"matches":0,"success_rate":0},{"id":"npm_npm-phantommcp-server__cap_3","uri":"capability://tool.use.integration.phantom.wallet.event.subscription.and.notification.relay","name":"phantom wallet event subscription and notification relay","description":"Subscribes to Phantom Wallet's event stream (account changes, network switches, wallet disconnections) and relays these events to MCP clients through the MCP protocol's notification mechanism. The server maintains event listeners on the Phantom extension's postMessage API, buffers events, and pushes them to connected clients, enabling real-time awareness of wallet state changes without polling.","intents":["Receive real-time notifications when user switches accounts or networks in Phantom","Trigger agent re-evaluation when wallet state changes mid-workflow","Update UI or agent context immediately when wallet disconnects"],"best_for":["Long-running agent workflows that must adapt to wallet state changes","Real-time dashboards or monitoring applications","Multi-user applications where wallet state is shared context"],"limitations":["Event delivery is best-effort — no guaranteed ordering or deduplication if server restarts","Phantom's event API is extension-specific — not standardized across wallet providers","No event filtering or sampling — all events are relayed, potentially overwhelming clients","Event latency depends on postMessage API performance — typically 10-50ms"],"requires":["Phantom Wallet extension with event emission support","MCP client with notification subscription capability","Active postMessage listener in browser context"],"input_types":["event subscriptions (implicit via MCP notification registration)"],"output_types":["wallet event objects (account changed, network changed, disconnected)","event metadata (timestamp, previous state, new state)"],"categories":["tool-use-integration","automation-workflow"],"confidence":0.5,"matches":0,"success_rate":0},{"id":"npm_npm-phantommcp-server__cap_4","uri":"capability://tool.use.integration.multi.signature.transaction.coordination","name":"multi-signature transaction coordination","description":"Coordinates signing of transactions that require multiple signers by managing signature collection, tracking which signers have approved, and assembling the final signed transaction once all required signatures are gathered. The server maintains a transaction signing session, routes signature requests to appropriate signers (via Phantom or other wallet providers), and combines signatures into a valid Solana transaction that can be submitted to the blockchain.","intents":["Execute multi-sig treasury transactions where multiple team members must approve","Coordinate complex DeFi operations requiring signatures from multiple accounts","Implement approval workflows where different agents or users must sign sequentially"],"best_for":["Teams managing shared Solana treasuries or DAOs","Multi-party DeFi protocols requiring coordinated signing","Workflows with approval chains or governance requirements"],"limitations":["Requires all signers to have Phantom Wallet or compatible wallet installed","No built-in timeout or expiration for pending signatures — sessions must be manually managed","Signature ordering matters for Solana transactions — server must enforce correct signer sequence","No persistence of signing sessions — in-memory only, lost on server restart"],"requires":["Multiple Phantom Wallet instances or multi-sig wallet support","Transaction object with all signers specified","MCP client capable of routing requests to multiple wallet instances"],"input_types":["transaction object","signer list (public keys)","signing order specification"],"output_types":["partially signed transaction (after each signer)","fully signed transaction (ready for submission)","signature collection status"],"categories":["tool-use-integration","automation-workflow"],"confidence":0.5,"matches":0,"success_rate":0}],"trust":{"score":24,"verified":false,"data_access_risk":"moderate","permissions":["Phantom Wallet extension v0.9.0 or higher installed in browser","Node.js 16+ for running the MCP server","MCP client implementation (e.g., Claude Desktop with MCP support)","Active Solana wallet connection in Phantom","Phantom Wallet extension installed and initialized","MCP client with resource subscription support","Active browser context for postMessage communication","Solana Web3.js library or equivalent for instruction serialization","MCP client with tool-calling support","Knowledge of Solana instruction parameters (even if abstracted by schema)"],"failure_modes":["Requires Phantom Wallet browser extension to be installed and unlocked on the host machine","Only supports Solana blockchain — no cross-chain transaction signing","No built-in transaction simulation or dry-run capability — all requests go directly to wallet for user approval","Depends on postMessage API availability — cannot work in pure Node.js environments without browser context","State is ephemeral — no persistence across server restarts without external storage","Network switching detection relies on Phantom's event emissions — may have slight latency","Cannot force wallet connection — only detects and reports existing connections","No built-in account filtering or permission scoping — exposes all accounts equally","Limited to pre-defined instruction types — custom program instructions require manual schema definition","No built-in instruction optimization or reordering — agents must understand dependency ordering","builder identity is not verified yet","no observed match outcomes yet"],"rank_breakdown":{"adoption":0.05,"quality":0.2,"ecosystem":0.3,"match_graph":0.25,"freshness":0.6,"weights":{"adoption":0.25,"quality":0.25,"ecosystem":0.15,"match_graph":0.23,"freshness":0.12}},"observed_outcomes":{"matches":0,"success_rate":0,"avg_confidence":0,"top_intents":[],"last_matched_at":null},"maintenance":{"status":"active","updated_at":"2026-05-24T12:16:23.904Z","last_scraped_at":"2026-05-03T14:23:35.272Z","last_commit":null},"community":{"stars":null,"forks":null,"weekly_downloads":null,"model_downloads":null,"model_likes":null}},"distribution":{"claim_url":"https://unfragile.ai/submit?claim=npm-phantommcp-server","compare_url":"https://unfragile.ai/compare?artifact=npm-phantommcp-server"}},"signature":"bq3pNi/GPsh/gkfsw4TTKIFqOW/sWTFP/X2GLZt0on0RtM7jfseJd3v8p1vvGQeAn64o6ZsGAlU0ZT5Kt8FnBg==","signedAt":"2026-06-20T18:39:06.873Z","signedBy":"unfragile.ai","version":1},"_links":{"self":"https://unfragile.ai/api/v1/passport/npm-phantommcp-server","artifact":"https://unfragile.ai/npm-phantommcp-server","verify":"https://unfragile.ai/api/v1/verify?slug=npm-phantommcp-server","publicKey":"https://unfragile.ai/api/v1/trust-passport-public-key","spec":"https://unfragile.ai/trust","schema":"https://unfragile.ai/schema.json","docs":"https://unfragile.ai/docs"}}