BTC.com API MCP for AI. Track Bitcoin State and Mining Performance
Works with every AI agent you already use
…and any MCP-compatible client








Connect to your AI in seconds.
BTC.com API provides a single connection point for deep Bitcoin blockchain analysis. It lets your agent read real-time data on everything from block heights and specific transactions to an address's entire history.
Plus, it monitors mining pool health, giving you current hashrate metrics and worker performance stats.
What your AI can do
Get account stats
Retrieves the current hashrate and performance statistics for your mining account.
Get address summary
Provides a quick overview of an address's total balance and transaction count.
Get address transactions
Fetches the full list of transactions associated with a specific Bitcoin address.
You pull detailed information about any specific block using its hash or height.
You fetch a complete record of all transactions and current balances for any Bitcoin address.
You retrieve real-time stats like hashrate, worker status, and historical performance records from your pool account.
You review pending transactions sitting in the mempool before they are included in a block.
Ask an AI about this
Waiting for input…
BTC.com API (BTC.com Explorer & Pool API) with 13 Tools
Use these tools to pull everything from the Bitcoin network: read blocks, track addresses, analyze transactions, and monitor your entire mining pool's performance.
Make your AI actually useful.
Add this MCP to Claude, Cursor, or Windsurf and your AI stops guessing. It gets real tools to look things up, take action, and handle the stuff you keep doing by hand.
Start using BTC.com API (BTC.com Explorer & Pool API) on VinkiusGet Account Stats
Retrieves the current hashrate and performance statistics for your mining account.
Get Address Summary
Provides a quick overview of an address's total balance and transaction count.
Get Address Transactions
Fetches the full list of transactions associated with a specific Bitcoin address.
Get Address Utxo
Identifies and retrieves all unspent transaction outputs (UTXOs) for an account.
Get Block
Gathers detailed information about a Bitcoin block using either its unique hash or...
Get Block Transactions
Lists all the transactions contained within a specific, identified block.
Get Hashrate History
Retrieves historical data points showing how your mining hashrate has changed over time.
Get Latest Block
Gets the most recent block information from the Bitcoin network instantly.
Get Payment History
Pulls a record of past payments and financial statistics linked to your account.
Get Transaction
Retrieves the full details for any specific Bitcoin transaction, including inputs...
Get Unconfirmed Transactions
Lists transactions that are pending and waiting to be added to a block.
Get Worker List
Provides a list of every mining worker currently registered to your pool account.
Get Worker Stats
Gathers specific performance metrics and status data for individual mining workers.
Security and governance baked right in.
Pick your AI client below to get set up. Just create a Vinkius account, subscribe, and you're instantly up and running. We handle the entire backend infrastructure, delivering out-of-the-box support for HTTPS Streamable, SSE, and OAuth2—zero messy routing required.
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 5,100+ other servers whenever your AI needs more. One click, no limits.
- Use this MCP plus 5,100+ 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
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 connection provides 13 powerful capabilities that interface natively with Claude, ChatGPT, Cursor, and other compatible AI platforms. No middleware. No custom integration required.
Tracking funds across a major crypto network is messy work.
Right now, tracking an address's total value means clicking through multiple web interfaces: one for the block explorer to see if transactions were confirmed, another dashboard to check current balances, and often a third place just to look at payment records. You spend time copy-pasting hashes and cross-referencing timestamps.
With this MCP, you ask your agent once. It pulls all those data points—the raw transaction details, the unspent outputs, and the block metadata—and gives it back clean. What you get is a single, structured narrative of where the funds moved.
Getting Mining Pool Performance Metrics
Before this MCP, checking your farm's health meant logging into a portal and manually looking at various gauges: was the hashrate dipping? Were workers listed as dead units? You’d have to jump between different pages just to assemble a status report.
Now, you simply ask. The agent runs `get_worker_list` and immediately pulls detailed stats using `get_worker_stats`. The difference is massive: instead of manual clicks, you get an instant diagnostic report.
What your AI can actually do with this
This MCP connects your AI client directly to the Bitcoin network's raw data and a professional mining pool dashboard. You can check any block, track every transaction that passes through a specific address, or pull up the full history of unspent outputs (UTXOs). It’s not just for looking at coin balances; you can also monitor your entire mining operation—checking worker uptime, historical hashrate trends, and payment receipts.
If you're building anything with blockchain data, this is it. Vinkius makes sure that once you connect to the catalog, you get access to all these specialized crypto endpoints without having to manage multiple keys or connections.
019e5d03-dfd8-70e1-93e3-d4a1cc2dda28 Here's how it actually works
The bottom line is you get direct access to both public blockchain records and private mining pool metrics through one unified connection.
First, you subscribe to the MCP and provide your BTC.com Access Key if you need mining pool data.
Next, you ask your AI client to perform a specific query, like 'What was the hashrate last week?' or 'Show me transactions for this address.'
The MCP executes the appropriate tool call using the API and returns clean, structured data that your agent can use directly.
Who is this actually for?
This MCP serves crypto developers, financial data analysts, and dedicated mining operators. It's for anyone who needs raw, verifiable network state data or real-time performance metrics that standard dashboards can’t provide.
You use the MCP to verify transaction inputs/outputs and debug address balances directly in your coding environment.
You monitor farm health by checking worker lists, current hashrate stability, and historical performance trends without logging into a separate portal.
You extract real-time blockchain metrics, payment history, and block metadata to build research reports or audit trails.
What Changes When You Connect
Instead of cross-referencing a block explorer with your mining dashboard, you can use this MCP to get both sets of data in one query. For example, checking the get_latest_block status alongside your worker stats.
Stop guessing where money went. You can trace an address's full journey by combining get_address_summary with specific transaction checks using get_transaction.
Keep your farm running optimally. Use get_worker_list and get_worker_stats to instantly spot inactive or underperforming miners, letting you troubleshoot without logging into a separate platform.
Move beyond simple balances. By calling get_address_utxo, you see the raw, unspent components of an address's value, which is critical for deep financial analysis.
When tracking payouts, combine get_payment_history with block data. This lets you confirm that a payment recorded on your dashboard actually made it into the public ledger.
See it in action
Auditing Funds Movement
A financial analyst needs to prove where funds originated and ended up. They ask their agent to get all transactions for a source address using get_address_transactions, then use the resulting hashes to pull detailed data via get_transaction to confirm the final recipient block.
Investigating Network Lag
A developer notices a transaction seems stuck. They first check get_unconfirmed_transactions for pending activity, then use get_block and get_latest_block to see if the network is currently processing blocks faster or slower than expected.
Optimizing Farm Capacity
A mining operator needs to know which units are struggling. They run get_worker_list and then use get_worker_stats on each unit to pinpoint exactly which machines have low hashrate or high rejection rates.
Calculating Total Wealth
A data scientist needs a true measure of an address's liquid wealth. They run get_address_utxo first, and then use the resulting UTXO hashes to pull all associated transactions using get_transaction.
The honest tradeoffs
Only checking balances
Just calling get_address_summary gives you a single number, which only tells you the current balance. It says nothing about the history or where that money came from.
To get full context, combine calls: use get_address_summary to start, then follow up with get_address_transactions and finally get_transaction for key events.
Treating mining stats as static
Assuming your farm's performance is stable means you might miss critical drops. You can't rely on a single snapshot of worker health.
Always monitor trends by calling get_hashrate_history to see performance over time, and use get_worker_stats for the current moment.
Forgetting block context
Pulling a list of transactions without knowing which block they belong to makes them useless data points.
Always start by getting the latest network state using get_latest_block or fetching specific historical blocks via get_block, and then use that hash/height with get_block_transactions.
When It Fits, When It Doesn't
Use this MCP if your analysis requires both public blockchain data (e.g., block heights, transaction details) AND private mining pool metrics (hashrate, worker status). If you only care about basic account balances and history, get_address_summary is enough. However, if you need to know why the balance changed or how healthy your hardware is, this MCP is necessary. Don't use it just because you want a single API endpoint; use it when you need depth. Specifically, if you are debugging a complex financial movement, you must combine get_address_utxo (for raw state) with get_transaction (for the event details). If your goal is purely academic research on block structure alone, then tools focused solely on block data might suffice, but this MCP covers that and more.
Questions you might have
How do I check my mining hashrate history using get_hashrate_history? +
You simply ask your agent to retrieve the hashrate history. The tool provides time-series data, letting you see how stable or volatile your pool's performance has been over days or weeks.
Do I need get_account_stats for every query? +
No, not always. get_account_stats gives an overview. If you want to know the specific transactions that led to a balance change, use get_address_transactions instead.
What is the difference between get_transaction and get_block_transactions? +
get_block_transactions lists all activity within one single block. get_transaction lets you focus on one specific transaction, giving you its full input/output breakdown.
Can I use this MCP to track payments received via get_payment_history? +
Yes, the MCP supports that by calling get_payment_history. This allows your agent to pull a record of past financial activity directly from your pool account.
How do I use get_address_utxo to check if a Bitcoin address has funds ready for immediate spending? +
It provides the exact unspent transaction outputs (UTXOs) tied to an address. This is critical because it tells you precisely which chunks of BTC are available right now, rather than just giving a total balance figure.
What happens if I try to run get_worker_list without setting the required BTC.com Access Key? +
The function will fail authentication because it requires credentials. You must set your access key first before calling get_worker_list or any other pool-related tool.
How do I use get_unconfirmed_transactions to see pending activity on the blockchain? +
It retrieves data from the mempool, showing transactions that have been broadcast but not yet included in a finalized block. This helps track network congestion and pending payments.
What is the difference between get_address_summary and using get_address_transactions? +
The summary gives you high-level metrics, like total balance and transaction count. However, get_address_transactions provides a full list of every single historical transaction associated with that address.
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.
We've already built the connector for BTC.com API. Just plug in your AI agents and start using Vinkius.
No hosting. No infrastructure. No complex setup.
All 13 tools are live and waiting.
You're up and running in seconds.
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.
Built, hosted, and secured by Vinkius. You just connect and go.