hood-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| ALCHEMY_KEY | No | Optional: private RPC instead of public | |
| HOOD_MCP_PORT | No | Port for HTTP transport (default 8730) | 8730 |
| HOOD_MCP_NETWORK | No | Network to use: mainnet or testnet (default mainnet) | mainnet |
| HOOD_MCP_TRANSPORT | No | Transport type: stdio or http (default stdio) | stdio |
| HOOD_MCP_ENABLE_TRADING | No | Must be set to '1' to enable trading server | |
| HOOD_MCP_MAX_SPEND_USDG | No | Per-call spend cap in USD (default 25) | 25 |
| HOOD_MCP_MAX_SESSION_USDG | No | Per-session spend cap in USD (default 100) | 100 |
| ROBINHOOD_CHAIN_PRIVATE_KEY | No | Private key for trading server (0x...) | |
| HOOD_MCP_ACKNOWLEDGE_ELIGIBILITY | No | Set to '1' if eligible to hold Stock Tokens (default 0) | 0 |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| get_chain_statsA | Live Robinhood Chain overview: latest block, gas price, TVL, and network totals (blocks, addresses, transactions, block time). No inputs. |
| list_stock_tokensA | The registry of tokenized-equity Stock Tokens on Robinhood Chain (ticker, name, contract, Chainlink feed). Set pricedOnly to return only tokens with a live feed. |
| get_stock_quoteA | Price a Stock Token by ticker: the Chainlink oracle price, the on-chain Uniswap DEX mid price, the premium/discount between them, and the ERC-8056 multiplier (so you also get the underlying share price). |
| get_portfolioA | Multiplier-correct Stock Token portfolio for any address: per-position token balance, ERC-8056 share-equivalent, USD value, plus the USDG cash balance. Read-only. |
| get_coinA | Detail for any Robinhood Chain token by contract address: price, 24h volume, liquidity, FDV, holder count, and whether it is a registered Stock Token. |
| list_trending_coinsA | The trending pools on Robinhood Chain right now (memecoins and stocks) with price, 24h volume, price change, and liquidity — the pulse of the chain. |
| get_recent_launchesA | Recently launched tokens on Robinhood Chain launchpads (NOXA and The Odyssey), newest first, scanned from on-chain logs. |
| watch_launchesA | Watch NOXA + The Odyssey live for new token launches, blocking up to waitSeconds (or until limit launches are seen), then returns what appeared. Falls back to the most recent launch if none fire in the window. |
| search_tokenA | Find tokens on Robinhood Chain by ticker, name, or contract address — searches the Stock Token registry and the Blockscout index together. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 9 tools
Most tools target distinct actions (network stats, portfolio, search, quote, launches), but get_coin and get_stock_quote both return price data, and search_token overlaps with get_coin for finding token info. Still, descriptions clarify inputs and outputs well enough to avoid major confusion.
All tool names follow a consistent verb_noun pattern using lowercase with underscores (get_*, list_*, search_*, watch_*). No mixed conventions or vague verbs.
With 9 tools, the server is well-scoped for a blockchain data API. Each tool covers a distinct area of the domain (stats, portfolio, tokens, quotes, launches) without unnecessary bloat or thinness.
The toolset covers the core read-only needs: network stats, portfolio, token lookup, pricing, trending, and launches. Minor gaps exist (e.g., no historical price data or transaction-level queries), but these are not obvious dead ends for typical agent workflows.