4,500+ servers built on MCP Fusion
Vinkius

TzKT MCP. Query Tezos State: Accounts, Contracts, Transactions.

Claude Claude
ChatGPT ChatGPT
Cursor Cursor
Gemini Gemini
Windsurf Windsurf
VS Code VS Code
JetBrains JetBrains
Vercel Vercel
See Vinkius in Action

Works with every AI agent you already use

…and any MCP-compatible client

TzKT (Tezos Indexer & Explorer API) MCP on Cursor AI Code Editor MCP Client TzKT (Tezos Indexer & Explorer API) MCP on Claude Desktop App MCP Integration TzKT (Tezos Indexer & Explorer API) MCP on OpenAI Agents SDK MCP Compatible TzKT (Tezos Indexer & Explorer API) MCP on Visual Studio Code MCP Extension Client TzKT (Tezos Indexer & Explorer API) MCP on GitHub Copilot AI Agent MCP Integration TzKT (Tezos Indexer & Explorer API) MCP on Google Gemini AI MCP Integration TzKT (Tezos Indexer & Explorer API) MCP on Lovable AI Development MCP Client TzKT (Tezos Indexer & Explorer API) MCP on Mistral AI Agents MCP Compatible TzKT (Tezos Indexer & Explorer API) MCP on Amazon AWS Bedrock MCP Support

Just plug in your AI agents and start using Vinkius.

TzKT (Tezos Indexer & Explorer API) connects your AI agent directly to the live Tezos blockchain ledger. Use it to query account details, inspect smart contract code (Michelson/Micheline), and trace complex transaction histories across Mainnet and testnets.

It lets you analyze asset holdings, monitor operations by hash, and generate JSON reports on specific addresses without leaving your chat client.

What your AI agents can do

Get account

Fetches detailed information for a single, specified account address.

Get account balance history

Retrieves a chronological list of balance changes for an account over time.

Get account report

Generates a structured JSON report summarizing all activity related to a single account.

+ 22 more capabilities included
Trace Account Activity Flow

Get detailed profiles and full balance change history for any Tezos account using get_account and get_account_balance_history.

Audit Smart Contract Logic

Inspect the underlying contract code (Michelson/Micheline) and list all callable entrypoints or current storage states for a specific KT1 address.

Monitor Asset Transfers

List token transfers, supporting both FA1.2 and FA2 formats, or get granular details on token balances for specified accounts using list_token_transfers.

Generate Financial Reports

Produce structured JSON reports detailing account activity and transaction flows across defined Tezos addresses via get_account_report.

Analyze Network State

Retrieve network-wide statistics like TPS or total volume using get_statistics, or check the current indexer head status with get_head.

Supported MCP Clients

Claude Claude
ChatGPT ChatGPT
Cursor Cursor
Gemini Gemini
Windsurf Windsurf
VS Code VS Code
JetBrains JetBrains
Vercel Vercel
+ other MCP clients
Free for Subscribers

Waiting for input…

AI Agent

TzKT (Tezos Indexer & Explorer API) MCP Server: 25 Tools

Use these tools to query every aspect of the Tezos ledger—from account balances and transaction history to raw contract code and network statistics.

get019e5d63

get account

Fetches detailed information for a single, specified account address.

get019e5d63

get account balance history

Retrieves a chronological list of balance changes for an account over time.

get019e5d63

get account report

Generates a structured JSON report summarizing all activity related to a single account.

get019e5d63

get baker rewards

Retrieves the baker rewards amount calculated for a specific cycle period.

get019e5d63

get block

Gets detailed information about a block, using either its hash or level number.

get019e5d63

get contract code

Fetches the raw Michelson or Micheline code used by a smart contract.

get019e5d63

get contract entrypoints

Lists all available functions (entrypoints) that can be called on a smart contract.

get019e5d63

get contract storage

Retrieves the current or historical key-value storage data for a contract.

get019e5d63

get delegator rewards

Calculates and returns the delegator rewards amount for a given cycle.

get019e5d63

get head

Gets the latest state information, including the indexer's current head block details.

get019e5d63

get operations by hash

Retrieves all operations and data associated with a specific transaction hash.

get019e5d63

get statistics

