About Nft Metadata X402
Nft Metadata X402 provides NFT metadata lookups on Ethereum and Base for AI agents and applications that need token details. It supports per-call x402 payments and can be called by MCP clients.
Key features
- 01Look up by contract address and token ID
- 02Return names, descriptions, and image URLs
- 03Provide attributes and collection details
- 04Support Ethereum and Base
- 05Accept per-call x402 payments
Use cases
- 01Verify metadata for a specific NFT
- 02Display NFT details in an application
- 03Analyze NFT traits and collection information
MCP support
Exposes the `crypto_get_nft_metadata` tool to MCP clients for lookups by contract address, token ID, and optional chain. Calls are also available through x402 payments.
Configuration
Remote servers need no local install. Pick your client, then copy the config or install in one click.
https://nft-metadata.api.klymax402.com/mcpclaude mcp add --transport sse nft-metadata-x402 https://nft-metadata.api.klymax402.com/mcp{"mcpServers":{"nft-metadata-x402":{"type":"sse","url":"https://nft-metadata.api.klymax402.com/mcp"}}}Open in Cursor{"servers":{"nft-metadata-x402":{"type":"sse","url":"https://nft-metadata.api.klymax402.com/mcp"}}}Open in VS Code{"mcpServers":{"nft-metadata-x402":{"type":"sse","url":"https://nft-metadata.api.klymax402.com/mcp"}}}{"mcpServers":{"nft-metadata-x402":{"serverUrl":"https://nft-metadata.api.klymax402.com/mcp"}}}Run commands in a terminal; paste JSON into the client’s MCP config and restart. Servers that need sign-in will prompt on first connect.
Tools
Details
From the project READMENFT Metadata API
NFT metadata lookup -- name, image, attributes, collection info from contract + token ID. Ethereum and Base. Pay-per-call via x402 (USDC on Base L2) -- no API key, no signup, no rate-limit wall.
Part of the klymax402 marketplace -- 100 x402 micropayment APIs for AI agents, one wallet, USDC on Base.
Quickstart -- MCP
Add to your MCP client config (Claude Desktop, Cursor, ElizaOS, etc.):
{
"mcpServers": {
"nft-metadata": {
"url": "https://nft-metadata.api.klymax402.com/mcp"
}
}
}
Quickstart -- HTTP (x402)
curl -X POST "https://nft-metadata.api.klymax402.com/api/metadata" \
-H "Content-Type: application/json" \
-d '{"contract":"...","tokenId":"..."}'
# -> 402 Payment Required, with an x402 payment challenge in the response body
Any x402-aware client (@x402/fetch, x402-agent-tools, ATXP) handles the 402 -> sign -> retry cycle automatically.
Tools
| Tool | Method | Path | Price | Description |
|---|---|---|---|---|
crypto_get_nft_metadata | POST | /api/metadata | $0.008 | Fetch NFT metadata from contract and token ID |
crypto_get_nft_metadata
Use this when you need to fetch metadata for a specific NFT by contract address and token ID. Returns full NFT details in JSON.
Parameters
| Name | Type | Required | Description |
|---|---|---|---|
contract | string | yes | NFT contract address (e.g. 0xBC4CA0EdA7647A8aB7C2061c2E118A18a936f13D) |
tokenId | string | yes | Token ID within the contract |
chain | string | no | Blockchain: 'ethereum' or 'base' (default: ethereum) |
Returns
name-- NFT token namedescription-- token description textimageUrl-- URL to the NFT image/mediaattributes-- array of trait objects with trait_type and valuecollection-- collection name and contract infotokenStandard-- ERC-721 or ERC-1155chain-- which blockchain the NFT is on
Example response:
{"name":"Bored Ape #1234","description":"A unique digital collectible...","imageUrl":"ipfs://Qm...","attributes":[{"trait_type":"Background","value":"Blue"},{"trait_type":"Fur","value":"Gold"}],"collection":"BoredApeYachtClub","tokenStandard":"ERC-721","chain":"ethereum"}
When to use: NFT verification, display, and trait analysis. Essential for NFT marketplace agents and collection tools.
Not for: wallet balances (use wallet_get_portfolio), ENS resolution (use crypto_resolve_ens), token safety (use token_check_safety).
Example agent prompts
- "Fetch metadata for a specific NFT by contract address and token ID"
Payment
- Protocol: x402 -- HTTP-native pay-per-call, no signup, no API key
- Network: Base L2 (
eip155:8453) - Asset: USDC
- Facilitator: Coinbase CDP (primary), PayAI (fallback)
- Also reachable via ATXP (OAuth-wrapped x402, RFC 9728 protected-resource metadata)
Part of klymax402
100 x402 micropayment APIs for AI agents -- one wallet, USDC on Base, zero signup.
- Catalog: https://klymax402.com/llms.txt
- Full API reference: https://klymax402.com/llms-full.txt
- Live stats: https://klymax402.com/stats
License
MIT
Comments
New to MCP?
From what the protocol is to installing your first server, these answers cover most first questions.
An open protocol that defines how AI applications connect to external tools and data in a uniform way. Clients talk to the model; MCP servers provide tools, resources and prompt templates. They exchange standard messages, so one server can be reused by many clients.