Repository navigation
Releases
Releases · Nomad07/nftdata-mcp
NFT Data MCP v1.0.3
NFT Data MCP v1.0.3
Documentation improvements
- Clarified that
azukiis an example collection slug, not a requirement. - Simplified the Claude Desktop first-query instruction.
- Updated the npm configuration example to use
nftdata-mcp@1.0.3.
Verification
- All 33 tests passed.
- Published
nftdata-mcp@1.0.3to npm. - Published
io.github.Nomad07/nftdata-mcp@1.0.3to the Official MCP Registry.
NFT Data MCP v1.0.2
NFT Data MCP v1.0.2
Changes
- Synchronized MCP server version metadata to
1.0.2. - Improved README documentation for supported payment protocols and payment networks.
- Expanded multichain documentation, highlighting Ethereum, Base, Ink, Arc, HyperEVM, Robinhood Chain, Solana, and other supported networks.
Validation
- Tests: 33 passed.
- TypeScript build: successful.
No payment implementation or runtime behavior changes in this release.
NFT Data MCP v1.0.1
What's new in v1.0.1
- Include the payment transaction hash and BaseScan verification link in successful MCP tool responses.
- Extract payment transaction hashes from payment response headers.
- Keep cached collection data separate from payment receipts to ensure each response reports the correct transaction.
- Add tests for payment receipt handling and transaction hash validation.
Verification
- All 33 tests pass.
- Published to npm as
nftdata-mcp@1.0.1. - Tested successfully with Claude Desktop on Base Mainnet.
NFT Data MCP v1.0.0
Initial release of nftdata-mcp, an MCP server for retrieving OpenSea NFT collection data through the NFT Data API.
- MCP tool:
get_collection_data - Local MCP transport: stdio
- Payment protocol: x402 on Base mainnet
- Price: $0.002 in USDC per successful API request
- Package: https://www.npmjs.com/package/nftdata-mcp
- MCP Registry: https://registry.modelcontextprotocol.io/?q=nftdata
Requires Node.js 20 or newer and a dedicated EVM wallet funded with USDC on Base. Configure EVM_PRIVATE_KEY before starting the server.
See README.md for installation, configuration, security guidance, and limitations.