BTC.com API MCP. Debug Bitcoin addresses and monitor mining performance.
Works with every AI agent you already use
…and any MCP-compatible client
Just plug in your AI agents and start using Vinkius.
BTC.com API (BTC.com Explorer & Pool API) gives you direct access to real-time Bitcoin blockchain data and mining pool statistics.
You can query specific blocks, trace any address's full transaction history, and monitor your mining account's hashrate and worker performance.
It's a dual-purpose tool for both public blockchain research and private mining operations.
What your AI agents can do
Get account stats
Retrieves your mining pool account hashrate and performance statistics (requires an access key).
Get address summary
Gets a quick overview of a Bitcoin address's current balance and transaction count.
Get address transactions
Fetches the full record of every transaction ever associated with a given address.
Retrieves the current balance, transaction count, and overall summary data for a specified Bitcoin address.
Fetches the complete list and details of all recorded transactions associated with a specific Bitcoin address.
Determines the current set of unspent transaction outputs (UTXOs) for a Bitcoin address, critical for validating spending capacity.
Retrieves detailed information about a specific block, either by its unique hash or its sequential height.
Accesses statistics like account hashrate (15m, 24h) and payment history for your mining pool account.
Lists all connected mining workers and provides detailed operational statistics for individual units.
Ask AI about this MCP
Supported MCP Clients
Waiting for input…
BTC.com API MCP Server: 13 Tools for Crypto Data
Use these tools to query Bitcoin block data, trace address movements, and monitor mining hardware performance via your agent.
019e5d03get account stats
Retrieves your mining pool account hashrate and performance statistics (requires an access key).
019e5d03get address summary
Gets a quick overview of a Bitcoin address's current balance and transaction count.
019e5d03get address transactions
Fetches the full record of every transaction ever associated with a given address.
019e5d03get address utxo
Determines the current unspent transaction outputs for a specific address.
019e5d03get block
Retrieves comprehensive information about a block, using either its unique hash or block height.
019e5d03get block transactions
Gets all the transactions that were included in a specific block.
019e5d03get hashrate history
Retrieves historical data showing how your mining pool's hashrate has changed over time (requires an access key).
019e5d03get latest block
Gets the most recently mined block's information from the Bitcoin network.
019e5d03get payment history
Retrieves a record of payment transactions and account statistics for the mining pool (requires an access key).
019e5d03get transaction
Retrieves all specific details about a single transaction using its unique hash.
019e5d03get unconfirmed transactions
Checks the mempool for transactions that have been broadcast but not yet included in a block.
019e5d03get worker list
Lists all connected mining workers and their current status (requires an access key).
019e5d03get worker stats
Provides detailed operational statistics for individual mining workers (requires an access key).
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 BTC.com API (BTC.com Explorer & Pool 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
Yo, this BTC.com API gives your agent straight-up access to all the Bitcoin blockchain and mining pool data you need. You can track everything from specific transactions to your own rig's performance, all without leaving your coding environment.
To check the big picture, you can get the most recent block with get_latest_block, or you can pull comprehensive data on any block using get_block (it takes a hash or height). You can also see all the transactions that went into that block by running get_block_transactions. For transactions that haven't landed yet, you can check the mempool with get_unconfirmed_transactions.
When you're digging into an address, you can run get_address_summary to get a quick read on its balance and total transaction count. If you need to know exactly what money's sitting there, get_address_utxo shows you the current unspent transaction outputs. And if you gotta see the whole story, you can fetch every single transaction ever linked to an address using get_address_transactions.
You can also check the details for a single transaction using its hash with get_transaction.
For the mining side, you can manage your pool's health. You't gonna need to eyeball numbers on a website; you can pull your account's hashrate and performance stats (15m and 24h) with get_account_stats and check your payment history with get_payment_history. You can also track how your pool's hashrate changes over time by checking the history with get_hashrate_history.
To manage your workers, you can list every connected worker and see their status with get_worker_list, and you can get detailed operational stats for each individual unit using get_worker_stats.
How BTC.com API MCP Works
- 1 First, subscribe to the server and (if needed) enter your BTC.com Access Key to enable pool-specific tools.
- 2 Next, instruct your AI client to run a query, specifying the action (e.g., 'Show the balance for X' or 'List active workers').
- 3 The server executes the necessary tool calls and returns structured, real-time data that your agent can interpret and use.
The bottom line is that your agent handles all the complex API calls, so you just ask the question in plain language.
Who Is BTC.com API MCP For?
This server is for crypto developers, quantitative analysts, and mining operations managers. If your job involves verifying fund movements, tracking network health, or building financial tools around Bitcoin, you need this. It lets you debug addresses and monitor farm performance without ever leaving your IDE.
Verifies transaction inputs and outputs, or debugs complex address balances directly within the code editor.
Monitors farm health, checks hashrate stability, and identifies underperforming workers using natural language queries.
Extracts real-time blockchain metrics, block metadata, and payment history for research, reporting, and quantitative modeling.
What Changes When You Connect
- See an address's full financial picture. Instead of visiting a web explorer, use
get_address_summaryfor a quick balance check, and thenget_address_transactionsto pull the full, verifiable history. - Track your mining operation's performance in real-time. Use
get_account_statsto check your current hashrate andget_hashrate_historyto identify performance drops over the last 24 hours. - Debug specific transactions. If a payment fails, run
get_transactionwith the hash. This gives you the raw details—the inputs, outputs, and metadata—you need to know what went wrong. - Know the network's current state. Use
get_latest_blockto get the latest block's info, orget_unconfirmed_transactionsto see what’s sitting in the mempool waiting to be confirmed. - Manage your farm remotely. Use
get_worker_listto get a roster of all workers, then runget_worker_statson a specific unit to check its current hash rate. - Cross-reference data points. Use
get_address_utxoto find all unspent funds, then useget_block_transactionsto see which block those funds were originally spent from.
Real-World Use Cases
Diagnosing a Failed Payment
A developer needs to know why a client payment failed. They start by running get_address_summary to confirm the receiving address is valid. Next, they use get_transaction on the payment hash to pull the full details. Finally, they run get_block_transactions on the block containing the transaction to check for any network-level rejection codes, solving the issue in minutes.
Building a Network Health Dashboard
An analyst wants a real-time dashboard. They use get_latest_block to get the current block height. They then call get_unconfirmed_transactions to quantify network congestion. If the volume is high, they use get_block_transactions to analyze the transaction types being prioritized.
Auditing a Mining Pool's Performance
A manager suspects poor performance. They first run get_worker_list to identify all units. They then use get_worker_stats on the suspect worker. If the stats look fine, they cross-reference the period with get_hashrate_history to prove a dip in performance at a specific time.
Tracking Large Fund Movements
A data analyst tracks a major fund movement. They start with get_address_summary to identify the source address. They use get_address_transactions to find the relevant outgoing transaction hash, then use get_transaction to analyze the inputs and outputs, mapping the fund's journey.
The Tradeoffs
Mixing up API calls
Trying to guess the right sequence of API calls to track a fund, leading to incomplete data or missing the root cause. For example, only calling get_address_summary and assuming the balance is accurate without checking the underlying get_address_utxo.
→
Always start with the summary tools (get_address_summary) for triage. If you need to validate the exact spendable amount, use get_address_utxo. This structured approach ensures you don't miss the actual mechanics of the funds.
Ignoring time context
Looking at a single transaction hash using get_transaction and concluding a failure, without checking the surrounding block data. The problem might be a network congestion issue that only get_block or get_block_transactions can reveal.
→
If you see an anomaly in a transaction, always check the surrounding block data. Use get_block_transactions and get_block to understand the context and confirm if the transaction was processed correctly within the block.
Manual data aggregation
Copying transaction hashes from a web explorer into a spreadsheet and manually running them through different API endpoints, which is slow and prone to human error.
→
Let your agent handle the orchestration. Feed your agent the target address, and it will automatically run get_address_transactions and then feed those hashes into get_transaction to build the full report automatically.
When It Fits, When It Doesn't
Use this server if you need to understand the mechanism of Bitcoin funds or mining operations. You need to know why a transaction failed, not just that it failed. For example, if you need to track a fund's history, start with get_address_summary and drill down using get_address_transactions. If your focus is strictly on the technical performance of your mining hardware, stick to the pool tools (get_account_stats, get_worker_stats). Don't use this if you just need a simple price feed—use a dedicated exchange API instead. If you only need to check the latest block height, get_latest_block works, but for full context, always follow up with get_block_transactions.
Independent Platform Disclaimer: Vinkius is an independent platform and is not affiliated with, endorsed by, sponsored by, verified by, or otherwise authorized by BTC.com. 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 13 capabilities that interface natively with Claude, ChatGPT, Cursor, and any MCP client. No middleware. No custom integration required.
Available Capabilities
Manually tracking fund movements is a nightmare.
Right now, tracking a single fund movement means jumping between three different websites: the block explorer for the hash, the address tracker for the balance, and a separate dashboard for pool metrics. You copy the hash, you open a new tab, you wait for the page to load, and you copy the data into a spreadsheet. It’s slow, and half the data is always missing.
With this MCP server, your agent does the legwork. You tell it, 'Show me the full history and status of this address.' It automatically runs `get_address_transactions` and `get_address_summary` in the background, stitching together the full, verifiable financial story and giving you a clean output.
BTC.com API MCP Server: Monitor Mining Performance
Before, checking your farm health required logging into the pool dashboard, finding the worker list, and manually querying hashrates for every unit. If you missed a single worker, your report was wrong. You were always working with stale data.
Now, your agent executes `get_worker_list` and `get_worker_stats` in sequence. You get the current, reliable metrics for every worker, instantly. The data is clean, structured, and ready for immediate analysis.
Common Questions About BTC.com API MCP
How do I check the balance of a Bitcoin address using get_address_summary? +
Use get_address_summary and provide the target address. The tool returns the current total balance and the total number of transactions associated with that address.
Can get_address_transactions show me the full history of a Bitcoin address? +
Yes, get_address_transactions retrieves the complete list of all transactions associated with that address, giving you a full audit trail of its activity.
What is the difference between get_transaction and get_block_transactions? +
Use get_transaction for details on a single, specific transaction hash. Use get_block_transactions to get a list of every transaction that was included in an entire block.
How do I check my mining pool's hashrate history using get_hashrate_history? +
Run get_hashrate_history and provide the necessary time range. This tool returns historical data, allowing you to plot performance dips or steady growth over time.
What does get_unconfirmed_transactions show me? +
get_unconfirmed_transactions checks the mempool and shows transactions that have been broadcast to the network but have not yet been included in a confirmed block.
How do I list all my mining workers and check their status using get_worker_list and get_worker_stats? +
You use get_worker_list first to get all worker identifiers. Then, you call get_worker_stats for each worker ID to get its current hashrate and status. This two-step process lets you confirm if units are active or dead.
Does `get_address_utxo` only retrieve the current balance, or does it show historical data? +
It retrieves the unspent transaction outputs (UTXO) for an address, which is the current, usable balance. It doesn't show historical data; for that, you'll need to use get_address_transactions.
What happens if I query a block hash or height that doesn't exist using `get_block`? +
The API returns a clear error message indicating that the requested block hash or height was not found. This lets your agent handle the failure gracefully and retry with correct parameters.
Can I check the balance of a specific Bitcoin address without an API key? +
Yes. Explorer tools like get_address_summary and get_address_transactions are public and do not require a BTC_COM_ACCESS_KEY.
How do I monitor the status of my mining workers? +
You can use get_worker_list to see all workers and their status (Active/Inactive/Dead), or get_worker_stats with a specific Worker ID for detailed metrics.
Does this server support unconfirmed transactions? +
Yes, the get_unconfirmed_transactions tool allows you to fetch a list of transactions currently in the Bitcoin mempool.
Use it with your favorite AI tools
Connect this server to Cursor, Claude, VS Code, and more.
More in this category
String Metrics Analyzer
Bypass LLM tokenization blindness. Get exact character counts, word counts, and specific string occurrences deterministically.
Dextools (DeFi Token Data API)
Access real-time DeFi market data, token prices, liquidity pairs, and blockchain information across multiple networks via Dextools.
GoatCounter
Privacy-friendly web analytics — track pageviews, analyze visitor stats, and manage your sites directly through any AI agent.
You might also like
Traefik Hub
Cloud-native API Management & Gateway evaluating proxy topologies explicitly running Kubernetes integrations.
Akeneo PIM
Product Information Management orchestration — manage products, attributes, and categories via AI.
Webex
Manage rooms, meetings, and collaboration workflows on Cisco Webex — the leading enterprise video conferencing platform.