Skip to main content
Glama
kukapay

bitcoin-utxo-mcp

by kukapay
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault

No arguments

Instructions

Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.

This server publishes no instructions, or was last inspected before Glama recorded them.

Capabilities

Server capabilities have not been inspected yet.

Tools

Functions exposed to the LLM to take actions

NameDescription
get_utxoA

Get UTXO for a Bitcoin address.

Args:
    address (str): Bitcoin address (base58 or bech32 format)

Returns:
    A string containing:
    - Address
    - Number of UTXOs
    - Total value in BTC
    - List of UTXO details (txid, value, confirmations)
get_block_statsA

Get transaction statistics for a specific Bitcoin block.

Args:
    block_height (int): The height of the block

Returns:
    A string containing:
    - Block height
    - Block hash
    - Number of transactions
    - Total transaction value in BTC
    - Block time

Prompts

Interactive templates invoked by user choice

NameDescription
analyze_bitcoin_flowPrompt to analyze Bitcoin funds flow and network health. Returns: A string prompt for LLM analysis of Bitcoin UTXO and block data, including: - Funds flow implications - Network health indicators - Potential market impacts

Resources

Contextual data attached and managed by the client

NameDescription

No resources

Deploy Server
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

TDQS

A3.8/5.0

Scored across 2 tools

Disambiguation5/5

The two tools have completely distinct purposes with no overlap. get_block_stats focuses on block-level transaction statistics, while get_utxo retrieves unspent transaction outputs for specific addresses. An agent can easily differentiate between these two operations.

Naming Consistency5/5

Both tools follow a consistent verb_noun naming pattern with get_ prefix and snake_case formatting. The naming convention is predictable and readable throughout the tool set.

Tool Count2/5

With only 2 tools, this server feels significantly under-scoped for Bitcoin UTXO operations. A Bitcoin UTXO-focused server would typically need more tools for comprehensive coverage, such as transaction broadcasting, fee estimation, or address validation.

Completeness2/5

The tool surface is severely incomplete for Bitcoin UTXO operations. While it provides read operations for blocks and addresses, it lacks essential capabilities like transaction creation, signing, broadcasting, fee estimation, or multi-address UTXO aggregation. This creates significant gaps that will cause agent failures in typical Bitcoin workflows.

Maintenance

ActivityInactive
ResponsivenessNo issues

Resources