Home / MCP registry index / io.github.xOrbuc/orbuc

Orbuc

io.github.xOrbuc/orbuc in the official MCP registry. Endpoint https://mcp.orbuc.io/mcp/orbuc. Source: github.com/xOrbuc/orbuc-mcp-server.

The registry describes it as: On-chain stablecoin market cap and Bitcoin institutional holdings data.

We read its 12 tools on 2026-10-30. Nothing in them matched our tool-poisoning rules.

A clean read means these rules found nothing, not that the server is harmless. A server can change its tools at any time, which is why the index reads it again every week.

Connect it

The endpoint answers MCP over HTTP; that is how we read it. Add it to your client:

Claude Code

claude mcp add --transport http orbuc https://mcp.orbuc.io/mcp/orbuc

Cursor: ~/.cursor/mcp.json

{
  "mcpServers": {
    "orbuc": {
      "url": "https://mcp.orbuc.io/mcp/orbuc"
    }
  }
}

VS Code

code --add-mcp '{"name":"orbuc","type":"http","url":"https://mcp.orbuc.io/mcp/orbuc"}'

Some servers ask you to sign in the first time a client connects, or want a key from the people who run them; the server's own docs say which.

Let Claude Code check servers as it adds them

With the free lazaretto-guard plugin installed, when Claude Code adds a server for you or writes one into an MCP config, the plugin reads the server's tools first and asks you if one of our rules matches. Install it, restart Claude Code, then ask it to run the command above.

Install lazaretto-guard

claude plugin marketplace add jamesdfinance-dev/lazaretto-plugins
claude plugin install lazaretto-guard@lazaretto-plugins

Tools it advertises

orbuc_stablecoin_mcap orbuc_stablecoin_latest orbuc_stablecoin_coin orbuc_stablecoin_coin_latest orbuc_stablecoin_aggregate orbuc_stablecoin_chains orbuc_btc_holdings_current orbuc_btc_holdings_segments orbuc_btc_holdings_daily orbuc_btc_holdings_weekly orbuc_btc_health orbuc_stablecoin_health

Run this server? Show the check in your README

The badge reflects the latest weekly read:

Markdown

[![MCP tool check](https://lazaretto.dev/mcp-registry/io-github-xorbuc-orbuc/badge.svg)](https://lazaretto.dev/mcp-registry/io-github-xorbuc-orbuc)

How this was checked

Lazaretto connects to the endpoint the way any MCP client does, asks the server to introduce itself and list its tools, and reads every name, description, parameter schema and server instruction for tool poisoning: hidden directive blocks, orders to read local secrets, parameters built to carry secrets or the conversation out, orders that redirect another server's tools, and invisible characters. It never calls a tool. What we found across the registry.

To run the same check every time Claude Code adds a server, install the free lazaretto-guard plugin. Browse every server in the index.