Skip to main content
Glama
xOrbuc

orbuc-mcp-server

by xOrbuc
OverviewSchemaSourceRelated ServersDiscussionsAdmin
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

Features and capabilities supported by this server

Protocol revision2025-11-25

CapabilityDetails
tools
{
  "listChanged": false
}

Tools

Functions exposed to the LLM to take actions

NameDescription
orbuc_stablecoin_mcapB

Get historical daily total stablecoin market cap across all tracked issuers.

Returns daily total_mcap_usd, daily_change_usd, and daily_change_pct.
Source: Orbuc.
orbuc_stablecoin_latestA

Get the latest full snapshot of all tracked stablecoins with per-issuer breakdown.

Returns each stablecoin's total_supply_usd, issuer, and per-chain deployment data.
orbuc_stablecoin_coinA

Get historical supply data for a specific stablecoin.

Args:
    symbol: Stablecoin ticker, e.g. USDT, USDC, DAI (required)
    days: Number of days of history
    start_date: Start date YYYY-MM-DD
    end_date: End date YYYY-MM-DD
orbuc_stablecoin_coin_latestA

Get the latest supply data for a specific stablecoin with chain breakdown.

Args:
    symbol: Stablecoin ticker, e.g. USDT, USDC (required)
orbuc_stablecoin_aggregateA

Get daily aggregate stablecoin data at different levels.

level='total': daily total market cap.
level='symbol': daily breakdown per stablecoin.
level='chain': daily breakdown per chain per symbol.
orbuc_stablecoin_chainsA

Get stablecoin supply distribution across chains (Ethereum, Tron, Solana, etc.).

Args:
    days: Number of days of history (optional)
orbuc_btc_holdings_currentA

Get the latest total BTC held by institutions, broken down by segment.

Segments: public_companies, etf_funds, governments, private_companies,
defi_other, exchanges_custodians.
orbuc_btc_holdings_segmentsA

Get current BTC holdings per segment.

Each segment includes btc_amount and source.
orbuc_btc_holdings_dailyA

Get daily BTC holdings time series, optionally filtered by segment.

Args:
    segment: public_companies, etf_funds, governments, private_companies,
             defi_other, exchanges_custodians. Omit for aggregate totals.
    start: Start date YYYY-MM-DD
    end: End date YYYY-MM-DD
orbuc_btc_holdings_weeklyA

Get weekly aggregated BTC holdings, optionally filtered by segment.

Args:
    segment: Segment name (optional)
orbuc_btc_healthA

Check health of the BTC holdings tracker.

Returns status, database date range, segment count, and record totals.

orbuc_stablecoin_healthA

Check health of the stablecoin market cap tracker.

Returns status, latest date, total market cap, and tracked coins/chains.

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

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.7/5.0

Scored across 12 tools

Disambiguation4/5

Tools are cleanly separated into BTC holdings and stablecoin domains with clear time-granularity distinctions (current/daily/weekly). Minor overlap exists between btc_holdings_current and btc_holdings_segments (both return current segment data), and between stablecoin_aggregate with level='total' and stablecoin_mcap, but descriptions help differentiate them.

Naming Consistency4/5

Consistent 'orbuc_domain_resource' pattern throughout with snake_case. All tools use domain prefixes (btc_ or stablecoin_) appropriately. Minor deviations include 'mcap' abbreviation instead of 'market_cap', and mixing temporal suffixes (current, daily) with structural nouns (segments, chains), but overall predictable.

Tool Count5/5

Twelve tools is well-scoped for a financial data server covering two distinct asset classes. The count provides appropriate granularity for BTC holdings (health, current, daily, weekly, segment views) and stablecoins (health, aggregate, chain, specific coin, latest snapshot) without bloat.

Completeness4/5

Strong coverage for stablecoin lifecycle data (historical, current, aggregate, per-chain, per-coin) and BTC holdings time-series. Minor gap: BTC tools only provide aggregate segment data (public_companies, governments, etc.) without entity-specific lookups (e.g., individual company holdings), though agents can filter from segment data.

Maintenance

ActivityInactive
ResponsivenessNo issues

Resources