MCP Server

Requirements:

Add the following block to your Claude Desktop config file:

macOS: ~/Library/Application Support/Claude/claude_desktop_config.json
Windows: %APPDATA%\Claude\claude_desktop_config.json

{
  "mcpServers": {
    "nftdata": {
      "command": "npx",
      "args": ["-y", "nftdata-mcp@1.1.0"],
      "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 hexadecimal characters). Store this value only in the config file on your own machine. Never share it in chat or paste it anywhere else.

After saving, fully restart Claude Desktop. The server communicates over stdio and is launched automatically by the client. Running it manually from a terminal shows no output; it waits for an MCP client to connect.

After restarting Claude Desktop:

1. Open a new conversation.
2. Start with an explicit request to make sure Claude selects the right server when multiple MCP servers are configured:

   Use the NFT Data MCP server.

3. When Claude asks for a collection slug, enter an existing OpenSea collection slug, for example:

   azuki

   This is just an example. You can use the slug of any OpenSea collection.
4. Continue with natural follow-up questions. If the NFT Data server is not selected, ask Claude explicitly to use it.

The get_collection_data tool returns the following fields for any OpenSea collection. Not every field is guaranteed to be populated for every collection.

The following values are from a specific historical query. Market data changes continuously; these are not current live data.

Collection

Market activity

Tool request

{ "collection": "azuki" }

Payment

{
  "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"
}

Claude can present the same underlying data as a summary, table, comparison, or detailed report without changing the source values. Ask Claude for the format you prefer.

Payment protocols

• One protocol per run. The protocol is selected once at server startup. The server never falls back from one protocol to the other and never switches during a run. If the API does not offer an acceptable payment in the selected protocol, nothing is signed and the call fails.
• Only x402 and mpp are accepted. Any other value (for example auto or x402,mpp) stops startup with an error.
• Both protocols use the same dedicated EVM wallet (EVM_PRIVATE_KEY) and the same USDC balance on Base mainnet.
• Price: $0.002 USDC per successful non-cached request in both protocols. Cache hits are free.

x402 v2 (default). Each request is paid automatically. The payment flow:

1. The server sends the API request.
2. The API responds with HTTP 402 and a payment challenge.
3. Before signing, the server validates the challenge:
   • Scheme: exact
   • Network: Base mainnet (eip155:8453)
   • USDC contract: 0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913
   • Amount: exactly 2000 atomic units ($0.002)
   • Recipient: 0x344143199642e87320785823c20c2df107d17534
4. If all values match, the wallet signs and submits the payment.
5. The API returns the collection data and an on-chain transaction hash.

MPP mode. To pay with MPP (EVM charge, USDC on Base mainnet) instead of x402, add NFTDATA_PAYMENT_PROTOCOL to the env block of your MCP server configuration:

"env": {
  "EVM_PRIVATE_KEY": "YOUR_EVM_PRIVATE_KEY",
  "NFTDATA_PAYMENT_PROTOCOL": "mpp"
}

• The same checks apply before signing: Base mainnet, USDC, exactly 2000 atomic units ($0.002), and the official recipient. Payment splits are refused.
• At most one payment credential is signed per tool call. A repeated 402 after payment is not retried.
• The spend limit, the 5-minute cache, and de-duplication of concurrent identical calls work the same way in both modes.

Successful non-cached responses include a transaction hash and a BaseScan verification link. Cache hits (results served from the 5-minute per-slug cache) are free and do not include a new hash.

Data network vs. payment network

Clone the repository and install dependencies:

npm install

Set EVM_PRIVATE_KEY for the current shell session only, then start:

export EVM_PRIVATE_KEY=0x...
npm start

$env:EVM_PRIVATE_KEY = "0x..."
npm start

set EVM_PRIVATE_KEY=0x...
npm start

To use a local checkout with Claude Desktop, set "command": "npx" and "args": ["tsx", "/absolute/path/to/nftdata-mcp/server.ts"] in the config.

Build and test:

npm run build   # compiles TypeScript to dist/
npm test        # offline unit tests, no network calls and no payments