MCP servers · br0ski777

NFT Metadata API

MCP server that returns NFT metadata, including name, image, traits and collection info, for a contract address and token ID on Ethereum and Base, paid per call via x402.

This text was machine-translated from the publisher's own information and has not been checked by a human editor. The publisher's original text is the reference.

This resource was imported automatically from the sources listed below and has not been reviewed by the AI Gate team yet. The description is the publisher's own, as published. Check the repository before installing.

What it does

The crypto_get_nft_metadata tool takes an NFT contract address and token ID and returns the token name, description, image URL, attributes as trait objects, collection name and contract information, token standard (ERC-721 or ERC-1155), and chain. It covers Ethereum and Base, with Ethereum as the default chain.

Use it when an agent needs to verify, display or analyse the traits of a specific NFT. The publisher names NFT marketplace agents and collection tools as typical users. For wallet balances, ENS resolution or token safety checks, the publisher directs users to other tools: wallet_get_portfolio, crypto_resolve_ens and token_check_safety.

It is offered as an MCP server for clients such as Claude Desktop, Cursor and ElizaOS, and also as a plain HTTP POST endpoint. Each call is paid in USDC on Base through the x402 protocol, which an x402-aware client handles automatically. No API key or signup is needed. The tool is part of the klymax402 marketplace of x402 micropayment APIs and is released under the MIT licence.

Limitations and requirements

Every call requires payment in USDC on Base through the x402 protocol, so an x402-aware client and a funded wallet are needed. The price is $0.008 per call. Supported chains are Ethereum and Base only.

Safety

Our team has not reviewed this resource. Only automated rules checked it; resources with high-risk signals are not published. These are signals, not a guarantee that installing it is safe. Try it in a sandbox project first.

  • Runs code or changes an assistant's behaviour

Sources

  • Official MCP Registry first seen 13 Nov 2026 · last seen 13 Nov 2026 · its page on the source
    NFT Metadata API

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

    v1.1.0
    As shown on registry.modelcontextprotocol.io when we last read it
MCP servers
cloudflare

Cloudflare MCP servers

Cloudflare's hosted MCP servers for its products: documentation search, sandbox containers, browser rendering, Radar internet data, logs and analytics, Workers and more.

4.5K GitHub starsCloud & DevOpsSoftware development
Updated 17 Nov 2026
MCP servers
redis

Redis MCP Server

Redis's official MCP server that lets an AI assistant store, read and search data in a Redis database, including streams, JSON documents and vector indexes.

642 GitHub starsData & databasesSoftware development
Updated 17 Nov 2026
MCP servers
microsoft

Playwright MCP (browser automation)

Microsoft's MCP server that lets an AI assistant open web pages, click, type and read them through a real browser, using the page structure instead of screenshots.

39.6K GitHub starsTesting & QAWeb, search & browser
Updated 17 Nov 2026
MCP servers
hashicorp

Terraform MCP Server (HashiCorp)

HashiCorp's MCP server that gives an assistant current Terraform Registry information on providers, modules and policies, and can manage HCP Terraform workspaces.

1.6K GitHub starsCloud & DevOpsSoftware development
Updated 17 Nov 2026