NFT Data MCP
Related Servers
Alternatives to NFT Data MCP
No user-submitted related servers found.
Related Servers
- AlicenseAqualityCmaintenanceEnables AI agents to fetch crypto market and on-chain data, including prices across venues, token facts, OHLC candles, market overview, DeFi TVL, and wallet balances, with two free tools and the rest paid per call in USDC on Base via x402.848 npmMIT
- AlicenseNot gradedqualityCmaintenanceNFT collection floor price, volume, holders, rarity data for Ethereum and Base via Alchemy. Pay-per-call via x402 (USDC on Base L2) without API key or signup.MIT
- AlicenseAqualityCmaintenanceEnables AI agents to access pay-per-call Base and Polygon onchain data (balances, tokens, transactions, gas, blocks, and trending pairs) settled in USDC via x402, with no API key required.18MIT
- AlicenseNot gradedqualityCmaintenanceEnables AI agents to access crypto market data such as prices, extreme funding rates, and briefs through MCP tools, with paid calls settled in USDC on Base via x402.MIT
- AlicenseNot gradedqualityCmaintenanceEnables AI agents to verify that an x402 API is live, real, and fairly priced before authorizing a payment, and to query live market data on agent commerce across Base and Solana. Exposes twelve tools covering pre-payment checks, provider ranking, liveness lookups, market snapshots and diffs, circular-settlement and whale signals, token metrics, provider revenue, and monthly report data, with free, free-key, and paid x402 tiers.MIT
- AlicenseNot gradedqualityCmaintenanceEnables agents to call paid on-chain data tools for receipt verification, wallet balances, transaction status, and address activity. Tool calls return x402 payment terms and settle in USDC on Base.MIT
TDQS
Scored across 1 tool
There is only one tool, so there is no possibility of selecting the wrong tool or confusing it with another. Its purpose (fetch market data for a single OpenSea collection) is unambiguous.
The single tool follows a clear, conventional verb_noun snake_case pattern (get_collection_data). With a one-tool surface there is no competing convention to clash with.
The tool bundles the entire collection-data lookup into one call, which is well-matched to a narrow data-provider service. However, a single-tool surface is thin by the rubric's standards, and there is no companion operation (e.g. resolving or searching collections) to round it out.
For a 'get data for one collection' endpoint the payload is comprehensive (floor, sales, volume, owners, supply). But the surface has no way to discover or search collections—the caller must already know the exact OpenSea slug—and no historical/timeseries retrieval, which are notable gaps for an NFT data service.