Skip to main content
Glama
jukkablomberg

CoinBucha

by jukkablomberg
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

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

Features and capabilities supported by this server

Protocol revision2025-11-25

CapabilityDetails
tools
{
  "listChanged": false
}
prompts
{
  "listChanged": false
}
resources
{
  "subscribe": false,
  "listChanged": false
}
experimental
{}

Tools

Functions exposed to the LLM to take actions

NameDescription
scan_signalsA

Ranked composite feed of Bitcoin signals.

Args:
    min_strength: only return signals with signal_strength >= this (0-100).
    direction: filter by 'tailwind', 'headwind', or 'neutral'.
    signal_types: filter by type, e.g. ['sovereign_adoption','hiring_velocity'].
get_hiring_signalA

Bitcoin-native hiring velocity (open roles + 30/90-day deltas).

Args:
    company: optional company name filter (case-insensitive substring).
get_sovereign_reservesB

Sovereign Bitcoin holdings, ranked.

Args:
    country: optional country name/code filter (case-insensitive substring).
    tier: optional tier filter (1 = largest holders).
get_treasury_holdingsB

Corporate Bitcoin treasury holdings: total BTC held by public companies + top holders.

get_etf_flowsA

Spot Bitcoin ETF net flows (latest day + trailing 5/30-day) — institutional demand.

get_network_signalA

Bitcoin network hashrate level and 30/90-day trend (miner conviction / security).

get_daily_brewB

Today's machine-readable signal digest (the CoinBucha Daily Brew).

Prompts

Interactive templates invoked by user choice

NameDescription
morning_bitcoin_briefOne-shot template to render the CoinBucha Daily Brew from live signals.

Resources

Contextual data attached and managed by the client

NameDescription
methodologyHow every CoinBucha signal is computed. Public = credibility moat.
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 7 tools

Disambiguation5/5

Each tool targets a distinct data category (hiring, sovereign reserves, treasury, ETF flows, network, digest, composite feed). While get_daily_brew and scan_signals both surface signals, their descriptions clearly differentiate a digest from a filterable ranked feed.

Naming Consistency4/5

Six of seven tools follow the 'get_<noun>' pattern (e.g., get_etf_flows, get_network_signal). The outlier 'scan_signals' uses a different verb style, causing a minor deviation in an otherwise consistent scheme.

Tool Count5/5

Seven tools is a well-scoped set for a Bitcoin signals server, covering distinct signal categories and aggregate views without bloat.

Completeness4/5

The surface covers key Bitcoin signal categories (institutional, corporate, sovereign, network, hiring) plus digest and composite feeds. A slight gap might be a direct price or on-chain metric tool, but the server appears purpose-focused and effective.

Maintenance

ActivityMaintained
ResponsivenessNo issues

Resources