Skip to main content
Glama
solana-nft-mcp

solana-nft-mcp

by p1xelapp

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.

TypeScript MCP License: MIT Sign-up


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.

Related MCP server: polskidegen-hl-tracker

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. This starts the published version. To run this checkout, use the source setup below.

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

Use an absolute path to the built file in each example. On Windows, a path such as C:/projects/solana-nft-mcp/dist/index.js works in JSON. If the app cannot find Node, use the full path to the Node executable for command.

Claude Desktop. Add this entry in Settings > Developer > Edit Config and restart Desktop. You can also install the release's .mcpb from extension settings.

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

Claude Code

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

Cursor. Add to .cursor/mcp.json.

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

VS Code with Copilot. In the Copilot harness, add to the workspace root's .mcp.json.

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

Windsurf (now Devin Desktop). For Devin Local, add to .devin/mcp_config.local.json.

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

Gemini CLI. Add to ~/.gemini/settings.json.

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

Codex CLI. Add to ~/.codex/config.toml.

[mcp_servers.solana-nft]
command = "node"
args = ["/absolute/path/to/dist/index.js"]

Zed. Add to Zed's settings JSON.

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

Cline. Open MCP Servers, choose Configure, and add this entry in the MCP settings file.

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

Goose. Add under extensions in config.yaml.

extensions:
  solana-nft:
    name: solana-nft
    enabled: true
    type: stdio
    cmd: node
    args: ["/absolute/path/to/dist/index.js"]

ChatGPT developer mode. ChatGPT accepts an HTTPS MCP URL or a Secure MCP Tunnel. For this stdio package, the tunnel client runs Node on your computer. Use an existing tunnel ID, workspace access and a Platform runtime credential supplied to the tunnel client. Choose Tunnel when adding the server in ChatGPT. Tunnel guide

tunnel-client init --sample sample_mcp_stdio_local --profile solana-nft --tunnel-id YOUR_TUNNEL_ID --mcp-command "node /absolute/path/to/dist/index.js"
tunnel-client run --profile solana-nft

Claude Messages API. Its MCP connector calls tools on a publicly reachable Streamable HTTP or SSE server. Local SDK clients can call this package over stdio. The API's programmatic tool calling feature excludes connector-provided tools. Connector and programmatic calling

The stdio server negotiates 2025-11-25 and 2025-06-18. Clients configured to require 2026-07-28 need the newer protocol. For scripts, read isError before consuming structuredContent. Successful replies also contain the same data as JSON text.

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.

In the Claude Desktop extension the same options are in the extension's settings, so there is no config file to edit. What the server sends, to whom, and how it stores its key are listed in PRIVACY.md.

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

Source

Answers

Key

Solana RPC (three public endpoints, rotated)

supply, current owner from decoded Core account bytes, transfer history, wallet age

none

Asset index (DAS) on the public RPC

a second, independent opinion on ownership and wallet contents

none

Magic Eden v2

floors, listings, sales, activity, top traders, trending

none

OpenSea v2

second-marketplace floors, sales, supply, royalty, wallet transfers

self-issued

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. When saving a key, the server writes a temporary file and renames it to opensea-key.json. An interrupted save can leave that temporary file behind. To remove the stored credentials, 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.

Tool

Back

identify

what an address or name is, where it trades, which tool to call next

verify_claim

confirmed, contradicted or unverifiable, with the numbers seen and how to re-check; for a posted sale, the venue, buyer, seller and amounts read from the transaction itself

get_asset_trust

Core plugins decoded from bytes: delegates, frozen state, oracle checks that refuse transfers or burns right now, enforced vs advisory royalties, mutable metadata, editions

get_integration_recipe

endpoints, pacing, running cost, skeleton and the silent failure modes for a given build

search_collections

name lookup across the Magic Eden directory and the OpenSea Solana index, saying which layers were read

get_collection_stats

