Skip to main content
Glama

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault
ALCHEMY_KEYNoOptional: private RPC instead of public
HOOD_MCP_PORTNoPort for HTTP transport (default 8730)8730
HOOD_MCP_NETWORKNoNetwork to use: mainnet or testnet (default mainnet)mainnet
HOOD_MCP_TRANSPORTNoTransport type: stdio or http (default stdio)stdio
HOOD_MCP_ENABLE_TRADINGNoMust be set to '1' to enable trading server
HOOD_MCP_MAX_SPEND_USDGNoPer-call spend cap in USD (default 25)25
HOOD_MCP_MAX_SESSION_USDGNoPer-session spend cap in USD (default 100)100
ROBINHOOD_CHAIN_PRIVATE_KEYNoPrivate key for trading server (0x...)
HOOD_MCP_ACKNOWLEDGE_ELIGIBILITYNoSet 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.

Read-only market data for Robinhood Chain (chain ID 4663), the permissionless Arbitrum Orbit L2 with tokenized-equity "Stock Tokens", the USDG stablecoin, and the NOXA / The Odyssey memecoin launchpads. Use get_stock_quote for a ticker's oracle+DEX price and premium, get_portfolio for a wallet's holdings, list_trending_coins / get_coin for memecoins, get_recent_launches / watch_launches for launchpad activity, and get_chain_stats for the chain. All data is public and read-only. To place trades, use the separate hood-mcp-trading server.

Capabilities

Features and capabilities supported by this server

Protocol revision2025-11-25

CapabilityDetails
tools
{
  "listChanged": true
}

Tools

Functions exposed to the LLM to take actions

NameDescription
get_chain_statsA

Live Robinhood Chain overview: latest block, gas price, TVL, and network totals (blocks, addresses, transactions, block time). No inputs.

list_stock_tokensB

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_coinsB

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

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription

No resources

TDQS

A3.8/5.0

Scored across 9 tools

Disambiguation4/5

Tools mostly target distinct resources: portfolio, single-token detail, trending list, launches, search, stock registry, stock quote, and chain stats. The only mild overlaps are get_coin vs get_stock_quote (both return price, but by address vs ticker with oracle detail) and list_stock_tokens vs search_token (registry vs fuzzy search), which descriptions clarify adequately.

Naming Consistency5/5

All nine tools follow a clean verb_noun snake_case pattern (get_portfolio, list_stock_tokens, search_token, watch_launches, etc.). The single non-'get' verb, watch_launches, still adheres to the verb_noun convention and reads predictably.

Tool Count5/5

Nine tools is well within the ideal 3-15 range for a chain data/analytics server. Each tool covers a distinct capability (portfolio, token detail, discovery, launches, stocks, chain stats) with no obvious filler.

Completeness4/5

The read-only surface covers portfolios, token detail, discovery (trending, launches, search, registry), stock pricing, and chain stats—a solid analytics scope. Minor gaps remain around transaction/address activity history and block-level lookups that agents might expect from a chain explorer.

Maintenance

ActivityMaintained
ResponsivenessLimited data