Bugglo CLI

Point a general-purpose token checker at a Robinhood Chain contract and it will tell you — truthfully, and uselessly — that no contract exists at that address. It is not lying. It is looking at Ethereum.

You cannot tell that answer apart from a real finding, and neither can a language model. So a live token with bytecode, supply, and a liquidity pool gets reported as a phantom, and the tool sounds confident while it does it. That is not a hypothetical failure mode. It is the specific bug this package was written to kill.

bugglo talks to chain 4663 and nothing else. It checks at startup that the RPC it reached really is Robinhood Chain, and if it is not — wrong endpoint, unreachable, intercepted by an ISP — it says that, loudly, instead of answering about the wrong chain.

# Full rug check
npx bugglo 0x2103faA9D1762e27a716C61718b3aCf3Ec1F9bf1

# Machine-readable, for scripts and CI
npx bugglo --json 0x2103faA9D1762e27a716C61718b3aCf3Ec1F9bf1

# Your own RPC, when the public one is rate-limited or blocked
npx bugglo --rpc https://your-robinhood-chain-rpc.example 0x2103…

# Several endpoints — the first healthy chain-4663 one wins
npx bugglo --rpc-list https://rpc.one,https://rpc.two 0x2103…

The public Robinhood Chain RPC is free and convenient, and it is also a single point of failure: public RPCs get rate-limited, blocked by some ISPs, and are simply unreachable from some networks. For bots, CI, desks, and anything public-facing, point it at a dedicated endpoint.

ROBINX_RPC_URL=https://robinhood-mainnet.g.alchemy.com/v2/YOUR_KEY
BUGGLO_RPC_URLS=https://rpc.one,https://rpc.two   # comma-separated fallbacks
CHAIN_RPC_TIMEOUT_MS=10000
CHAIN_DEX_TIMEOUT_MS=8000

If every chain read fails, bugglo reports CANNOT CHECK / UNKNOWN. It does not turn an outage into a clean verdict — which, on the day the RPC is down and you are in a hurry, is the only behaviour worth anything.

Two hosts, and no others — named here because a tool that will not name its own dependencies has no business lecturing you about disclosure. rpc.mainnet.chain.robinhood.com serves everything read from the chain itself: bytecode, owner(), the EIP-1967 slot, ERC-20 metadata. api.dexscreener.com serves market data only, and it is a third party. If the RPC is down, every contract check reports UNKNOWN. If DexScreener is down, the market check reports UNKNOWN and the contract checks still run.

{
  "mcpServers": {
    "bugglo": {
      "command": "npx",
      "args": ["-y", "bugglo-mcp"]
    }
  }
}

It is not the only MCP server covering Robinhood Chain. RobinX MCP answers questions this one cannot — deployer reputation and insider-distribution history, both of which need an indexer behind them. If you want a deployer's rap sheet, use that; its stronger tools are paid and reached through a hosted API. This one is the other trade: it reads the chain directly, so it needs nothing from anybody. Different tools. Run both.

import { rugCheck, ROBINHOOD_CHAIN_ID } from "bugglo";
import { renderRugCheck } from "bugglo/report";

const result = await rugCheck("0x2103faA9D1762e27a716C61718b3aCf3Ec1F9bf1");
console.log(renderRugCheck(result));

import {
  ROBINHOOD_CHAIN_ID,
  RPC_URL,
  UNMEASURABLE,
  rugCheck,
  getContractCode,
  getTokenMetadata,
  getOwnership,
  getProxyStatus,
  getMarket,
  scanPowers,
} from "bugglo";

import { renderRugCheck, renderOneLine } from "bugglo/report";

UNMEASURABLE is exported on purpose. If you are building a UI on top of this, the list of what could not be checked is not an error path to swallow — it is a thing your users have to see.