NFT Metadata API
Let your coding agent pull NFT name, image, and trait metadata from chain given contract address and token ID without wiring your own indexer.
Overview
io.github.Br0ski777/nft-metadata is an MCP server for the Build phase that fetches NFT name, image, and trait metadata from a contract address and token ID via a remote x402-paid API.
What is this MCP server?
- Resolves NFT metadata by contract address plus tokenId (name, image URI, traits).
- Remote MCP over SSE at nft-metadata.api.klymax402.com.
- x402 micropayment on the hosted API—pay per request rather than a flat SaaS seat.
- Published server schema version 1.1.0 with GitHub source nft-metadata-x402.
- Suited for agent-driven collection browsers, rarity tools, and mint UIs.
- Remote MCP endpoint: https://nft-metadata.api.klymax402.com/mcp (SSE)
- Server version 1.1.0 per MCP server schema 2025-12-11
What problem does it solve?
Agents and early NFT UIs stall when every metadata pull means hand-rolling RPC, tokenURI resolution, and JSON parsing.
Who is it for?
Indie builders prototyping NFT dashboards, trait filters, or agent tools against known contract and tokenId pairs.
Skip if: Teams that need full-chain indexing, bulk historical backfills, or zero micropayment dependencies on third-party hosts.
What do I get? / Deliverables
After you add the remote MCP URL, your agent can query normalized NFT metadata in conversation while you focus on product logic.
- Structured NFT metadata (name, image, traits) returned inside agent tool results
- Repeatable metadata queries without custom indexer code in the repo
Recommended MCP Servers
Journey fit
NFT galleries, marketplaces, and agent workflows need on-chain metadata during product build, not after launch. This is a remote MCP integration that connects Claude Code or Cursor to a hosted metadata API instead of custom RPC and IPFS glue code.
How it compares
Remote MCP metadata API with x402 billing, not a local skill or self-hosted indexer node.
Common Questions / FAQ
Who is io.github.Br0ski777/nft-metadata for?
Solo and indie developers using Claude Code, Cursor, or other MCP clients to build NFT-related apps who want metadata without maintaining their own resolver stack.
When should I use io.github.Br0ski777/nft-metadata?
Use it during build when you have contract addresses and token IDs and need name, image, and traits inside agent-driven workflows or quick UI integration.
How do I add io.github.Br0ski777/nft-metadata to my agent?
Register the remote MCP SSE URL https://nft-metadata.api.klymax402.com/mcp in your client’s MCP config, ensure x402 micropayment is configured per the klymax402 setup, then invoke the server tools from the agent.