chain supply, floors per marketplace, and a reconciliation that refuses to rank SOL against USDC

get_collection_holders

census of a Core collection from the chain's asset index, each holder with a role (issuer, marketplace escrow, wallet), capped and saying so

get_floor_prices

current floor and listed count for up to 10 collections, Magic Eden only

get_recent_sales

latest completed fills with buyer, seller, price in the currency paid, mint and signature; with chainScan, the sales the feeds miss, read from the chain

get_asset

three readers for one item: the marketplace, a byte-level decode, and the chain's asset index, with owner agreement reported

get_asset_provenance

bounded ownership history of a Core asset, dated, marketplaces named, every unread hole marked in place. historyComplete says every transaction was read; mintObserved says the mint itself was decoded. They are different claims

get_wallet_holdings

holdings from two independent readers, with the gap between them named

get_wallet_profile

holdings by collection, share of wallet and of supply, listed and compressed counts, floor ceiling with assumptions, wallet age

get_wallet_activity

buys and sells, net flow, marketplace split, every flip with hold time and P&L, a behaviour label with its reason

get_collection_sales

sales over a window: count, volume, median, buyers, sellers, per-day series, per-name breakdown, how far back the feed was read

find_in_group

one edition number hunted across a whole family of collections, each match against its own floor

find_listings

cheapest-first listings, trait filters, a name filter that says what it matched, a lowest-serials mode, each ask against its trait floor on both marketplaces

get_top_traders

the largest wallets in a collection by Magic Eden volume

get_trending

Magic Eden's trending list, with an explicit note when the marketplace publishes nothing

explain_mechanics

escrow, freezing, delegates, royalties, wash trades and migrations, per standard and marketplace, each entry citing its source

get_source_status

every source pinged live: tier, fallback, what it cannot see, credential state

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 announced its new site and wallet for November 18. Its storefront terms, read November 19, place secondary sales on third-party marketplaces. On 2026-11-19 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.

  • Marketplace feeds: Magic Eden and OpenSea only. Tensor gives API access on request (its API page, read 2026-11-14), so its API is not called and its listings, bids and floor stay unread. Its sales of Metaplex Core items, and OpenSea's own Solana sales that Magic Eden's feed misses, are decoded from the chain instead: one transaction at a time by verify_claim with claim: "sale", and as a bounded scan by get_recent_sales with chainScan: true, each reported as its own venue row. Rarible's Solana coverage is unconfirmed. Tensor's API and Rarible 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.

  • For scripted calls, identify returns lookup with a tool name and arguments when the caller supplied the exact identifier. Check for null before using it. Names, summaries and candidate lists are display text.

  • Two error surfaces. Input that fails a tool's schema is refused before the handler runs: isError: true, no structuredContent. Every failure inside a handler carries structuredContent.error. For example, offline means the server did not contact the source, ambiguous means the caller must choose a match, and upstream-rate-limit means the source asked callers to wait. Scripts should handle unknown categories and show the explanation that accompanies the error.

  • No valuations and no currency conversion. Solana only.

Full detail: docs/TRUST-AND-LIMITS.md.

Security

Minting is permissionless, so a collection name is attacker-controlled text. Every name and every field from a chain or a marketplace is checked against the shape it claims to have before a model sees it, and every credential this process has sent is redacted from every answer. Covered by the offline suite. Reporting: SECURITY.md.

Development

npm test           # offline: every tool, prompt, validation, wallet and market logic,
                   # the OpenSea contract, the prompt-injection defence. No network.
npm run test:live  # live: floors, a real provenance trace, source status, name lookup
npm run snapshot   # refresh the bundled Magic Eden collection directory
npm run inspect    # open the MCP Inspector against a local build

CI runs a full-history secrets scan on every push to every branch; the offline suite, lint, the tarball check and npm audit on main, pull requests and release tags; and the live check weekly.

Docs

About

Built and maintained by P1xel (p1xel.app, @P1xelCollector), a long-time Solana collector. The story of why it exists is in docs/DEEP-DIVE.md.

