NFT Metadata API

io.github.Br0ski777Published by GitHub account Br0ski777v1.1.0Updated Nov 2, 2026

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

VerifiedSSEWeb executableWeb Search & ScrapingFinance

Overview

AI-generated overview

Remote MCP endpoint that fetches NFT metadata — name, image, traits and collection info — from a contract address and token ID on Ethereum or Base, paid per…

What you can do
  • Fetch NFT metadata for a specific token from its contract address and token ID
  • Return name, description, image URL, trait attributes, collection info, token standard and chain
  • Choose between Ethereum and Base as the chain, defaulting to Ethereum
  • Pay per call through an x402 micropayment challenge instead of an API key
When to use it
Useful for agents that verify, display or analyze individual NFTs, such as marketplace or collection tooling. It covers only single-token metadata lookup, not wallet balances, ENS resolution or token safety checks.
Requirements
A remote MCP client pointed at the hosted endpoint; nothing to install locally. No API key or signup, but each call is paid in USDC on Base L2 through the x402 protocol, so an x402-capable client with a funded wallet is needed. Network access to the provider and its payment facilitator.
Before you install
Calls cost money: the listed price is $0.008 per metadata request, settled in USDC on Base, so an agent can spend funds without a per-call confirmation. It requires a wallet that can sign x402 payments, and payment handling passes through third-party facilitators. The service is a single hosted provider with no declared authentication.

Installation

In SourceWeft

  1. Open NFT Metadata API in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Web executable via SSE. Remote servers run from the web runtime once configured in a workspace.

Use with an agent

Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.

Read https://sourceweft.com/mcp/io.github.Br0ski777%2Fnft-metadata/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config.

{
  "mcpServers": {
    "nft-metadata-api": {
      "type": "sse",
      "url": "https://nft-metadata.api.klymax402.com/mcp"
    }
  }
}

README

NFT Metadata API

[MCP Server] [x402] [License: MIT]

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.):

json
{  "mcpServers": {    "nft-metadata": {      "url": "https://nft-metadata.api.klymax402.com/mcp"    }  }}

Quickstart -- HTTP (x402)

bash
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:

json
{"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

Source: README.md at commit c61be67

Tools

0
SourceWeft has not read this server's tools yet.

Version history

1
  1. v1.1.0LatestSep 16, 2026

Score

50% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 daysRequired25 pts

    Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.

  • Auth declaredRequired10 pts

    Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.

  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts
  • License10 pts