Solana Nft MCP

solana-nft-mcp

The NFT APIs I tried return an empty ownership history for a Metaplex Core asset, and an AI reading that empty answer tells you the card has never traded. solana-nft-mcp reads the chain itself: who owned it, who can freeze it, what sold and for how much, and where the deals are. Read-only, no sign-up, nothing collected, runs on your machine.

Why

Ask an assistant about a Solana card today and it answers from memory. It will say a card "never traded", because the mainstream NFT APIs return an empty history for Metaplex Core assets while the transfers sit on chain the whole time. It will compare two floors quoted in two currencies as if they were one.

solana-nft-mcp hands the same assistant live, labelled data instead: the chain for supply, ownership, provenance and custody rules, Magic Eden without a key, and OpenSea through a free key the server issues itself. Each number comes back with its marketplace, its currency, its read time, and what the source could not see.

The server runs on your machine and your AI app starts it. There is no hosted service and no account between you and the data. The picture is generated from the running server, so the counts cannot drift from the code: npm test fails if they do.

Install

Node 22 or newer. Two ways to run it.

From npm, no clone. Wherever a client asks for a command, give it npx with the arguments -y solana-nft-mcp. The first start downloads the package; later starts reuse it.

claude mcp add solana-nft -- npx -y solana-nft-mcp

From source. Build once, then point the client at dist/index.js:

git clone https://github.com/p1xelapp/solana-nft-mcp.git

cd solana-nft-mcp && npm install && npm run build

Claude Code

claude mcp add solana-nft -- node /absolute/path/to/solana-nft-mcp/dist/index.js

Claude Desktop. Settings -> Developer -> Edit Config, add the block below, then quit the app fully and reopen it. Or install the .mcpb bundle from the latest release by dragging it onto Settings -> Extensions.

{

"mcpServers": { "solana-nft": { "command": "node", "args": ["/absolute/path/to/solana-nft-mcp/dist/index.js"] } } }

Other clients. Tested: Claude Desktop, Claude Code, Codex CLI 0.153.4 (codex exec -c 'mcp_servers.solana-nft.command="node"' -c 'mcp_servers.solana-nft.args=["/absolute/path/to/dist/index.js"]'). Cursor, Windsurf, Gemini CLI, Zed, Cline and VS Code take the same command / args pair in their own config; the server is plain stdio with no client-specific code, but those have not been tested here. ChatGPT on the web and Grok cannot run a local process. The server speaks MCP protocol revision 2025-11-25 through the official TypeScript SDK v1. A client that offers the newer 2026-07-28 revision gets 2025-11-25 back, which current clients accept; one that refuses anything older cannot use this server yet.

Did it work? Your app lists the tools near the message box (Claude Code: /mcp). You should see 21, starting with identify. If none: the path must be absolute and end in dist/index.js, npm run build must have run, and the app must be fully quit and reopened.

OpenSea is on without any setup. The first question that needs it makes the server ask OpenSea for a free agent key, stored at ~/.solana-nft-mcp/opensea-key.json and renewed before it expires. The key is never logged or printed into an answer. A collection's OpenSea slug is found from its on-chain address, or by name and then proved against that address; pass openseaSlug to override. Options, set in the config's env block (clients launch the server with a clean environment):

• OPENSEA_API_KEY - your own key, overrides the self-issued one.
• SOLANA_NFT_MCP_NO_AUTO_KEYS=1 - never request a key; OpenSea is off unless you set one.
• SOLANA_RPC_URL, DAS_RPC_URL - a private endpoint, neither required. A key in the URL is registered and redacted from every answer (details in docs/FAQ.md).
• SOLANA_NFT_MCP_NO_UPDATE_CHECK=1 - skip the one startup request to npm for a newer version.

Ask it anything

Nobody types a tool name. These are asked in plain words and the assistant picks the calls.

• Who has owned this card since it was minted, with dates and the marketplaces involved?
• Is it true this card has never traded?
• Can the project still freeze, move or burn what is in my wallet?
• What is in wallet 7HHs3..., and does that wallet flip or hold?
• What is the cheapest Legendary listing in that DC collection right now?
• Any Superman or Batman DC comic #1 or #100 for sale, and are any close to floor?
• What did Shohei Ohtani cards sell for this week, and how many changed hands?
• Are the Magic Eden and OpenSea floors for this collection even comparable?
• What would it take to build a sales bot on this, and where would it fail quietly?

A collection name, a player name, a card number or a trait is enough to start. Names resolve against a bundled snapshot of the Magic Eden directory, against OpenSea's Solana index, and against the marketplace itself, and a fuzzy match is offered as a candidate with the mismatch stated, never presented as the answer. Long answers are sized to arrive whole: a client that caps a tool result gets fewer per-row details before it gets fewer rows, and the answer says what it left out.

What it reads

No account, no sign-in, no telemetry, no log of your questions, and no signing code anywhere in the repository; every tool declares readOnlyHint. What leaves the machine: the public address, symbol or name you asked about, sent to the source that can answer it; one startup request to npm for the latest version number; one request to OpenSea for a free key, the first time a question needs it. One file may be written, the key file above. Nothing else touches disk. To remove everything: uninstall or delete the clone, then delete ~/.solana-nft-mcp/.

Key files use mode 600 on macOS and Linux. Windows uses the home folder's access permissions; mode 600 does not set a Windows ACL. Keep that folder private to your account. A linked key file or key directory is not used. If saving fails, the key stays in memory and get_source_status reports that it was not saved.

Tools

21 tools. Names are frozen: agents reference them in prompts, and a rename breaks integrations without raising an error.

Three prompts: getting_started, collection_report, wallet_report. No MCP resources, on purpose: everything they would carry is reachable by a tool the assistant calls itself.

Trust and limits

Candy's trading status can change. On 2026-11-08 all 401 registered collections carried burn-only oracle checks; the oracle still refused holder burns, while transfers no longer consulted it. Use get_asset_trust on the card for the live answer. A wallet migration is a transfer, not proof of a sale. Wallet indexes can retain the old owner; get_asset checks current Core ownership against account bytes.

• Buying, selling, listing and signing are absent. No code exists for them.
• Provenance and trust decoding cover Metaplex Core only. Legacy SPL and compressed NFTs are reported as named gaps, never as empty lists. Holdings and activity cover both.
• Magic Eden and OpenSea only. Tensor has no self-serve keys; Rarible's Solana coverage is unconfirmed. Both are catalogued with the condition that would add them.
• Every money figure names its currency and the API it came from, on the summary and on every priced row, and counts keep their coverage flags beside them (truncated, stale, historyComplete). A program should refuse to act on a row whose flag says the read was partial.
• Two error surfaces. Input that fails a tool's schema is refused before the handler runs: isError: true, no structuredContent. Every failu