Server data from the Official MCP Registry
Fetch NFT metadata — name, image, traits from contract+tokenId. x402 micropayment.
Fetch NFT metadata — name, image, traits from contract+tokenId. x402 micropayment.
Remote endpoints: sse: https://nft-metadata.api.klymax402.com/mcp
Valid MCP server (1 strong, 0 medium validity signals). No known CVEs in dependencies. Imported from the Official MCP Registry. Trust signals: trusted author (146/150 approved); 6 highly-trusted packages.
1 tool verified · Open access · No issues found
Security scores are indicators to help you make informed decisions, not guarantees. Always review permissions before connecting any MCP server.
This plugin requests these system permissions. Most are normal for its category.
Remote Plugin
No local installation needed. Your AI client connects to the remote endpoint directly.
Add this to your MCP configuration to connect:
{
"mcpServers": {
"io-github-br0ski777-nft-metadata": {
"url": "https://nft-metadata.api.klymax402.com/mcp"
}
}
}From the project's GitHub README.
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.
Add to your MCP client config (Claude Desktop, Cursor, ElizaOS, etc.):
{
"mcpServers": {
"nft-metadata": {
"url": "https://nft-metadata.api.klymax402.com/mcp"
}
}
}
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.
| Tool | Method | Path | Price | Description |
|---|---|---|---|---|
crypto_get_nft_metadata | POST | /api/metadata | $0.003 | Fetch NFT metadata from contract and token ID |
crypto_get_nft_metadataUse 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 onExample 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).
eip155:8453)100 x402 micropayment APIs for AI agents -- one wallet, USDC on Base, zero signup.
MIT
Be the first to review this server!
by Modelcontextprotocol · Developer Tools
Read, search, and manipulate Git repositories programmatically
by Toleno · Developer Tools
Toleno Network MCP Server — Manage your Toleno mining account with Claude AI using natural language.
by mcp-marketplace · Developer Tools
Create, build, and publish Python MCP servers to PyPI — conversationally.