MCP Setup

Search the full Blue Hub catalog of 110+ callable x402 tools (on-chain data, security, DeFi, token intel, builder tooling) and get each one's id, price, category and input shape. Use when the user's request has no exact match among the tools loaded here, BEFORE telling them it cannot be done — most capabilities live in the catalog, not in this manifest. Pair it with blue_call: registry finds the id, blue_call runs it. Triggers — "what tools do you have", "can you analyse X", "is there a tool for Y", "list your capabilities", or any request you are about to decline. Covers Base 8453 and Robinhood Chain 4663; each result states its own chain. Free.

Execute ANY tool from the Blue Hub catalog by its id — the paid counterpart to blue_registry. Use after blue_registry returns an id you want to run. PAYMENT: this is an x402 endpoint. The first call returns HTTP 402 with a `paymentRequirements` object (USDC on Base 8453, EIP-3009 transferWithAuthorization, payTo and exact amount included); sign that authorization with your own wallet and call again with the resulting header in `payment` to get the result. You hold your own keys — Blue Agent never sees them and never pulls funds. Triggers — any time you have a catalog id and need its output. Report the 402 to the user verbatim rather than inventing the tool's output.

Build an unsigned swap transaction the user signs in their OWN wallet. Base 8453 routes through 0x AllowanceHolder across Base liquidity; Robinhood Chain 4663 routes through Blue Agent's deployed RobinhoodSwapRouter against Uniswap V3 pools. Returns { to, data, value, chainId } plus any ERC-20 approval needed first — never a broadcast, never a private key. Use when the user wants to trade a token and you have both token addresses. Triggers — "swap X for Y", "buy TOKEN", "sell my TOKEN", "convert USDC to ETH". Check hub_honeypot and hub_liquidity_depth before swapping an unfamiliar token. If no route exists the response says so — do NOT invent a price.

Build an unsigned ERC-20 or native-ETH transfer the user signs in their OWN wallet, on Base 8453 or Robinhood Chain 4663. Returns { to, data, value, chainId } with the resolved symbol, decimals and exact base-unit amount so the user can verify before signing. Non-custodial — the server encodes calldata and nothing else. Use when the user wants to move tokens to an address. Triggers — "send 50 USDC to 0x…", "transfer TOKEN to", "pay this address". Run hub_risk_gate on the recipient first when the user has not sent there before.

Build an unsigned BIDIRECTIONAL bridge transaction between Base 8453 and Robinhood Chain 4663, backed by the Relay Protocol. Returns { to, data, value, chainId } plus a separate `approve` tx when the source token needs one — the user signs both in their own wallet. Use when a token or the user is on the wrong chain for what they want to do next, which is common because tokenized stocks list on both. Triggers — "bridge USDC to Robinhood", "move my ETH to Base", "get funds onto chain 4663", "I'm on the wrong network". fromChain and toChain must differ; the response carries a Relay tracker URL for the user to follow settlement.

Produce a concrete implementation plan for a project on Base 8453 — architecture, stack choice, folder structure, the integrations it needs, and a test plan. Use when the user has decided WHAT to build and needs the shape of it before writing code. Triggers — "how should I build this", "architecture for", "what stack", "structure this project", "plan the implementation". Advisory output: this is a framework for a builder to judge, not a set of measured facts. blue_idea / blue_ship / blue_raise are deliberately NOT loaded here — they ship as Claude Skills in the blue-agent plugin, where progressive disclosure costs no context.

Security and product-risk review of code, a smart contract, or a system design — 500+ checks across 13 categories, returning critical issues, suggested fixes, and a go/no-go. Use before a user deploys or ships anything that holds funds or user data, and when they ask for a second opinion on safety. Triggers — "audit this", "review my contract", "is this secure", "what could go wrong", "ready to deploy". For an already-deployed address on Base 8453 use hub_contract_trust instead — that reads the chain; this reads what you give it.

Open a Blue Hood signal ("arrow") — the desk's fired tokenized-stock signals with serial, ticker, direction, verdict note and the exact numbers captured at fire time. Use when the user asks WHY the desk took a view, or about a specific arrow. Triggers — "why is Blue Hood shorting NVDA", "what was arrow #0007", "show me the AAPL arrow", "latest Hood signal", "explain the last drift on TSLA". ⚠️ CHAIN IS PART OF THE QUESTION. Blue Hood runs TWO desks — Robinhood Chain 4663 and Base 8453 — and NVDA / META / GOOGL / AAPL exist on BOTH. A bare ticker does NOT identify an arrow. If the user names a chain, you MUST pass `chain`; omitting it searches either desk and you will answer about the wrong one. If they named none, omit it and REPORT whichever chain the returned arrow says it is. On not_found, say so plainly — never substitute the other chain's arrow, and never invent numbers. Answer only from the returned verdict_note and facts_at_fire.