Pulls network-wide metrics like total transactions per second (TPS) or volume.

list019e5d63

list accounts

Lists multiple accounts, allowing you to filter results by balance, activity level, or account type.

list019e5d63

list bigmap keys

Retrieves all keys stored within a specific big map on the blockchain.

list019e5d63

list bigmap updates

Gets the historical record of updates made to a particular big map.

list019e5d63

list bigmaps

Lists all available 'big maps' accessible on the network.

list019e5d63

list blocks

Retrieves lists of blocks, supporting filters by time range or other criteria.

list019e5d63

list contracts

Lists smart contracts, allowing filtering based on contract creation parameters.

list019e5d63

list delegations

Fetches a list of all recorded delegation operations.

list019e5d63

list originations

Retrieves records detailing how and when contracts were originally created (origination).

list019e5d63

list staking

Lists and summarizes staking-related operations that occurred on the network.

list019e5d63

list token balances

Gets the current token balance for one or more specific accounts.

list019e5d63

list token definitions

Retrieves metadata, standards, and definitions for tokens used on Tezos.

list019e5d63

list token transfers

Lists all token transfer events (both FA1.2 and FA2 formats) between accounts.

list019e5d63

list transactions

Provides a comprehensive list of transactions, with advanced filters for sender, target, or amount.

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
Start building

Make Your AI Do More

