OKLink MCP. Trace token flows & analyze multi-chain data.
Works with every AI agent you already use
…and any MCP-compatible client
Just plug in your AI agents and start using Vinkius.
OKLink Multi-chain Web3 Blockchain Data API connects your AI agent to real-time blockchain data across dozens of networks like Bitcoin, Ethereum, and BSC.
You can query everything: get a wallet summary, trace full transaction histories, list all tokens on a chain, or check the latest block details instantly.
It gives your agent instant access to structured on-chain intelligence without manual explorer searching.
What your AI agents can do
Get address summary
Pulls a high-level summary (balance, total transactions) for any given blockchain address.
Get address transactions
Lists all historical and current transactions linked to a specific blockchain address.
Get block detail
Retrieves detailed information about any specified block hash on the chain.
Get an address summary that includes current balances, total transaction counts, and general activity metrics.
Pull a full, chronological list of every transaction associated with a specific wallet or contract address.
Retrieve the latest block details for any supported blockchain network.
Get detailed token metrics, check specific token balances at an address, or list all tokens available on a chain.
Inspect granular information about any given block hash, including its timestamp and miner details.
Analyze a single transaction hash to see its status, gas cost, sender, and recipient addresses.
Ask AI about this MCP
Supported MCP Clients
Waiting for input…
OKLink (Multi-chain Web3 Blockchain Data API): 12 Tools
These twelve specialized tools let your AI client programmatically analyze blockchain activity. You can trace funds, check balances, and inspect data across dozens of major crypto networks.
019e5d3dget address summary
Pulls a high-level summary (balance, total transactions) for any given blockchain address.
019e5d3dget address transactions
Lists all historical and current transactions linked to a specific blockchain address.
019e5d3dget block detail
Retrieves detailed information about any specified block hash on the chain.
019e5d3dget block transactions
Gets a list of all transaction hashes that were included within a specific block.
019e5d3dget chain info
Provides detailed metadata about a particular supported blockchain network.
019e5d3dget latest block
Fetches the most recently mined block data for any specified chain.
019e5d3dget nft collection info
Retrieves metadata and details about a specific NFT collection contract.
019e5d3dget supported chains
Returns a list and summary of all blockchains currently supported by the server.
019e5d3dget token balance
Checks the balance amount for a specific token held at an address.
019e5d3dget token detail
Gets detailed information, including contract and metrics, for any specified token type.
019e5d3dget token list
Retrieves a list of all available tokens on a specific blockchain network.
019e5d3dget transaction detail
Provides the full payload and status details for a single, specified transaction hash.
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 OKLink (Multi-chain Web3 Blockchain Data 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
This server connects your AI client directly to real-time blockchain data across dozens of networks, including Ethereum, Bitcoin, and BSC. It gives your agent the full ability to query structured on-chain intelligence without needing a manual explorer search.
To start, you'll use get_supported_chains to check exactly which blockchains we can access; that’s always good to know first. You can then grab general metadata about any supported network using get_chain_info.
Tracking Addresses and Accounts
If you need a quick read on an address, you've got two options: run get_address_summary for a high-level overview that gives you the current balance, total transactions count, and general activity metrics. For a deep dive, use get_address_transactions; this pulls a full, chronological list of every single transaction ever linked to that specific wallet or contract address.
Analyzing Tokens and Assets
The token tools let your agent investigate asset movements thoroughly. To see which tokens exist on a chain, you run get_token_list. You can then get detailed metrics—like the contract and full specs—for any type of token using get_token_detail. If you want to know how much of a specific token an address holds, you'll use get_token_balance.
For NFTs, if you know the collection contract, run get_nft_collection_info; this pulls all the metadata and details about that particular NFT set.
Inspecting Blocks and Transactions
When it comes to block data, your agent can check for the most recent activity by using get_latest_block on any supported chain. If you need granular specifics, running get_block_detail retrieves detailed information about a specific block hash, including its timestamp and who mined it. To see every transaction that made it into a block, use get_block_transactions, which gives you a list of all the associated transaction hashes.
Finally, if your agent finds a specific transaction hash, it can analyze the whole thing using get_transaction_detail. This function provides the full payload and status details for that single transaction, letting you see the gas cost, who sent it, and where it went. You'll also find that getting all historical or current transactions linked to an address is handled by get_address_transactions.
This suite of tools lets your AI client analyze everything from general wallet activity using get_address_summary, to tracing the full life cycle of a single token with get_token_balance, making it the definitive source for on-chain intelligence.
How OKLink MCP Works
- 1 Subscribe to this server and provide your OKLink API Key (Access Key).
- 2 Instruct your AI agent to call a specific function, passing required parameters like an address or chain ID.
- 3 The tool executes the on-chain query and returns clean, structured data directly back to your client.
The bottom line is you get structured, multi-chain blockchain data instantly without writing boilerplate API calls yourself.
Who Is OKLink MCP For?
This server is for developer tools and quantitative analysts who need to read on-chain data fast. Think of the smart contract auditor who has to check 20 different chains or the DeFi researcher needing to trace funds across multiple tokens. It's built for speed over general usability.
Uses this API to build agent logic that pulls live data, like calling get_address_transactions to populate a user dashboard.
Runs complex queries, using get_token_detail combined with get_address_summary, to monitor asset movements across several chains simultaneously.
Tests contract logic by fetching specific block details or analyzing transaction payloads using get_transaction_detail on a test network.
What Changes When You Connect
- Analyze Addresses: Use
get_address_summaryto instantly see a wallet's total activity and balance without querying transaction lists first. It saves multiple steps on the data pipeline. - Track Full History: Instead of just seeing the latest block, use
get_block_transactionsto pull every hash in that block, then runget_transaction_detailon each one for a complete picture. - Token Visibility: The combination of
get_token_listandget_token_balancelets you programmatically know what assets exist on a chain and how much an address holds of them. No more guessing the asset type. - Multi-Chain Scope: By calling
get_supported_chains, your agent knows exactly which chains it can query, making the system robust enough for any cross-chain analysis task you throw at it. - NFT Specifics: Use
get_nft_collection_infoto pull metadata on specific collections. This is critical when building tools that track digital asset ownership and provenance.
Real-World Use Cases
Auditing a Smart Contract's Funds
A developer needs to know if a contract address (0x...) was funded by specific tokens. They first call get_token_list for the chain, then use get_address_summary on the contract to confirm balances, and finally run get_transaction_detail using recent transaction hashes to trace the exact inflow event.
Monitoring a New Protocol Launch
A quant wants to know which chains are active. They start by calling get_supported_chains. Once they target Polygon, they use get_latest_block to see the current activity height and then run get_block_transactions to spot suspicious or unusual transaction patterns.
Verifying an NFT Sale
A user wants proof of purchase for a rare digital asset. They first call get_nft_collection_info for the collection, then use get_address_transactions on their own wallet to pull the sale transaction hash, and finally run get_transaction_detail to confirm the transfer details.
Debugging Token Ownership
A user suspects an address has tokens that aren't showing up. They call get_token_list for the relevant chain, identify the missing token contract, and then use get_token_balance to confirm if the balance exists at all.
The Tradeoffs
Treating it like a simple API call
Trying to fetch everything with one massive query, resulting in an incomplete or rate-limited response. You'll miss the specific details you need.
→
Break down the task into steps: First, use get_address_summary for quick stats. Then, if needed, call get_address_transactions to get hashes. Finally, feed those limited hashes into get_transaction_detail for the full picture.
Overlooking the chain context
Running a token query without specifying the correct network ID. The agent pulls generic data that doesn't match the assets you actually care about.
→
Always start by checking get_supported_chains to confirm the required network, then use get_token_list and pass the chain context with every subsequent call.
Assuming a tool does everything
Thinking that calling get_address_summary will also give you the token breakdown. It won't; it only gives general balance info.
→
If you need specific asset details, use two tools: first get_token_list to find the contract, and then get_token_balance using that contract ID.
When It Fits, When It Doesn't
Use this server if your goal is deep data tracing or cross-chain analysis. Specifically, if you need to answer 'How did X get from Y to Z?' You must use tools like get_transaction_detail and get_address_transactions. Don't use it if all you need is a simple public block explorer view—those are fine for quick checks. However, don't rely only on get_latest_block; always follow up with get_block_transactions to get the actual data payloads inside that block. If you just want general marketing metrics about the blockchain ecosystem, look at dedicated reporting APIs instead; this toolset is purely operational data access.
Independent Platform Disclaimer: Vinkius is an independent platform and is not affiliated with, endorsed by, sponsored by, verified by, or otherwise authorized by OKLink. 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 12 capabilities that interface natively with Claude, ChatGPT, Cursor, and any MCP client. No middleware. No custom integration required.
Available Capabilities
Tracking funds across multiple chains shouldn't require context switching.
Today, tracking a single asset movement often means opening the Ethereum explorer, copying an address, going to the Polygon explorer, and repeating that process for every chain involved. You spend more time clicking tabs and formatting data than actually analyzing it.
With this MCP server, your agent handles all of it. Give it the source and destination addresses; it runs `get_address_summary` across multiple chains and returns a unified report. You stop managing interfaces and start drawing conclusions.
The OKLink Multi-chain Web3 Blockchain Data API MCP Server gives you full visibility.
Manual tracing requires pulling block data, then listing transactions for that block (`get_block_transactions`), and finally getting the detailed payload of each transaction using `get_transaction_detail`. It’s a three-step manual process with tons of copy/pasting.
Now, your agent manages the sequence. You ask it to trace funds, and it executes all those steps automatically in the background, returning one cohesive report. The complexity is abstracted away.
Common Questions About OKLink MCP
How do I get a full history of an address using get_address_transactions? +
Calling get_address_transactions pulls all historical transaction hashes for that address. You can then pass those hashes into get_transaction_detail to see the payload and status of each one.
What is the difference between get_latest_block and get_block_detail? +
get_latest_block only retrieves the most recent block's metadata. Use get_block_detail when you already know a specific hash and need to inspect all its contents, like timestamps or miner details.
Can I check token balances for multiple networks with get_token_balance? +
You must specify the network context in your prompt. While get_supported_chains lists available networks, you need to run get_token_balance separately for each chain and token type.
Do I need get_nft_collection_info for every NFT asset? +
Yes, if you want collection metadata (like the contract or total supply), use get_nft_collection_info. This provides context beyond just checking the ownership record.
What credentials do I need to use the `get_address_summary` tool? +
You must provide your unique OKLink API Key when connecting the MCP Server. This key authorizes every single call, so make sure you store it securely within your client environment.
If I pass an invalid hash to `get_transaction_detail`, what error will my agent receive? +
The server returns a clear 'Not Found' status. This tells your AI client immediately that the specific transaction ID doesn't exist on any supported chain, saving you guesswork.
Are there rate limits when using the `get_token_list` tool across multiple chains? +
Yes, standard API rate limits apply. If your agent makes too many calls in quick succession, it will hit a 429 error. It's best to space out large batches of token lookups.
When I use `get_chain_info`, what core metadata can I retrieve about a blockchain? +
You get the chain’s name, native currency symbol, and total supply details. This helps your agent validate if the network is fully active or limited in scope.
How do I check the balance of a specific wallet address? +
You can use the get_address_summary tool by providing the chain name (e.g., 'eth') and the address. For a detailed list of all token holdings, use the get_token_balance tool.
Can I retrieve information about NFT collections? +
Yes! Use the get_nft_collection_info tool with the chain name and the NFT contract address to fetch metadata and collection details.
How do I find the latest block on a specific blockchain? +
Simply use the get_latest_block tool and specify the chain (e.g., 'btc', 'eth', 'polygon'). It will return the height and details of the most recently mined block.
Use it with your favorite AI tools
Connect this server to Cursor, Claude, VS Code, and more.
More in this category
IPRoyal (Proxy Services)
Manage proxies via IPRoyal — monitor traffic, rotate credentials, and manage whitelisted IPs.
Phone Validator Engine
Stop LLMs from hallucinating phone numbers. Validates and formats numbers to E.164 natively.
Zippopotam.us Alternative
Free geocoding and postal code lookup — retrieve city, state, and coordinates for any zip code or find postal codes by city.
You might also like
Neon
Manage serverless PostgreSQL databases via Neon — provision projects, branches, endpoints and roles from any AI agent.
GoHighLevel Alternative
Manage your GHL location — audit contacts, opportunities, and tasks via AI.
Aliyun API Market / 阿里云云市场
China's largest API marketplace — access thousands of 3rd-party OCR, SMS, and data services via AI.