SimpleHash MCP. Query Multi-Chain NFT Data via Your AI Agent
Gemini Works with every AI agent you already use
…and any MCP-compatible client
Just plug in your AI agents and start using Vinkius.
SimpleHash Multi-chain NFT API connects your AI client to real-time data across 50+ major blockchain networks, including Ethereum, Polygon, and Solana.
Your agent uses this server to query a wallet's entire NFT portfolio, retrieve deep metadata (traits, image URLs), track transaction history by address or contract, and analyze specific collections—all from one unified API endpoint.
What your AI agents can do
Get collection details
Retrieves general information, links, and metrics for a specific NFT collection using its contract address.
Get collections by wallet
Lists all NFT collections that a specific wallet address currently owns assets from.
Get nft details
Fetches the full metadata and current ownership status for one specific NFT token ID.
The server identifies and lists every NFT owned by a given wallet address across multiple connected blockchains.
It retrieves granular details for a single token, including its unique traits, attribute values, and direct image links.
The server tracks the complete movement history of an asset, filtering transfers by either a wallet address or a smart contract ID.
It pulls collection-level data, giving insights into associated links and current market floor prices.
The server generates a list of every NFT ever minted under a specific smart contract address.
Ask AI about this MCP
Supported MCP Clients
Gemini Waiting for input…
SimpleHash (Multi-chain NFT API): 7 Tools for Web3 Data
These tools let your AI agent query, list, and track every facet of an NFT—from its metadata to its entire transfer history across multiple blockchains.
019e5d55get collection details
Retrieves general information, links, and metrics for a specific NFT collection using its contract address.
019e5d55get collections by wallet
Lists all NFT collections that a specific wallet address currently owns assets from.
019e5d55get nft details
Fetches the full metadata and current ownership status for one specific NFT token ID.
019e5d55get nft transfers by contract
Gets a chronological record of all NFTs that moved through a specified smart contract address.
019e5d55get nft transfers by wallet
Retrieves the complete transaction history, showing every NFT transfer involving a specific wallet address.
019e5d55get nfts by contract
Lists all unique NFTs that were minted under a given smart contract ID across connected chains.
019e5d55get nfts by wallet
Retrieves an inventory of every NFT owned by one wallet address across multiple supported blockchains.
Choose How to Get Started
Build a custom MCP for your own tools, or connect a ready-made integration from our catalog.
Build Your Own
Turn any API into an MCP. Import a spec, define Agent Skills, or deploy with MCPFusion.
- Import from OpenAPI, Swagger, or YAML specs
- Create Agent Skills with progressive disclosure
- Deploy to edge with MCPFusion framework
- Built in DLP, auth, and compliance on every call
- Real time usage dashboard and cost metering
- Publish to catalog or keep private
Make Your AI Do More
Start with SimpleHash (Multi-chain NFT API), then connect any of our 4,700+ other servers whenever your AI needs more. One click, no limits.
- Use this MCP plus 4,700+ others, all in one place
- Add new capabilities to your AI anytime you want
- Every connection is secured and compliant automatically
- Track usage and costs across all your servers
- Works with Claude, ChatGPT, Cursor, and more
- New servers added to the catalog every week
What you can do with this MCP connector
SimpleHash Multi-chain NFT API - Your Direct Line to Blockchain Data
Your agent connects directly to real-time data spanning over 50 major blockchain networks, including Ethereum, Polygon, and Solana. You're not dealing with a bunch of separate APIs; you use one unified endpoint to query everything an NFT owner or analyst needs.
When you wanna check what assets a wallet holds, your agent runs get_nfts_by_wallet, giving you an inventory of every single NFT owned by that address across all connected chains. You can also see the full breadth of collections associated with an address using get_collections_by_wallet.
If you're digging into a specific token, get_nft_details pulls the complete metadata and current ownership status for one particular NFT ID. This includes granular details like unique traits, attribute values, and direct image links for that single token.
To understand the bigger picture of a collection, your agent uses get_collection_details to pull general information, associated links, and key metrics for an entire collection based on its contract address. You can also run get_nfts_by_contract, which lists every unique NFT that's ever been minted under a specific smart contract ID across the connected chains.
Tracking movement is where this thing shines. To see everything that moved through a particular piece of code, you use get_nfts_by_contract to list all NFTs associated with a given smart contract address. If you wanna track an asset's journey by who owned it, get_nft_transfers_by_wallet gives you the total transaction history for a specific wallet address—every NFT transfer that ever touched it.
Conversely, if you know the exact contract that moved the token, get_nft_transfers_by_contract provides a chronological record of all NFTs that passed through that smart contract address.
How SimpleHash MCP Works
- 1 You connect your AI client to the SimpleHash MCP Server and input your API key.
- 2 Your agent executes a tool call (e.g.,
get_nfts_by_wallet) using natural language instructions, specifying the wallet address or contract ID. - 3 The server returns structured JSON data containing all requested NFT details, metadata, and transaction records.
The bottom line is: Your AI client talks to SimpleHash, gets complex blockchain data back, and you use that data without writing a single query script.
Who Is SimpleHash MCP For?
Web3 developers who need reliable, multi-chain indexing shouldn't spend time building custom scrapers. Crypto traders who track portfolios across multiple chains need an immediate view of holdings and transaction history. Blockchain researchers require a single source to aggregate collection metrics and transfer logs.
Uses the server tools to pull NFT metadata, ownership data, and asset details directly into a coding environment or application backend.
Asks the agent to compare current holdings and recent transfer history for several wallets across different chains simultaneously.
Runs multiple tool calls—like get_nfts_by_contract followed by get_nft_transfers_by_wallet—to build a complete lifecycle graph of an asset class.
What Changes When You Connect
- Get a full portfolio view with
get_nfts_by_wallet. You don't have to run separate queries for Ethereum, Polygon, and Solana; the server handles the aggregation automatically. - Deep dive into assets using
get_nft_details. Instead of just getting an ID, you get the traits, the high-res image URL, and structured metadata fields immediately. - Track asset movement with
get_nft_transfers_by_wallet. This tool provides a complete audit log of sales and transfers for any given wallet address over time. - Understand the scope of a project using
get_nfts_by_contract. Run this to list every NFT minted by an IP, letting you map out its full history without knowing individual token IDs. - Build context with
get_collection_details. This gives you collection-level data—like floor price and social links—which helps interpret the raw asset data coming from other tools.
Real-World Use Cases
Auditing a Client's Portfolio
A portfolio manager needs to audit a client. They ask their agent to use get_nfts_by_wallet first to get the total count of assets across all chains. Then, they run get_nft_transfers_by_wallet on key tokens to see exactly when and how those items changed hands.
Analyzing a New Collection
A researcher wants background on 'Project Alpha.' They start by using get_collection_details to understand the lore and links. Next, they use get_nfts_by_contract to list every mint under that contract ID, building a full roster of assets.
Identifying Cross-Chain Ownership
A developer needs to build an inventory tool. They use the combination of get_nfts_by_wallet and then filter results using get_collections_by_wallet to quickly determine which collections are active on multiple chains for a single user.
Debugging Asset Provenance
Someone finds an NFT with weird attributes. They use get_nft_details first, then run get_nft_transfers_by_contract against the contract ID to trace the token back through its entire history and find where it came from.
The Tradeoffs
Treating data like simple lookups
Just asking for 'NFT details' without specifying which wallet or contract. You get partial, unusable data that doesn't show context.
→
Always scope your query. Use get_nft_details by providing the token ID and its unique contract address to guarantee you fetch the correct asset state.
Missing historical context
Only querying a wallet's current holdings using one tool, then assuming that’s all there is. You miss sales and transfers.
→
Always pair your ownership check (get_nfts_by_wallet) with get_nft_transfers_by_wallet to get the full picture—you need both the current state and the history.
Over-reliance on one chain
Writing a query that only targets Ethereum, ignoring other major chains like Polygon or Solana where the asset might live. Your data set is incomplete.
→
Use get_nfts_by_wallet to automatically check multiple chains simultaneously, ensuring you capture assets regardless of their underlying blockchain.
When It Fits, When It Doesn't
Use this server if your workflow needs to map an asset's entire life cycle. This means checking current ownership AND its historical movement (sales/transfers). You need the comprehensive view that combines get_nfts_by_wallet with get_nft_transfers_by_wallet. Don't use it if you only need simple, single-point data retrieval—like just listing all contract IDs. For basic list generation without needing ownership or history context, a simpler indexer might suffice. However, if the question is 'What did this asset do over time?' SimpleHash and its transfer tools are non-negotiable.
Independent Platform Disclaimer: Vinkius is an independent platform and is not affiliated with, endorsed by, sponsored by, verified by, or otherwise authorized by SimpleHash. All third-party trademarks, logos, and brand names are the property of their respective owners. Their use on this website is strictly for informational purposes to identify service compatibility and interoperability.
VINKIUS INFRASTRUCTURE
Cloud Hosted
Managed infra
V8 Isolated
Sandboxed per request
Zero-Trust Proxy
No stored credentials
DLP Enforced
Policy on every call
GDPR Compliant
EU data residency
Token Compression
~60% cost reduction
Works with Claude, ChatGPT, Cursor, and more
The Model Context Protocol standardizes how applications expose capabilities to LLMs. Instead of operating in isolation, your AI gains direct access to external platforms, live data, and real-world actions through secure, standardized connections.
This server provides 7 capabilities that interface natively with Claude, ChatGPT, Cursor, and any MCP client. No middleware. No custom integration required.
Available Capabilities
Tracking assets across multiple blockchains should never feel like running six different API calls.
Right now, checking a wallet's status means opening the Ethereum explorer, then switching tabs to Polygon, maybe copying an address and pasting it into a Solana dashboard. If you want transfer history, you have to run separate queries for every chain, making simple research take twenty minutes of manual clicking and copy-pasting.
With this MCP server, your agent runs one command. It handles the cross-chain logic instantly. You get consolidated results—a unified view of assets across all chains without ever leaving your chat window.
SimpleHash (Multi-chain NFT API) MCP Server: Get a complete asset history.
The manual process involves querying for holdings (`get_nfts_by_wallet`), then running separate queries for every transfer log (`get_nft_transfers_by_wallet`) and collection data (`get_collection_details`). This is slow, prone to error, and requires complex scripting just to stitch the pieces together.
Now, you ask your agent. It orchestrates the necessary calls—getting the current state, then tracing the history, then adding context—and hands you a single, accurate data package. The complexity disappears.
Common Questions About SimpleHash MCP
How do I check all my NFTs on different chains using get_nfts_by_wallet? +
You simply ask your agent to run get_nfts_by_wallet and provide your wallet address. The server automatically checks multiple connected blockchains for you, giving a single, consolidated list of every token you own.
What is the difference between get_nft_details and get_collections_by_wallet? +
get_nft_details gives deep data on one specific NFT (metadata, traits). get_collections_by_wallet only lists which collections a wallet has owned NFTs from—it's a high-level grouping tool.
Can I track the full history using get_nft_transfers_by_contract? +
Yes. get_nft_transfers_by_contract shows every NFT that has moved through a specific smart contract ID, regardless of which wallet owned it. This is useful for tracking project-wide activity.
Do I need to use get_nfts_by_wallet or get_collections_by_wallet? +
It depends on the goal. Use get_nfts_by_wallet if you want a count/list of assets owned by an address. Use get_collections_by_wallet if you just want to know which major IP brands (collections) that address has touched.
When I run `get_nft_details`, what information do I need besides the NFT ID and contract address? +
You must also specify the blockchain network (e.g., Ethereum or Polygon). The tool requires this scope to accurately pull metadata. If you omit the chain, it won't know which version of that NFT data to fetch.
Are there rate limits when using `get_nfts_by_wallet` across multiple chains? +
Yes, while we optimize for high throughput, aggressive querying can trigger throttling. We suggest implementing a small delay (2-3 seconds) between wallet lookups on different chains to maintain reliability.
How do I filter the results of `get_nft_transfers_by_wallet` by date? +
You can refine the transfer history using start and end timestamp parameters. Providing a specific date range cuts down the dataset significantly, making it much faster to process large volumes.
If `get_collection_details` returns an empty list, does that mean the collection is private or non-existent? +
It usually means no assets matching the criteria were found in our index for the requested chain. This doesn't always guarantee the collection isn't real; it just means we couldn't pull data through the API.
How do I check all NFTs owned by a specific wallet address? +
Use the get_nfts_by_wallet tool. You'll need to provide the wallet address and the chains you want to search (e.g., 'ethereum,polygon').
Can I get the floor price of a specific NFT collection? +
Yes! The get_collection_details tool returns comprehensive metadata for a collection, including its current floor price on various marketplaces.
Is it possible to see the history of an NFT's movement? +
Absolutely. You can use get_nft_transfers_by_wallet to see transfers involving a specific user, or get_nft_transfers_by_contract to see all transfers within a specific collection or contract.
Use it with your favorite AI tools
Connect this server to Cursor, Claude, VS Code, and more.
More in this category
SQL Parser AST Engine
Parse any SQL query into a structured AST — extract tables, columns, JOINs, and WHERE clauses programmatically. Supports 15+ dialects including MySQL, PostgreSQL, and BigQuery. Your SQL injection firewall.
Nationalize
Predict the nationality of a person based on their name using the Nationalize.io API.
Svix
Manage your webhook infrastructure via Svix — orchestrate applications, configure endpoints, and monitor message delivery directly from any AI agent.
You might also like
Open-Meteo Weather Forecast
Give your AI agent live weather intelligence: 16-day forecasts, current conditions, and hourly breakdowns for any GPS coordinate on Earth — zero API keys required.
EdApp
Train your workforce with mobile-first microlearning courses, quizzes, and gamified lessons that employees complete on their phones.
Epic Games EOS
Connect to Epic Online Services — lookup accounts, friends, and explore the Epic Games ecosystem.