hip4-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
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 |
|---|---|
| list_outcomesB | List all HIP-4 outcome markets with metadata, side specs, and linked questions. Returns outcome IDs, names, descriptions, and for priceBinary markets: underlying asset, target price, expiry, and period. |
| get_outcome_bookB | Get the L2 orderbook for a specific outcome side. Returns bids, asks, spread, and depth summary. |
| get_outcome_pricesA | Get mid prices for all outcome markets. Returns decoded outcome IDs, side names, and current mid prices. |
| get_outcome_positionsA | Get a user's outcome token balances (positions in prediction markets). Filters spot balances to outcome tokens only. |
| get_outcome_depth_summaryB | Get a depth summary across ALL outcome markets. Shows bid/ask depth, spread, and best prices for every active outcome side. |
| search_outcomesA | Search and filter outcome markets by underlying asset, type, or keyword. Useful for finding specific prediction markets (e.g. all BTC binary markets). |
| get_outcome_candlesA | Get OHLCV candle data for an outcome side. Useful for charting price history of prediction market positions. |
| get_outcome_tradesA | Get a user's trade (fill) history filtered to outcome markets only. |
| get_outcome_open_ordersB | Get a user's open orders filtered to outcome markets only. |
| encoding_helperB | Convert between outcome IDs, side indices, coin symbols (#xxx), token names (+xxx), and asset IDs. Useful for understanding the HIP-4 asset encoding system. |
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 10 tools
Each tool targets a distinct data type (market info, prices, orderbook, user data, encoding), but get_outcome_prices and get_outcome_depth_summary both return price-related data for all markets, which could cause minor confusion. Descriptions are clear enough to differentiate them.
Most tools follow a consistent verb_noun pattern (list_, get_, search_), but 'encoding_helper' breaks the pattern by using a noun phrase. The rest are highly consistent, with all get_ tools prefixed uniformly.
10 tools is well within the optimal 3-15 range and each covers a specific aspect of HIP-4 outcome markets (listing, pricing, orderbook, user positions, trades, etc.). No tool feels redundant or unnecessary.
The server effectively covers read-only market data needs: listing, searching, prices, depth, candles, and user account data. The only notable gap is the lack of order placement/cancellation, but the server appears intended for data retrieval, not trading. A single-market fetch could also be useful but list_outcomes already provides all metadata.