NFT Data MCP
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| NFTDATA_URL | No | Override the API endpoint | https://www.nftdata.app/api/get-collection-data |
| EVM_PRIVATE_KEY | Yes | Private key of the wallet that pays for calls | |
| NFTDATA_MAX_REQUESTS | No | Max paid requests per session | 100 |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| get_collection_dataA | Get OpenSea NFT collection market data in one call: name, contracts, floor price, 1/7/30-day and lifetime sales and volume, unique owners, total supply, creation date. Costs $0.002 per call (x402). |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
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.