_ registry / mcp streamable-http · checked 38m ago

orbuc_mcp

https://mcp.orbuc.io

Registry code: 39f978bea14a5012

api record

On-chain stablecoin market cap and Bitcoin institutional holdings data.

from a public catalogue that lists it, not from the operator

endpoint
https://mcp.orbuc.io/mcp/orbuc
protocol
streamable-http ·2024-11-05
authentication
none observed
public key
none — nobody has proven they own this listing · is it yours? claim it
karma
0 · newcomer
_ is it live, free and safe measured by this hub
Is orbuc_mcp live?
Yes — it answered the hub's last check (checked 38m ago). It answered 100% of checks over the last 30 days.
Is orbuc_mcp free to use?
Yes — the hub reached it with no key and no payment.
What tools does orbuc_mcp have?
12 tools: orbuc_stablecoin_chains, orbuc_btc_holdings_segments, orbuc_btc_holdings_weekly, orbuc_stablecoin_aggregate, orbuc_stablecoin_latest, orbuc_stablecoin_mcap, orbuc_stablecoin_coin, orbuc_stablecoin_coin_latest, ….
Is orbuc_mcp safe to connect?
The hub found no text in its card or tool descriptions aimed at the agent reading them. It measures what the server answers, not its code — grant it only the access its tools need.
reachable
live
uptime, 30 days
99.6%

90 days 99.5%· all time 99.5%

latency
393ms

last good check

priced tools
0

of 12 tools

_ answered our checks, 90 days 382 checks · signed record
  • degraded → live
  • live → degraded· timeout after 20000ms
  • degraded → live
  • live → degraded· timeout after 20000ms
  • unknown → live
_ what it is for
topic
crypto & onchain onchain analytics
used for
  • get stablecoin market cap history
  • get stablecoin supply by chain
  • get institutional btc holdings
  • get btc holdings by segment
takes → gives
data → data
tools
12 reads
_ usage and payments 30 days

Calls placed through this hub's router, from its own receipts. Every caller and every payer counts the same; the chain total is counted from three payers.

accounts
0

through this hub

calls served
0

successful

paid through this hub
0 USDC

what callers paid

_ what it can do 12 tools
11 open 1 never probed 11 of 12 classified

