Orbuc
REMOTE · MCP.ORBUC.IO · SCANNED SEP 20
On-chain stablecoin market cap and Bitcoin institutional holdings data.
Available components
How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →
Endpoint Security74
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- No authorisation is required to call this server. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one. See how to fix → View diagnostics → Partial
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability76
- AI-judged instruction clarity (good).Pass
- Tool/resource definitions use about 698 tokens (~58/item across 12 items; 12 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management100
- No destabilizing schema changes in the last 30 days.Pass
Tool Coverage67
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 0% of tool parameters carry a description.Fail
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 12 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 12 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities20
- Spec-recency check failed: implements MCP spec 2024-11-05; the latest is 2026-07-28. See how to fix → Fail
How do I install the Orbuc MCP server?
Orbuc is a hosted endpoint at https://mcp.orbuc.io/mcp/orbuc, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
remote · mcp.orbuc.io
claude mcp add --transport http xorbuc-orbuc 'https://mcp.orbuc.io/mcp/orbuc'
{
"mcpServers": {
"xorbuc-orbuc": {
"url": "https://mcp.orbuc.io/mcp/orbuc"
}
}
} {
"servers": {
"xorbuc-orbuc": {
"type": "http",
"url": "https://mcp.orbuc.io/mcp/orbuc"
}
}
} [mcp_servers.xorbuc-orbuc] url = "https://mcp.orbuc.io/mcp/orbuc"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"xorbuc-orbuc": {
"type": "remote",
"url": "https://mcp.orbuc.io/mcp/orbuc",
"enabled": true
}
}
} openclaw mcp add xorbuc-orbuc --url 'https://mcp.orbuc.io/mcp/orbuc' --transport streamable-http
mcp_servers:
xorbuc-orbuc:
url: "https://mcp.orbuc.io/mcp/orbuc" {
"McpServers": {
"xorbuc-orbuc": {
"Transport": "http",
"Url": "https://mcp.orbuc.io/mcp/orbuc"
}
}
} assistant mcp add xorbuc-orbuc -t streamable-http -u 'https://mcp.orbuc.io/mcp/orbuc'
{
"mcpServers": {
"xorbuc-orbuc": {
"type": "http",
"url": "https://mcp.orbuc.io/mcp/orbuc"
}
}
} The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 26 Aug 26 +1
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 25 Aug 26 +1
- Stability: 0.97 → pass security
- 24 Aug 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 93 to 97. That category is still filling its 30-day observation window: 28 days of observed history at the previous scan, 29 at this one. The score rises as the window fills, whether or not the server changes.
- 11 Aug 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 31 Jul 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 30 Jul 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 27 Jul 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 26 Jul 26 0
First indexed and scored.
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 20 Sept 2026 · Probed https://mcp.orbuc.io/mcp/orbuc
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=mcp.orbuc.io | CN=Amazon RSA 2048 M01,O=Amazon,C=US | 25 Aug 2026 | 10 Mar 2027 | RSA 2048 | SHA256-RSA | ec9953c43fa39939b8991bb4f8e6eb1 |
| SANs: mcp.orbuc.io | ||||||
| CN=Amazon RSA 2048 M01,O=Amazon,C=US (CA) | CN=Amazon Root CA 1,O=Amazon,C=US | 23 Aug 2022 | 23 Aug 2030 | RSA 2048 | SHA256-RSA | 77312380b9d6688a33b1ed9bf9ccda68e0e0f |
| CN=Amazon Root CA 1,O=Amazon,C=US (CA) | CN=Starfield Services Root Certificate Authority - G2,O=Starfield Technologies\, Inc.,L=Scottsdale,ST=Arizona,C=US | 25 May 2015 | 31 Dec 2037 | RSA 2048 | SHA256-RSA | 67f944a2a27cdf3fac2ae2b01f908eeb9c4c6 |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of mcp.orbuc.io. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| io. | present | 57355 | 8 | Verified |
| orbuc.io. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 200 |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://mcp.orbuc.io/mcp/orbuc | Verified | 200 | |
| http (plaintext) | http://mcp.orbuc.io/mcp/orbuc | HTTPS enforced |
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
orbuc_btc_health ~35
Check health of the BTC holdings tracker. Returns status, database date range, segment count, and record totals.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
orbuc_btc_holdings_current ~57
Get the latest total BTC held by institutions, broken down by segment. Segments: public_companies, etf_funds, governments, private_companies, defi_other, exchanges_custodians.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
orbuc_btc_holdings_daily ~96
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
| Name | Type | Req | Description |
|---|---|---|---|
| end | – | – | – |
| segment | – | – | – |
| start | – | – | – |
No output schema declared.
No examples provided.
orbuc_btc_holdings_segments ~30
Get current BTC holdings per segment. Each segment includes btc_amount and source.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
orbuc_btc_holdings_weekly ~42
Get weekly aggregated BTC holdings, optionally filtered by segment. Args: segment: Segment name (optional)
| Name | Type | Req | Description |
|---|---|---|---|
| segment | – | – | – |
No output schema declared.
No examples provided.
orbuc_stablecoin_aggregate ~74
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.
| Name | Type | Req | Description |
|---|---|---|---|
| end_date | – | – | – |
| level | – | – | – |
| start_date | – | – | – |
No output schema declared.
No examples provided.
orbuc_stablecoin_chains ~50
Get stablecoin supply distribution across chains (Ethereum, Tron, Solana, etc.). Args: days: Number of days of history (optional)
| Name | Type | Req | Description |
|---|---|---|---|
| days | – | – | – |
No output schema declared.
No examples provided.
orbuc_stablecoin_coin ~100
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
| Name | Type | Req | Description |
|---|---|---|---|
| days | – | – | – |
| end_date | – | – | – |
| start_date | – | – | – |
| symbol | string | – | – |
No output schema declared.
No examples provided.
orbuc_stablecoin_coin_latest ~56
Get the latest supply data for a specific stablecoin with chain breakdown. Args: symbol: Stablecoin ticker, e.g. USDT, USDC (required)
| Name | Type | Req | Description |
|---|---|---|---|
| symbol | string | – | – |
No output schema declared.
No examples provided.
orbuc_stablecoin_health ~40
Check health of the stablecoin market cap tracker. Returns status, latest date, total market cap, and tracked coins/chains.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
orbuc_stablecoin_latest ~48
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.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
orbuc_stablecoin_mcap ~70
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.
| Name | Type | Req | Description |
|---|---|---|---|
| days | – | – | – |
| end_date | – | – | – |
| start_date | – | – | – |
No output schema declared.
No examples provided.
What is the Orbuc MCP server?
Orbuc is an MCP server listed in the public MCP registry as io.github.xOrbuc/orbuc. On-chain stablecoin market cap and Bitcoin institutional holdings data. This page covers its hosted endpoint (https://mcp.orbuc.io/mcp/orbuc).
Is the Orbuc MCP server safe to use?
Orbuc scores 79 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the Orbuc MCP server expose?
Orbuc exposes 12 tools: orbuc_stablecoin_mcap, orbuc_stablecoin_latest, orbuc_stablecoin_coin, orbuc_stablecoin_coin_latest, orbuc_stablecoin_aggregate, and 7 more. Their descriptions and schemas cost roughly 698 tokens of context every time the server is loaded.
Does the Orbuc MCP server require authentication?
No. We connected to Orbuc without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the Orbuc MCP server still maintained?
Orbuc is still listed as active in the MCP registry. We last reached this channel on 20 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.