Bitcoin balance api skill

Skill BitconBalanceAPI/bitcoin-balance-api-skill/skills/bitcoin-balance-api-skill

Looks up confirmed Bitcoin mainnet address balances, batch balances, and UTXOs via the Bitcoin Balance API (MCP streamable HTTP or REST at api.bitcoin-balance-api.com). Use when the user needs Bitcoin on-chain balance checks, UTXO lists, wallet monitoring ideas, or help configuring the MCP client, API key, or Open Plugins bundle. Triggers: bitcoin-balance-api, address balance, satoshis, UTXO, MCP get_address_balance, batch balances, or api.bitcoin-balance-api.com.From its SKILL.md

Install

npx -y skills add BitconBalanceAPI/bitcoin-balance-api-skill --skill bitcoin-balance-api-skill

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

2 things to look at

no licenseNo license file was found in the repository. Code published without one is not open source by default, so using it at work is a question for whoever answers licensing questions where you are.
0 stars0 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

What its file declares

Copied from the file, not written here

The file declares its own license as Proprietary. That is the author’s claim about this one file, and it is not the same thing as the license GitHub reports for the repository, which is listed with the other numbers below.

SKILL.md

3.4 KB, 648 tokens by cl100k_base, as published. Nobody here has run it

Bitcoin Balance API

This skill orients the agent to query Bitcoin (mainnet by default) on-chain confirmed balances and UTXOs through Model Context Protocol (MCP) tools or REST, using the same API key and usage accounting for both.

When to use

Answering or automating: single-address balance, many addresses, or UTXO set.
Explaining how to connect Cursor (or another MCP client) to the hosted MCP endpoint.
Falling back to HTTP if MCP tools are not available in the environment.

MCP tools (hosted)

Tool	Purpose
`get_address_balance`	Confirmed balance in satoshis for one address.
`get_batch_balances`	Multiple addresses; limits align with the REST batch endpoint.
`get_utxo`	UTXO list for an address.

Authentication: send the same key as REST ?apikey= on every MCP HTTP request, preferably via the X-API-Key header.

Hosted (mainnet) MCP URL: https://api.bitcoin-balance-api.com/mcp

Example client config (merge mcpServers into the user’s MCP config; replace the placeholder key):

{
  "mcpServers": {
    "bitcoin-balance-api-mainnet": {
      "url": "https://api.bitcoin-balance-api.com/mcp",
      "headers": {
        "X-API-Key": "YOUR_API_KEY"
      }
    }
  }
}

Obtain a key: Get API key.

Open Plugins layout: a ready-made bundle (plugin manifest + .mcp.json) is published at github.com/BitconBalanceAPI/bitcoin-balance-api-mcp; copy or merge for distribution.

REST fallback (no MCP)

Base URL for the public mainnet service: https://api.bitcoin-balance-api.com

Method	Path	Notes
`GET`	`/v1/address/{address}`	Query: `?apikey=`
`POST`	`/v1/address/batch`	JSON body; same batch limits as tools
`GET`	`/v1/utxo/{address}`	Query: `?apikey=`

Interactive docs: Swagger / OpenAPI.

Edge cases and limits

Accounting: one tool call that resolves one address is counted like one GET /v1/address/...; batch tools count once per address, like POST /v1/address/batch. (Same rules as the REST API per official documentation.)
Treat API keys as production secrets; use HTTPS to the official host.

More detail

references/INTEGRATION.md — official MCP and REST examples, Open Plugins

What ships with it: 1 file

2.3 KB alongside SKILL.md

references/

INTEGRATION.md2.3 KB