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 | |
Latest Blog Posts
- Who's Calling? MCP Hosts Are an Identity Blind Spot (And the Spec Knows It)By Om-Shree-0709 on .mcpAgent IdentityOAuth 2.1
- Your AI Chatbot Just Exposed Your CEO's Salary to an InternBy Om-Shree-0709 on .Agent IdentityMCP SecurityOAuth Delegation
- Why MCP Servers Need Execution Sandboxing (And Why Your Current Stack Isn't Enough)By Om-Shree-0709 on .Agentic AiPrompt InjectionWebAssembly
MCP directory API
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/yashhsm/hip4-mcp'
If you have feedback or need assistance with the MCP directory API, please join our Discord server