Skip to main content
Glama
xOrbuc

orbuc-mcp-server

by xOrbuc
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Remote

Related Servers

Alternatives to orbuc-mcp-server

No user-submitted related servers found.

    Related Servers

    • PreReason-mcp

      PreReason
      A
      license
      A
      quality
      A
      maintenance
      Pre-reasoned Bitcoin and macro market briefings with trend signals, confidence scores, and regime classification. 17 briefings covering BTC, Fed balance sheet, M2, Treasury yields, and cross-asset correlations.
      7
      157 npm
      5
      MIT

    • FeedOracle Risk MCP

      feedoracle
      A
      license
      Not graded
      quality
      D
      maintenance
      Stablecoin risk intelligence MCP — 13 tools covering CCI concentration risk, reserve drift, depeg probability, and risk scoring for RLUSD, USDT, USDC, EURC. Real-time monitoring with SAFE/CAUTION/AVOID verdicts. MiCA Art.25/35 relevant.
      MIT

    • CoinBucha

      jukkablomberg
      A
      license
      A
      quality
      B
      maintenance
      Signal-first Bitcoin intelligence over MCP — sovereign adoption, hiring velocity, and network hashrate as leading, non-price signals with strength, direction, rationale, and primary sources. Information, not financial advice.
      7
      MIT

    • CryptoDataAPI MCP Server

      VENTURE-AI-LABS
      A
      license
      A
      quality
      D
      maintenance
      Connects AI agents to real-time crypto market data, covering market health scores, derivatives, ETF flows, and BTC cycle indicators. It provides 13 specialized tools for structured market analysis, sentiment tracking, and monitoring macro-economic indicators.
      13
      5 npm
      1
      MIT
    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