An MCP server that exposes the NFT Data API to AI clients (Claude Desktop, Cursor, etc.) as a single
An MCP server that exposes the NFT Data API to AI clients (Claude Desktop, Cursor, etc.) as a single tool. It handles the selected x402 and MPP payment flow automatically.
·
A multichain NFT data MCP server that gives AI assistants, agents, and other MCP-compatible clients access to the NFT Data API through a single tool: get_collection_data.
Compatible with Claude Desktop and other MCP-compatible applications, AI agents, and clients, including future clients that support the Model Context Protocol (MCP).
Each API request is paid automatically at $0.002 in USDC on Base using the x402 payment protocol (default) or, when you select it, the Machine Payments Protocol (MPP).
Retrieve NFT collection data across 30+ blockchain networks through the NFT Data API's OpenSea integration, including Ethereum, Base, Ink, Arc, HyperEVM, Robinhood Chain, Solana, and more.
Always use a dedicated wallet with only a small balance. Never use your primary wallet or share its private key.
Add the following block to claude_desktop_config.json (usually found in ~/Library/Application Support/Claude/ on macOS or %APPDATA%\Claude\ on Windows):
{
"mcpServers": {
"nftdata": {
"command": "npx",
"args": ["-y", "[email protected]"],
"env": {
"EVM_PRIVATE_KEY": "YOUR_EVM_PRIVATE_KEY"
}
}
}
}Replace YOUR_EVM_PRIVATE_KEY with the private key of your dedicated wallet (0x followed by 64 hex characters). Then restart Claude Desktop.
The server communicates over stdio and is launched automatically by Claude Desktop. Running it by hand shows no output; it waits for an MCP client to connect.
After restarting Claude Desktop:
Open a new conversation.
To make sure Claude selects the right server when you have multiple MCP servers configured, start with an explicit request:
Use the NFT Data MCP server
When Claude asks for a collection slug, enter an example slug such as:
azuki
You can use the slug of any existing NFT collection instead.
Continue with natural follow-up questions. If Claude does not use the NFT Data server, ask it explicitly to do so.
You can also ask directly by collection name or OpenSea slug. Claude will retrieve the latest collection statistics, including floor price, sales volume, owner count, supply, and lifetime metrics. Each newly paid successful request includes a payment transaction hash and a BaseScan verification link. Cached responses do not, because no new payment is made.
The following is an example response from one query. Market data changes continuously; these values are from a specific query and are not current live data.
Collection overview
| Field | Value |
|---|---|
| Name | Azuki |
| Slug | azuki |
| Chain | Ethereum |
| Contract | 0xed5af388653567af2f388e6224dc7c4b3241c544 |
| Created | January 12, 2022 |
| Total supply | 10,000 |
| Unique owners | 4,394 |
| Floor price | 0.4933 ETH |
Market activity
| Period | Sales | Volume |
|---|---|---|
| 24 hours | 21 | 10.15 ETH |
| 7 days | 163 | 96.68 ETH |
| 30 days | 471 | 325.72 ETH |
| Lifetime | 93,156 | 831,992.65 ETH |
Payment
| Field | Value |
|---|---|
| Cost | $0.002 |
| Protocol | x402 |
| Transaction | 0x4fb3...580f8 |
The server supplies the underlying collection data returned by the API. Claude can organize that information in the format you prefer, from a concise summary to a detailed report, tables, or comparisons. Simply ask Claude how you want the results presented. This changes the presentation, not the source values.
Claude Desktop may show the tool request and returned data through its tool-activity details (the exact label varies by client version).
Tool request
{ "collection": "azuki" }{
"name": "Azuki",
"slug": "azuki",
"contracts": [
{
"address": "0xed5af388653567af2f388e6224dc7c4b3241c544",
"chain": "ethereum"
}
],
"floor_price": 0.49328599,
"floor_price_currency": "ETH",
"one_day_sales": 21,
"one_day_volume": 10.150091000000002,
"seven_day_sales": 163,
"seven_day_volume": 96.67526161112121,
"thirty_day_sales": 471,
"thirty_day_volume": 325.72023569476767,
"total_sales": 93156,
"total_volume": 831992.6461159982,
"num_owners": 4394,
"total_supply": 10000,
"created_date": "2022-01-12",
"one_day_volume_currency": "ETH",
"seven_day_volume_currency": "ETH",
"thirty_day_volume_currency": "ETH",
"total_volume_currency": "ETH"
}Raw floating-point values have more decimal places than the rounded values in the report above.
Payment verification
Transaction hash: 0x4fb35acc31a9f6841647ca2533a7f9ac7113f54364e979b8de4786bf1de580f8
Verify on BaseScan: https://basescan.org/tx/0x4fb35acc31a9f6841647ca2533a7f9ac7113f54364e979b8de4786bf1de580f8
| Product | Payment Protocols | Payment Networks |
|---|---|---|
| NFT Data (website/API) | x402 and MPP | x402 - Base and Solana; MPP - Base |
| NFT Data (MCP server) | x402 (default) or MPP, selected with NFTDATA_PAYMENT_PROTOCOL | x402 - Base; MPP - Base |
Note: The NFT Data website/API and the NFT Data MCP server have different payment capabilities. The MCP server pays on Base only, with one protocol per run (x402 by default, MPP if you set
NFTDATA_PAYMENT_PROTOCOL=mpp). Solana is not supported by the MCP server.
Data network refers to the blockchain where an NFT collection exists. NFT Data is a multichain service supporting NFT collections across 30+ blockchain networks through the NFT Data API's OpenSea integration, including Ethereum, Base, Ink, Arc, HyperEVM, Robinhood Chain, and Solana, among others. OpenSea continues to expand its supported blockchain networks, so coverage may grow over time. The data network is independent of the payment network used to pay for API requests.
Payment network refers to the blockchain used to pay for each API request. This server pays on Base mainnet only, using USDC via x402 or MPP, regardless of which chain the queried collection is on.
Each request is paid automatically using the x402 protocol over Base mainnet. The payment flow:
exacteip155:8453)0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913)0x344143199642e87320785823c20c2df107d17534Every newly paid successful request includes:
Payment: 0x...
Verify: https://basescan.org/tx/0x...A cache hit (the same collection requested again within 5 minutes) is served without a new payment, so it does not include these lines.
This server supports x402 and MPP on Base only. Solana payments are not implemented.
Set NFTDATA_PAYMENT_PROTOCOL=mpp to pay with MPP (EVM charge, USDC on Base) instead of x402:
"env": {
"EVM_PRIVATE_KEY": "YOUR_EVM_PRIVATE_KEY",
"NFTDATA_PAYMENT_PROTOCOL": "mpp"
}x402 and mpp are accepted; any other value (for example auto or x402,mpp) stops startup with an error.EVM_PRIVATE_KEY) and the same USDC balance on Base.| Variable | Required | Default | Description |
|---|---|---|---|
EVM_PRIVATE_KEY | yes | - | Private key (0x + 64 hex chars) of the wallet that pays for calls |
NFTDATA_MAX_REQUESTS | no | 100 | Max signed payments per session. Integer 1–1000; any other value stops startup with an error |
NFTDATA_PAYMENT_PROTOCOL | no | x402 | Payment protocol: x402 or mpp. Unset or empty selects x402; any other value stops startup with an error |
NFTDATA_TIMEOUT_MS | no | 15000 | Request timeout in milliseconds (1000–60000) |
NFTDATA_URL | no | https://www.nftdata.app/api/get-collection-data | Accepts only the official NFT Data endpoint; anything else stops startup |
POST /api/get-collection-data with body {"collection": "<slug>"}.^[a-z0-9][a-z0-9_-]*$ (max 100 characters); otherwise no request is made.NFTDATA_MAX_REQUESTS, including payments for requests that later fail or time out.400 (invalid slug), 404 (collection not found), 429 (rate limit, with retry delay), timeouts, and other failures. Server and payment details are not exposed to the MCP client.Server does not appear in Claude Desktop
Verify the claude_desktop_config.json path, check for JSON syntax errors, and restart Claude Desktop fully.
EVM_PRIVATE_KEY is missing or malformed
The key must be 0x followed by exactly 64 hex characters. Check for extra whitespace or a missing 0x prefix.
paid request limit ... reached
The session has reached NFTDATA_MAX_REQUESTS. Restart Claude Desktop to reset the counter, or set a higher limit.
Request timed out A payment may have been signed before the timeout. The server does not retry automatically.
Imports fail after an SDK update The x402 SDK changes frequently. Check the x402 docs and the nftdata-mcp changelog for the latest compatible version.
npm installSet the key for the current shell session only, then start:
# macOS / Linux
export EVM_PRIVATE_KEY=0x...
npm start# Windows PowerShell
$env:EVM_PRIVATE_KEY = "0x..."
npm start:: Windows cmd
set EVM_PRIVATE_KEY=0x...
npm startTo use a local checkout with Claude Desktop, set "command": "npx" and "args": ["tsx", "/absolute/path/to/nftdata-mcp/server.ts"].
npm run build # compiles to dist/
npm test # offline tests (mocked API), no network and no real paymentsOFFICIAL_PAY_TO in lib.ts and release a new version.@x402/* and mppx SDKs. npm test exercises them against a mocked API (no real payments).Pick your client and paste the snippet. Each one is the same server, written the way that client expects it.
claude mcp add nftdata -- npx -y [email protected]{
"mcpServers": {
"nftdata": {
"env": {
"EVM_PRIVATE_KEY": ""
},
"args": [
"-y",
"[email protected]"
],
"command": "npx"
}
}
}code --add-mcp '{"name":"nftdata","env":{"EVM_PRIVATE_KEY":""},"args":["-y","[email protected]"],"command":"npx"}'[mcp_servers.nftdata]
command = "npx"
args = ["-y", "[email protected]"]Runs locally on your device. Your client starts the server itself, so nothing has to be hosted.
Paste this prompt into your agent. It reads this page and does the setup for you.
Read https://aiagentslisting.com/mcp/nft-data-mcp to learn what the "NFT Data MCP" MCP server does and how to install it. Add it to my coding agent's MCP configuration as documented on that page, then confirm the server connects and list the tools it exposes.Agents can also browse this directory over MCP at https://aiagentslisting.com/api/mcp
This server runs locally, so we can't read its tool list over the web yet.
We could not run this server: its npm package has not answered in our offline sandbox, which usually means it needs an API key or other configuration to start. The four checks that need a live server are left out, and the grade tops out at B until we can read its tools.
Paste this line near the top of your repository's README. The badge always renders the current score.
[](https://aiagentslisting.com/mcp/nft-data-mcp)TypeScript client and MCP manifest for Placement API — buy SEO link placements across every
Official MCP bridge for 19 Amazon commerce and market intelligence tools
MCP bridge for ChatGPT to use OpenClaw browser, desktop, file, and runtime tools.
v1.1.0NFT Data MCP v1.1.0Release notesv1.0.3NFT Data MCP v1.0.3Release notesv1.0.2NFT Data MCP v1.0.2Release notesv1.0.1NFT Data MCP v1.0.1Release notesv1.0.0NFT Data MCP v1.0.0Release notesConnect to the AI Agents Listing MCP server at https://aiagentslisting.com/api/mcp using the HTTP transport and complete the sign-in when it asks. Then call the submit_review tool for the listing "nft-data-mcp" with a rating from 1 to 5 and a short note on what worked and what did not.No reviews yet
Be the first to share your experience with this tool.
TypeScript client and MCP manifest for Placement API — buy SEO link placements across every
Developer Tools
Official MCP bridge for 19 Amazon commerce and market intelligence tools
Developer Tools
MCP bridge for ChatGPT to use OpenClaw browser, desktop, file, and runtime tools.
Browser & Scraping
One email a week. New agents, MCP servers and skills, and what is actually getting traction.