Start with TzKT (Tezos Indexer & Explorer 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

Listen up. The TzKT Tezos Indexer API hooks your agent right into the live Tezos blockchain ledger. You're talking deep reads here—we’re talking everything from raw block headers to complex smart contract storage, and you can analyze it all without leaving your chat client.

Tracing Account Activity Flow. If you wanna know what happened with an account, you got a couple of tools for that. Use get_account to pull detailed information on any specific account address. To see the full money trail, run get_account_balance_history; it gives you a chronological list of every balance change over time.

You can summarize everything into a neat JSON report using get_account_report. If you're just trying to get a snapshot of what accounts are floating around, use list_accounts, and you can filter those results by activity level or account type.

Monitoring Asset Transfers. Wanna track tokens? You've got options. Use list_token_transfers to list every token transfer event—it handles both the old FA1.2 format and the newer FA2 format, so you don't lose anything. For a specific account, use list_token_balances to get its current token balance, or if you need metadata on what tokens are even floating around, check out list_token_definitions.

You can also get a list of all available 'big maps' with list_bigmaps, and track changes by running list_bigmap_updates for any specific big map key.

Auditing Smart Contract Logic. Need to poke at some smart contract code? You got this. Use get_contract_code to fetch the raw Michelson or Micheline code used by a contract, and get_contract_entrypoints lists every function—every entrypoint—that can actually be called on that contract. If you want to know what data it's keeping track of internally, use get_contract_storage to grab the current or historical key-value storage for a contract.

You can also look at how contracts were first created using list_originations, and get a list of all existing smart contracts via list_contracts, letting you filter by creation parameters.

Analyzing Network State. Want to know what's going on network-wide? Use get_statistics to pull metrics like total transactions per second (TPS) or the overall volume. To check the latest indexer status, hit up get_head. You can also get a detailed breakdown of any single block using get_block, specifying it by either its hash or level number.

If you're digging into specific transactions, get_operations_by_hash retrieves all operations and data tied to that transaction hash. To see everything that moved around the network in terms of staking, run list_staking. You can also get a list of all recorded delegation operations using list_delegations, or view every single operation by listing all transactions with list_transactions, where you can filter results based on sender, target, or amount.

Deep Dive Data Retrieval. If you're dealing with core ledger data, use get_baker_rewards to get the reward amount calculated for a specific cycle period, or calculate delegator payouts using get_delegator_rewards. You can list all recorded account creations and monitoring staking operations by running list_deposits and list_originations, respectively. Finally, if you just want a broad overview of what's happening with the ledger, you can run get_head to get the indexer’s current head block details.

How TzKT MCP Works

  1. 1 Subscribe to this server. You'll connect it via your preferred AI client (Claude, Cursor, etc.).
  2. 2 (Optional) Input your TzKT API Key if you need higher rate limits for heavy querying.
  3. 3 Ask your agent to perform a specific query, like 'list all transactions involving address X', and the tool runs the necessary lookup against the Tezos ledger.

The bottom line is that it turns complex blockchain calls into simple chat commands, letting you read live state data directly from your AI client.

Who Is TzKT MCP For?

Any developer or analyst who needs to move beyond basic block explorer views. If you're stuck clicking through multiple tabs—one for transactions, one for contract code, another for balances—you need this. It brings all that raw on-chain data directly into your workflow.

Web3 Developer

Debugging smart contracts or verifying storage states. You use get_contract_code and get_account_report to confirm a contract behaves as expected.

Blockchain Data Analyst

Extracting historical balance data and transaction flows for multiple Tezos accounts. You rely heavily on list_transactions and get_account_balance_history.

DeFi Auditor

Monitoring wallet activity or tracing asset movements across specific operations. You use tools like list_token_transfers to confirm ownership paths.

What Changes When You Connect

  • Pinpoint every asset movement by running list_token_transfers to track both FA1.2 and FA2 transfers across the ledger.
  • Get a complete financial picture of an address using get_account_report, which bundles balance history and activity into one JSON output.
  • Debug smart contract behavior immediately. Use get_contract_code to pull the raw Michelson/Micheline code, and then check state via get_contract_storage.
  • Analyze network health on demand. Call get_statistics for real-time metrics (like TPS) or use list_blocks to review historical block data by specific filters.
  • Track complex ownership paths using the combined power of list_token_transfers and list_accounts, making it easy to audit asset flow without leaving your chat interface.

Real-World Use Cases

01

Auditing an Investment Pool

A DeFi auditor needs to confirm every movement of a pooled asset. Instead of cross-referencing multiple block explorer tabs, the agent runs list_transactions filtered by the pool's contract address, then uses get_operations_by_hash on key transactions to verify all associated actions.

02

Debugging a New Contract

A developer wrote a new smart contract that isn't storing data correctly. They first run get_contract_code to check the logic, then call list_bigmaps and examine specific keys using list_bigmap_keys to isolate where the state change failed.

03

Tracking an Individual User's Wealth

A data analyst needs a full picture of one wallet. They start by running get_account for the address, then follow up with get_account_balance_history and finally list_token_transfers to build a complete financial timeline.

04

Checking Network Capacity

A product manager needs to report on recent network usage. They ask the agent for network statistics, triggering get_statistics, which provides current TPS and volume data instantly, perfect for reports or dashboards.

The Tradeoffs

Assuming a single call gets everything.

Asking 'What happened with this contract?' and expecting one tool to return the code, storage, and history. It won't work; data is separated by function.

You need a phased approach. First, use get_contract_entrypoints to see what functions exist. Then, run get_contract_storage for the current state. Finally, check historical activity using list_transactions filtered against that contract's address.

Over-relying on simple listing tools.

Just running list_contracts and getting a list of addresses isn't enough. You need to know if the contract is even doing anything useful right now.

Always cross-reference the listed contracts with get_contract_storage. This tells you if the contract has any active, stored data that needs inspection.

Confusing token types.

Assuming all transfers are standard. You might miss transactions because some tokens use different transfer protocols (FA1.2 vs FA2).

Use list_token_transfers specifically, as this tool handles the differences between both major token transfer formats.

When It Fits, When It Doesn't

Use this server if your task involves reading specific state changes from the Tezos blockchain ledger. If you need to trace asset flow, check contract code, or pull historical account data, this is necessary. Don't use it if you just need a simple list of addresses—list_accounts works fine for that. But if you need why an address has a certain balance (i.e., the history), you must combine get_account_balance_history with list_token_transfers. If your goal is simply to write new contract code, this tool only reads data; you'll still need a separate environment for writing and compiling.

Independent Platform Disclaimer: Vinkius is an independent platform and is not affiliated with, endorsed by, sponsored by, verified by, or otherwise authorized by TzKT. 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

How we secure it →

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 25 capabilities that interface natively with Claude, ChatGPT, Cursor, and any MCP client. No middleware. No custom integration required.

Available Capabilities

get_account get_account_balance_history get_account_report get_baker_rewards get_block get_contract_code get_contract_entrypoints get_contract_storage get_delegator_rewards get_head get_operations_by_hash get_statistics list_accounts list_bigmap_keys list_bigmap_updates list_bigmaps list_blocks list_contracts list_delegations list_originations list_staking list_token_balances list_token_definitions list_token_transfers list_transactions

Tracking asset ownership shouldn't involve jumping between four different tabs.

Today, tracking an account’s full history means opening the main block explorer. You click to see transactions (`list_transactions`), then you have to open a second tab to check the contract code (`get_contract_code`), and a third just to get current balances (`list_token_balances`). Then, if you need historical data, you're stuck digging through raw blocks.

With this MCP server, your agent handles it all. You ask for an account report, and the system runs multiple lookups behind the scenes—combining `get_account`, `list_transactions`, and `list_token_transfers` into one clean JSON output. You just get the answer.

The TzKT MCP Server: Get full contract state and history.

Manually, checking a smart contract's functionality requires querying its entrypoints (`get_contract_entrypoints`) to see what it *can* do. Then you have to check the `list_bigmaps` to see if anyone has actually written data to it.

Now, your agent handles that sequence for you. You ask about a contract, and the server checks its callable functions while also retrieving its current storage state via `get_contract_storage`. It’s a complete audit in two lines of chat.

Common Questions About TzKT MCP

How do I find out what tokens an account holds? +

Use the list_token_balances tool. This function retrieves the current token balance for specific accounts, providing clearer data than general transaction listings alone.

What is the difference between `list_transactions` and `get_operations_by_hash`? +

list_transactions gives you a broad list of operations across many hashes. Use get_operations_by_hash when you know the exact transaction hash and need all associated data for that single operation.

Can I see how much reward was earned by stakers? +

Yes, use the dedicated functions like list_staking or get_delegator_rewards. These tools calculate and report specific rewards based on delegation cycles.

Do I need to know Michelson vs Micheline code for debugging? +

The tool handles it. Use get_contract_code and it will return the contract's underlying language (Michelson or Micheline) so you can debug based on what was deployed.

If I run a large query using `list_transactions`, how do I handle rate limits? +

You must enter your TzKT API Key to increase the rate limit. Without it, repeated queries will hit default restrictions and fail. The key allows your agent to send more requests in a shorter time frame.

When I use `list_accounts`, does the network I query affect the results? +

Yes, you must specify which blockchain network you are targeting (Mainnet, Ghostnet, or Shadownet). Running a list command without defining the network will result in an error because the data is isolated by chain.

What should I do if `get_operations_by_hash` fails because the hash doesn't exist? +

The API returns a specific error code indicating no matching operation was found. You can then adjust your query or confirm the transaction hash with other sources.

How do I filter results when using `list_contracts` beyond just name? +

You pass advanced parameters like contract type, minimum balance, or creation date into the function call. This narrows down millions of entries to only the relevant subset you need.

Can I see how an account's balance has changed over time? +

Yes! Use the get_account_balance_history tool with the account address. It will return a historical record of balance changes for that specific Tezos address.

How do I check the current state or storage of a smart contract? +

You can use the get_contract_storage tool by providing the contract's KT1 address. This will retrieve the current data stored in the contract's state.

Is it possible to list transactions for a specific sender or target? +

Absolutely. Use the list_transactions tool and apply filters like sender or target to narrow down the results to specific addresses or interaction flows.

More in this category

You might also like

Built & Managed by Vinkius 30s setup 25 tools

We've already built the connector for TzKT. Just plug in your AI agents and start using Vinkius.

No hosting. No infrastructure. No complex setup.
All 25 tools are live and waiting. You're up and running in seconds.

Claude Claude
ChatGPT ChatGPT
Cursor Cursor
Gemini Gemini
Windsurf Windsurf
VS Code VS Code
JetBrains JetBrains
Vercel Vercel
+ other MCP clients

Vinkius gives your AI agents access to the full catalog of app connectors, all fully managed, secure, and enterprise-ready. One subscription, every tool you need.

Zero hosting required Full MCP catalog included Enterprise-grade security Auto-updated by Vinkius

Built, hosted, and secured by Vinkius. You just connect and go.