Live price, market cap, 24h volume, price change and pool liquidity for any token on Base 8453, read from DexScreener — never from model memory. Use whenever a price or market-cap number is about to appear in your answer; quoting one from training data is always wrong by now. Triggers — "price of TOKEN", "what's X trading at", "market cap", "is it up today", "how much volume". Takes a 0x address (exact) or a ticker (resolved against Base pools, so verify the returned address is the one the user meant — tickers are not unique).

Every ERC-20 and native ETH balance held by a wallet on Base 8453, with live USD values, read via Moralis. Use before any portfolio answer, and before building a swap or send — it tells you what the wallet can actually spend, so you size a transaction against a real balance instead of an assumed one. Triggers — "what's in my wallet", "show my portfolio", "do I have enough USDC", "what tokens does 0x… hold", "my balance". Base 8453 only — for Robinhood Chain 4663 holdings, use blue_registry to find the rh- tools.

Trending and newly-active liquidity pools on Base 8453 with the chain-wide TVL snapshot — where volume is actually moving right now. Use when the user wants to find something rather than look something up. Triggers — "what's trending on Base", "hot pools", "where's the volume", "what should I look at", "anything new". Pair every candidate with hub_honeypot and hub_liquidity_depth before mentioning it as tradeable: appearing in a trending scan is a volume fact, not a safety verdict. Base 8453 only.

Live Base 8453 gas price with USD cost estimates for common actions (transfer, swap, contract deploy). Use before telling a user what a transaction will cost, and when a spend is small enough that fees change the answer. Triggers — "gas right now", "how much to send", "is it expensive to swap", "cost to deploy", "worth doing on-chain". Takes no arguments. Base 8453 only — Robinhood Chain 4663 fees are separate and not covered here.

Pre-flight screen for a pending transaction on Base 8453 — rug patterns, AML exposure on the counterparty, and known malicious contract shapes — returning a clear allow/deny verdict. Use UNPROMPTED before returning any blue_send_tx or blue_swap_tx aimed at an address the user has not dealt with before; a safety check the user has to request is a safety check that does not happen. Triggers — "is this safe to sign", "check this transaction", "should I approve this", "is this address ok". Base 8453.

Detect whether a Base 8453 token can be BOUGHT but not SOLD — the honeypot trap, plus punitive sell taxes and transfer restrictions that amount to the same thing. Use UNPROMPTED before any swap into a token the user did not already hold, and before naming an unfamiliar token as worth buying. Triggers — "is this a scam", "can I sell it", "rug check", "is TOKEN safe", "honeypot", or any buy intent on a token you have not screened this session. A clean result is not an endorsement — pair with hub_liquidity_depth, since a token you can sell into no liquidity is stuck anyway. Base 8453.

Trust assessment for any smart contract on Base 8453 — source verification, upgradeability, ownership and admin powers, privileged functions, audit history. Use before the user grants an approval or interacts with a protocol they have not used, and when "is this legit" is about a CONTRACT rather than a token. Triggers — "is this contract safe", "who controls this", "can they upgrade it", "should I approve", "is this protocol legit". Report unknowns as unknown — an unverified contract means we cannot assess it, which is not the same as it being malicious. Base 8453.

Risk and AML screen for a Base 8453 wallet from its real on-chain flow via Moralis — sanctions exposure, mixer proximity, and illicit-flow patterns in its transaction history. Use before sending funds TO an unknown address, and when a user asks whether a counterparty is safe to deal with. Triggers — "is this wallet safe", "check this address", "who is 0x…", "is this counterparty clean", "AML check". Distinct from hub_risk_gate, which screens a specific pending transaction; this screens the ADDRESS itself. Base 8453.

Real liquidity depth, expected slippage at size, and exit risk for a token on Base 8453 — whether a position can actually be closed, and at what cost. Use before recommending a token and before sizing any swap above pocket change; hub_honeypot answers "can I sell at all", this answers "can I sell THIS MUCH without destroying the price". Triggers — "can I exit", "how much slippage", "is there liquidity", "what if I buy $10k of this", "can I get out". A thin pool is a real finding — report the numbers, never soften them. Base 8453.

Encode a B20 `transferWithMemo` call on Base 8453 — send a B20 token with an on-chain memo (order id, invoice ref) so the payment reconciles against off-chain books. Returns { to, data, value } for the sender to sign; pure calldata builder, no keys, no payment, no broadcast. Use when an agent or merchant needs a payment that carries its own reference. Triggers — "pay invoice 1234 in USDC", "send payment with order id", "settle this with a memo", "reconcilable transfer". Memo is capped at 31 characters on-chain. B20 is Base-only — there is no B20 registry on Robinhood Chain 4663.