English Français العربية

NFT Metadata API

Official registry Media and design

Fetch NFT metadata — name, image, traits from contract+tokenId. x402 micropayment.

Source code Website Documentation

Install

Add this to your client's MCP configuration (Claude Desktop: claude_desktop_config.json; Cursor: .cursor/mcp.json; VS Code and others use the same "mcpServers" shape).

Remote (sse)
Claude Code 
claude mcp add --transport sse nft-metadata-api 'https://nft-metadata.api.klymax402.com/mcp'
JSON configuration (Claude Desktop, Cursor, VS Code) 
{
    "mcpServers": {
        "nft-metadata-api": {
            "type": "sse",
            "url": "https://nft-metadata.api.klymax402.com/mcp"
        }
    }
}

Documentation

From the project's README on GitHub, refreshed weekly. Links open on GitHub.

Contents
  1. NFT Metadata API
  2. Quickstart -- MCP
  3. Quickstart -- HTTP (x402)
  4. Tools
  5. Example agent prompts
  6. Payment
  7. Part of klymax402
  8. License

NFT 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

ToolMethodPathPriceDescription
crypto_get_nft_metadataPOST/api/metadata$0.008Fetch 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

NameTypeRequiredDescription
contractstringyesNFT contract address (e.g. 0xBC4CA0EdA7647A8aB7C2061c2E118A18a936f13D)
tokenIdstringyesToken ID within the contract
chainstringnoBlockchain: 'ethereum' or 'base' (default: ethereum)

Returns

  • name -- NFT token name
  • description -- token description text
  • imageUrl -- URL to the NFT image/media
  • attributes -- array of trait objects with trait_type and value
  • collection -- collection name and contract info
  • tokenStandard -- ERC-721 or ERC-1155
  • chain -- 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.

License

MIT

Frequently asked questions

What is NFT Metadata API?

Fetch NFT metadata — name, image, traits from contract+tokenId. x402 micropayment.

How do I install NFT Metadata API?

It runs as a remote server. In Claude Code: claude mcp add --transport sse nft-metadata-api 'https://nft-metadata.api.klymax402.com/mcp'. For other clients, paste the JSON configuration from this page into their MCP settings.

Does NFT Metadata API need an API key?

Its registry entry lists no required key or secret. Some features may still need an account with the service it connects to.

Is NFT Metadata API open source?

Yes. Its code is on GitHub under the MIT license.

Who maintains NFT Metadata API?

It is published by Br0ski777. AI.tn lists it but does not maintain or endorse it.

From the official MCP Registry. Listing is not an endorsement: review a server's code and permissions before giving it access to your data.