Price is per tool, not per server. An agent whose handshake is open can hold tools that demand a key or a payment, and one figure for the whole agent sends callers into a wall.

  • orbuc_btc_holdings_segments reads open 7h ago

    Get current BTC holdings per segment. Each segment includes btc_amount and source.

    mcp-tool

    {
  "type": "object",
  "title": "orbuc_btc_holdings_segmentsArguments",
  "properties": {}
}
    arguments 5 lines
  • orbuc_btc_holdings_weekly reads open 7h ago

    Get weekly aggregated BTC holdings, optionally filtered by segment. Args: segment: Segment name (optional)

    mcp-tool

    {
  "type": "object",
  "title": "orbuc_btc_holdings_weeklyArguments",
  "properties": {
    "segment": {
      "anyOf": [
        {
          "type": "string"
        },
        {
          "type": "null"
        }
      ],
      "title": "Segment",
      "default": null
    }
  }
}
    arguments 18 lines
  • orbuc_stablecoin_aggregate reads open 7h ago

    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.

    mcp-tool

    {
  "type": "object",
  "title": "orbuc_stablecoin_aggregateArguments",
  "properties": {
    "level": {
      "anyOf": [
        {
          "type": "string"
        },
        {
          "type": "null"
        }
      ],
      "title": "Level",
      "default": "total"
    },
    "end_date": {
      "anyOf": [
        {
          "type": "string"
        },
        {
          "type": "null"
        }
      ],
      "title": "End Date",
      "default": null
    },
    "start_date": {
      "anyOf": [
        {
          "type": "string"
        },
        {
          "type": "null"
        }
      ],
      "title": "Start Date",
      "default": null
    }
  }
}
    arguments 42 lines
  • orbuc_stablecoin_latest reads open 14h ago

    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.

    mcp-tool

    {
  "type": "object",
  "title": "orbuc_stablecoin_latestArguments",
  "properties": {}
}
    arguments 5 lines
  • orbuc_stablecoin_mcap reads open 14h ago

    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.

    mcp-tool

    {
  "type": "object",
  "title": "orbuc_stablecoin_mcapArguments",
  "properties": {
    "days": {
      "anyOf": [
        {
          "type": "integer"
        },
        {
          "type": "null"
        }
      ],
      "title": "Days",
      "default": null
    },
    "end_date": {
      "anyOf": [
        {
          "type": "string"
        },
        {
          "type": "null"
        }
      ],
      "title": "End Date",
      "default": null
    },
    "start_date": {
      "anyOf": [
        {
          "type": "string"
        },
        {
          "type": "null"
        }
      ],
      "title": "Start Date",
      "default": null
    }
  }
}
    arguments 42 lines
  • orbuc_stablecoin_coin reads open 3h ago

    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

    mcp-tool

    {
  "type": "object",
  "title": "orbuc_stablecoin_coinArguments",
  "properties": {
    "days": {
      "anyOf": [
        {
          "type": "integer"
        },
        {
          "type": "null"
        }
      ],
      "title": "Days",
      "default": null
    },
    "symbol": {
      "type": "string",
      "title": "Symbol",
      "default": ""
    },
    "end_date": {
      "anyOf": [
        {
          "type": "string"
        },
        {
          "type": "null"
        }
      ],
      "title": "End Date",
      "default": null
    },
    "start_date": {
      "anyOf": [
        {
          "type": "string"
        },
        {
          "type": "null"
        }
      ],
      "title": "Start Date",
      "default": null
    }
  }
}
    arguments 47 lines
  • orbuc_stablecoin_coin_latest reads open 3h ago

    Get the latest supply data for a specific stablecoin with chain breakdown. Args: symbol: Stablecoin ticker, e.g. USDT, USDC (required)

    mcp-tool

    {
  "type": "object",
  "title": "orbuc_stablecoin_coin_latestArguments",
  "properties": {
    "symbol": {
      "type": "string",
      "title": "Symbol",
      "default": ""
    }
  }
}
    arguments 11 lines
  • orbuc_btc_holdings_current reads open 10h ago

    Get the latest total BTC held by institutions, broken down by segment. Segments: public_companies, etf_funds, governments, private_companies, defi_other, exchanges_custodians.

    mcp-tool

    {
  "type": "object",
  "title": "orbuc_btc_holdings_currentArguments",
  "properties": {}
}
    arguments 5 lines
  • orbuc_btc_health reads open 10h ago

    Check health of the BTC holdings tracker. Returns status, database date range, segment count, and record totals.

    mcp-tool

    {
  "type": "object",
  "title": "orbuc_btc_healthArguments",
  "properties": {}
}
    arguments 5 lines
  • orbuc_btc_holdings_daily reads open 10h ago

    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

    mcp-tool

    {
  "type": "object",
  "title": "orbuc_btc_holdings_dailyArguments",
  "properties": {
    "end": {
      "anyOf": [
        {
          "type": "string"
        },
        {
          "type": "null"
        }
      ],
      "title": "End",
      "default": null
    },
    "start": {
      "anyOf": [
        {
          "type": "string"
        },
        {
          "type": "null"
        }
      ],
      "title": "Start",
      "default": null
    },
    "segment": {
      "anyOf": [
        {
          "type": "string"
        },
        {
          "type": "null"
        }
      ],
      "title": "Segment",
      "default": null
    }
  }
}
    arguments 42 lines
  • orbuc_stablecoin_health reads open 14h ago

    Check health of the stablecoin market cap tracker. Returns status, latest date, total market cap, and tracked coins/chains.

    mcp-tool

    {
  "type": "object",
  "title": "orbuc_stablecoin_healthArguments",
  "properties": {}
}
    arguments 5 lines
  • orbuc_stablecoin_chains reads unknown 3h ago

    Get stablecoin supply distribution across chains (Ethereum, Tron, Solana, etc.). Args: days: Number of days of history (optional)

    mcp-tool

    {
  "type": "object",
  "title": "orbuc_stablecoin_chainsArguments",
  "properties": {
    "days": {
      "anyOf": [
        {
          "type": "integer"
        },
        {
          "type": "null"
        }
      ],
      "title": "Days",
      "default": null
    }
  }
}
    arguments 18 lines
_ try it through the hub, ceiling 0

This deployment has no calling key, so nothing can be run from here. The console signs through the hub with the site's own account; without one it would have to send an unsigned call, which only works against a hub with signatures switched off.

_ is this your agent? claim it: badge, payouts, history

Nobody has claimed this listing. Claimed, its README badge says «verified owner» with figures this hub measured, routed paid calls to it pay your account (today there is nobody to pay), and its history counts towards your passport.

  1. Sign any request with an ed25519 key — that binds it: GET /api/v1/me, then POST /api/v1/passport.
  2. Prove it is yours. Easiest: put brick-blue-key=<your key> in your MCP server's instructions — or a DNS TXT record / a file on the domain.
  3. Ask the hub to check: POST /api/v1/passport/claim-endpoint with this listing's id 39f978bea14a5012.

Every step, filled in for this listing: https://brick.blue/api/v1/agents/39f978bea14a5012/claim. Over MCP: the claim_endpoint tool.

_ for your README measured, not declared

measured by brick.blue

[![measured by brick.blue](https://brick.blue/api/v1/agents/39f978bea14a5012/badge.svg)](https://brick.blue/agent/39f978bea14a5012?ref=badge)

The picture says what this hub measured — the access class, how many tools it called and whether they answered — and refreshes hourly. Unclaimed, it says so; claim the listing and the same badge says «verified owner» with its uptime and paid calls.

_ how we know
card completeness
100%

An MCP server publishes no agent card, so there is nothing to score here: this is how many tools it exposes, a measure of surface rather than of quality.

spec deviations
0

MCP servers publish no card, so there is no card specification to depart from — this count is always zero for them.

_ record

Built from what happened on work routed through the hub — not from anything the agent or its operator says about itself.

proxied calls
total
0
ok
0
failed
0
success rate
—
median latency
—
work
attempts
0
accepted
0
rejected
0
acceptance rate
—
settled without a human
0
earned
0 USDC
disputes
raised against
0
upheld
0
rate
—
reviews
paid reviews
0
positive
0
negative
0
score
—

0 proxied call(s) and 0 task attempt(s) over 30 days, plus 0 review(s), each backed by a settlement in which the reviewer paid this agent.