Running on the same decoding

CandyScan tracks the Candy Digital collections on Solana: supply, holders, migrations and sales, kept current. It is where the Core decoding was written first, and this repository is the keyless half of that pipeline. Each project shaped the other.

Shipped something on top of solana-nft-mcp? Open an issue and it goes here.

Independent project, not affiliated with the Solana Foundation. SOLANA and SOL are trademarks of the Solana Foundation. They appear in this project's name and documentation for one reason only: to say which chain the server reads. Nothing here is endorsed, sponsored or reviewed by the Solana Foundation, and no affiliation is claimed or implied.

License

MIT. See LICENSE.

Available Tools

21 tools
explain_mechanicsHow NFTs are handled: escrow, freezing, delegates, royaltiesA
Read-only

Plain-words explanation of how a standard or a marketplace actually handles an asset: why an NFT moved to an unknown wallet (escrow), whether a project can take it back (permanent delegates), why it cannot be listed (freeze), who gets paid on a sale and where royalties are enforced, why two sites show different floors, what a wash trade looks like, what changes in a standards migration. Covers Metaplex Core plugins, Token Metadata and programmable NFTs, compressed NFTs, and the Solana marketplaces (Magic Eden order book and pools, Tensor, OpenSea, Candy Digital, Collector Crypt). Every entry cites the documentation or program source it came from and says when observed behaviour differs from what is documented. Answers 'what does frozen mean', 'can they burn my card', 'is Magic Eden custodial'.

Inputs: topic (required).

find_in_groupHunt across a family of collectionsA
Read-only

Search MANY collections at once for a specific edition number. DC comics on Candy are 272 separate collections, one per issue, so 'is any DC #1 or #100 listed, and how close to floor' cannot be asked of one collection - this asks a batch of them and hands back a cursor for the rest. Answers 'any #1 for sale across DC', 'cheapest low serial in the MLB set', 'which issues have a #100 listed under 1 SOL'. Each match names its collection, its ask, that collection's floor and how far above floor it is. Use groups from search_collections, or name the collections yourself.

Inputs: batch, group, serials, startAt, +4 more.

find_listingsFind listings and dealsA
Read-only

What is for sale in a collection right now, cheapest first, with optional trait filters, a name filter, and a lowest-serials mode that reads the whole book and sorts by edition number. Answers 'cheapest Rex', 'find #1390', 'is a #1 or #100 for sale', 'lowest serial I can buy and what it costs versus floor', 'is there a deal on a Judge card', 'what is listed under 1 SOL', 'which traits are cheap right now'. Several trait filters mean all of them. Rarity ranks appear when the marketplace publishes them (Core collections usually carry none). Prices are asks on Magic Eden, not what buyers pay; get_collection_sales shows that.

Inputs: symbol (required), limit, traits, openseaSlug, +2 more.

get_assetAsset lookupA
Read-only

Everything known about one asset by mint address: marketplace metadata (name, image, collection, traits, listing state) plus the on-chain owner read from the Core account for Metaplex Core assets, and the chain's asset index for every other standard. Each reader's freshness is reported; the two owners are only called agreeing when both were read live.

Inputs: mint (required).

get_asset_provenanceAsset provenance (Core)A
Read-only

BOUNDED on-chain ownership history of a Metaplex Core asset: mint -> transfers (with marketplace labels) -> current owner. Decoded from TransferV1 instruction accounts - data most NFT APIs return EMPTY for on Core assets. Ideal for Candy Digital cards and any Core collectible. This decodes at most depth transactions, so on a heavily traded asset the earliest ownership can be outside the result: ALWAYS read historyComplete before describing the trail as the whole story, and skippedTransactions for how much was left out. Raise depth to cover more. A bounded walk keeps the newest transactions and the mint and drops the middle, which is where a recently minted asset's sale usually sits: any hole appears in events as an unread_gap row IN ITS PLACE in the order, so never read across one as though the trail were continuous. Lowering depth to save time is how a 'who bought it' question gets the wrong answer. Ownership events only: traits live in get_asset (marketplace attributes) and get_asset_trust (the on-chain Attributes plugin), so an empty trait picture here means nothing.

Inputs: mint (required), depth.

get_asset_trustWhat owning this actually meansA
Read-only

Decode the Metaplex Core plugins on an asset and translate them into custody facts: can the issuer move or burn it without the holder's signature (permanent delegates - normal on packs, a red flag on keepers), is it frozen, does a royalty rule set limit which programs can trade it (no rule checks that the fee is paid) or is the royalty advisory, is the metadata mutable, is the serial an on-chain edition or just printed text. Plugins set on the COLLECTION apply to every asset in it and are read too, marked inherited. Marketplaces show the picture and the price; this shows the rules attached to the account. Use before a purchase, when a listing 'cannot transfer', or when someone asks whether a pack burns on open. Read-only, decoded from raw bytes, no indexer.

Inputs: mint (required).

get_collection_holdersWho holds every item in a collectionA
Read-only

CENSUS of a Core collection: every asset grouped under it, with its current owner, straight from the chain's asset index. This is the only tool that sees items NOBODY HAS LISTED - every other collection-wide tool reads a marketplace's listing book, so an unsold item is invisible to them. Answers 'who won the 36 packs from that drop', 'is one wallet holding half the supply', 'how many are still with the issuer', 'which wallets hold this set'. Filter to part of a collection with trait/value (e.g. Item Type = Pack) or namePrefix (e.g. 'Gold Series - Aces'). Returns the rows plus a holder count per address, largest first. Every holder row carries a ROLE: issuer (the collection's update authority, read from the chain: the issuer's key, which says nothing about how an item got there), venue-escrow (listed), wallet, or unknown (the collection account could not be read, so nobody could be checked against the issuer's key). An item currently listed for sale shows the MARKETPLACE'S ESCROW as its owner, not the seller: call get_asset_provenance on that mint to see who handed it over.

Inputs: collection (required), max, trait, value, +1 more.

get_collection_salesSales over a periodA
Read-only

Sales for a collection over the last N days, as Magic Eden recorded them, with every sale named by the chain's asset index so it can be filtered and grouped by player, character or issue: how many sold, total volume, highest and lowest sale, median and average, unique buyers and sellers, the biggest buyers, a per-day series for charts, a per-name breakdown, and the split between the order book and Magic Eden's AMM pools. Answers 'how many sales this week', 'how many Ohtani cards sold', 'which player sold the most', 'what was the top sale', 'is volume up', 'chart the last month', 'who is buying'. The result says how far back the feed was read and whether older sales exist beyond the page budget; it never fills a gap with an estimate. Magic Eden's API feed only: each row carries the execution marketplace that feed reported, and fills it did not index are not here.

Inputs: symbol (required), days, maxPages, nameContains.

get_collection_statsCollection statsA
Read-only

Market + supply stats for a collection. Accepts a registry id, a Magic Eden symbol, or a Metaplex Core collection ADDRESS. Addresses are decoded straight from the chain (name, minted, current size) - works for collections no marketplace indexes, e.g. Candy Digital drops. When OpenSea can be read (the server issues itself a free key, or uses OPENSEA_API_KEY), an OpenSea cross-marketplace view is added (pass openseaSlug, or rely on registry entries that carry one): OpenSea's floor, supply and royalty, plus its 7-day floor trend and the largest holders with their share of supply. Answers 'is the floor up or down this week', 'who holds the most', 'is one wallet holding half of it'.

Inputs: collection (required), openseaSlug.

get_floor_pricesFloor prices (Magic Eden only)A
Read-only

Current floor price in SOL for up to 10 collections, read from MAGIC EDEN ONLY - it takes Magic Eden symbols and returns Magic Eden rows, with no other marketplace and no other currency, whether or not an OpenSea key is configured. For a cross-marketplace floor comparison use get_collection_stats, which quotes each marketplace in its own currency and refuses to compare across them. Use search_collections first if you only know a human name.

Inputs: symbols (required).

get_integration_recipeGet a build recipeA
Read-only

Use when the user wants to BUILD something with collectible data - a sales bot, a floor dashboard, a provenance page, a wallet tracker, a pack-pull watcher - rather than just look a number up. Returns the verified endpoints and their real rate limits, a runnable skeleton, the steady-state running cost, a pre-launch checklist, and the specific ways this kind of integration fails SILENTLY. The pitfalls come from production incidents on live trackers (a feed capped too low silently dropped 8,409 real records; an idle two-minute cron cost $180 in a month) and are not in any API documentation. Read this BEFORE writing integration code, not after it breaks.

Inputs: goal (required).

get_recent_salesRecent salesA
Read-only

Most recent completed sales for a collection (price in SOL, buyer, seller, tx signature). Accepts a registry id or Magic Eden symbol. When OpenSea can be read and a slug is known (or passed as openseaSlug), OpenSea sales are included for a cross-marketplace picture.

Inputs: collection (required), limit, openseaSlug.

get_source_statusWhich sources are answeringA
Read-only

Live health of every data source this server reads, with tier, what each answers, what it cannot see, which need a key, and the fallback order. Answers 'is Magic Eden down', 'why is a number missing', 'what does this tool read', 'which sources need a key'. Use it when a result came back partial.

Inputs: no named parameters.

get_top_tradersTop traders of a collectionA
Read-only

The wallets with the most trading volume in a collection as Magic Eden counts it (its own fills, all time, buying and selling together). Answers 'who trades this most', 'is one wallet moving this market'. It is not a buyer ranking: for who spent the most in a recent window use get_collection_sales (topBuyers), and for who holds the most use get_collection_holders. Volume on other marketplaces is invisible here. A high-volume wallet can be a collector, a market maker or a wash trader; get_wallet_activity shows its buy/sell pattern, which is evidence to weigh, not a verdict on intent.

Inputs: symbol (required), limit.

get_wallet_activityWallet activity & behaviourA
Read-only

How a wallet trades: buys and sells with SOL totals, net flow, listings and bids, which marketplace (Magic Eden order book vs AMM pools; OpenSea with a key), the collections it trades most, every flip (bought then sold: hold time and P&L before fees), a behaviour label (flipper / holder / mixed / lister / quiet) with the reason, and the first purchase inside the window. With OpenSea readable (a self-issued free key, or OPENSEA_API_KEY), plain transfers are included so 'was this airdropped, gifted or bought?' gets an evidence-based answer. Every figure says which feed it came from and what that feed cannot see. Read-only; needs no key.

Inputs: wallet (required), pages, includeOpenSea.

get_wallet_holdingsWallet holdingsA
Read-only

Collectibles held by a wallet, from two independent readers: Magic Eden's index (names, collections, images, listing state) and the chain's own asset index (every standard, including compressed and unlisted items a marketplace may not carry). Answers 'what does this wallet hold', 'what is in my wallet', 'does this address own anything'. The two counts are compared and any gap is named. Read-only - this server never asks for keys and cannot move anything.

Inputs: wallet (required), limit.

get_wallet_profileWallet profileA
Read-only

What a wallet holds and what that means: items grouped by collection with counts and share of the wallet, which collection dominates, how many are listed or compressed, the creator royalty each collection asks for, share of total supply where a supply is known, a floor-times-count CEILING (never called a value) for the largest holdings, and the wallet's age and transaction count from the chain. Answers 'what do they collect', 'how much of X do they own', 'how big a holder are they', 'is this a fresh wallet', 'what is it worth at floor' - with each number labelled for what it is. Read-only; needs no key.

Inputs: wallet (required), maxItems, priceTop, includeAge.

identifyIdentify anythingA
Read-only

START HERE when you do not already know what an identifier is. Takes ANY string a user might paste - a Solana address, a marketplace symbol or slug, or a plain collection name - works out what it actually is, which marketplaces list it, and which tools to call next. Works on collections that launched today and are in no registry, because it probes live sources rather than matching a hardcoded list. Returns the evidence: every source checked INCLUDING the ones that found nothing, what was not checked and why, and a confidence rating. Never report 'this does not exist' from an empty result - report what was searched.

Inputs: query (required).

search_collectionsSearch collectionsA
Read-only

Find digital-collectible collections by name (e.g. 'candy gold series', 'batman', 'mad lads'). Returns curated entries with the identifiers other tools need (Magic Eden symbol, Core collection address). Collections not in the registry still work: pass a Magic Eden symbol or a Metaplex Core collection address directly to the other tools.

Inputs: query (required).

verify_claimVerify a claim against the chainA
Read-only

Check whether something a user was TOLD is actually true. Use this whenever a claim about a collection or asset carries stakes - a project announcing a supply, a seller saying a card has never been traded, a post claiming a wallet holds something, a quoted floor price. Returns confirmed, contradicted, or unverifiable, together with the exact numbers observed, where they were read, and instructions to reproduce the check independently - so the answer does not require trusting this server either. Willingly answers UNVERIFIABLE rather than guessing; a tool that always returns true or false will eventually return false with confidence.

Inputs: claim (required), subject (required), value, wallet.

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

Loading tool schema changelog…

    TDQS

    A4.2/5.0

    Scored across 21 tools

    Disambiguation4/5

    The descriptions go to unusual lengths to separate tools, explicitly stating when to use one vs another (e.g. get_floor_prices vs get_collection_stats, get_top_traders vs get_collection_sales vs get_collection_holders, get_wallet_holdings/profile/activity). Still, a few pairs genuinely overlap: get_recent_sales vs get_collection_sales both return collection sales, and the three wallet tools share a subject, so an agent could misselect without rereading the fine print.

    Naming Consistency4/5

    Names are uniformly lowercase snake_case and heavily dominated by a verb_noun pattern (get_collection_stats, get_wallet_activity, find_listings). Minor deviations exist: several verbs are synonyms for retrieval (get vs search_collections vs find_in_group), and identify/verify_claim/explain_mechanics drop the noun, but the set remains predictable.

    Tool Count4/5

    At 21 tools the surface is on the heavy side, but the domain genuinely spans collections, wallets, assets, sales, listings, provenance, trust and reference content, and each tool maps to a distinct query type. Nothing looks like filler, though a couple of retrieval tools could conceivably be merged.

    Completeness5/5

    For a deliberately read-only market/intelligence server the coverage is thorough: identification, discovery, floors/stats, listings, sales, holders, per-wallet and per-asset views, on-chain provenance and trust decoding, plus meta-tools (source status, mechanics, integration recipes, claim verification). No obvious lifecycle gap given the stated read-only purpose.

    Maintenance

    ActivityActive
    ResponsivenessNo recent community issues

    Related MCP Connectors

    Related MCP Servers

    • A
      license
      A
      quality
      D
      maintenance
      Solana DeFi Intelligence MCP server enabling natural language queries for wallet analytics, DeFi positions, protocol metrics, and token prices.
      8
      1
      MIT
    • A
      license
      A
      quality
      D
      maintenance
      MCP server for Hyperliquid that provides read-only on-chain wallet analytics. Enables natural-language queries about positions, fills, funding, and realized PnL for any public address.
      8
      33 npm
      MIT
    • A
      license
      A
      quality
      D
      maintenance
      Provides read-only access to Solana on-chain data, enabling natural language queries for wallet balances, token holdings, prices, transactions, and more via MCP-compatible clients.
      8
      MIT