horus-flow-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| RAPIDAPI_KEY | Yes | Your RapidAPI key for accessing Horus Flow Intelligence API |
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": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| get_crypto_flowA | Get real-time institutional orderflow for a cryptocurrency. |
| get_equity_flowA | Get real-time institutional orderflow for a US equity stock. |
| scan_crypto_flowA | Scan multiple cryptocurrencies for orderflow signals at once. |
| get_macro_blocksA | Get US equity market macro trend and recent institutional block trades. |
| get_composite_intelligenceA | Get composite intelligence score (0-100) with tactical verdict. |
| get_liquidation_heatmapA | Get liquidation zones with dollar amounts — where leveraged positions will be force-closed. |
| get_cross_exchange_flowA | Get Futures/Spot ratio, speculation index, and smart money divergence. |
| get_market_climateA | Get current market mode and health status. |
| get_ignitionsA | Detect volatility ignition events — potential explosive price moves. |
| get_market_intelligenceA | Get complete market intelligence in a single call — combines all endpoints. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
| get_api_info | Information about the Horus Flow Intelligence system. |
TDQS
Scored across 10 tools
Most tools have distinct purposes: crypto vs equity flow, batch scanning, macro blocks, composite score, liquidations, cross-exchange, climate, and ignition detection. The main ambiguity is between get_composite_intelligence and get_market_intelligence, though the latter is clearly described as an aggregate of all endpoints.
The dominant pattern is get_<domain>_<concept>, which is predictable and readable. One deviation is scan_crypto_flow, which uses a verb other than get, but it still follows the same broad noun/flow convention.
Ten tools is well-suited to the server's purpose of providing comprehensive market intelligence. Each tool addresses a distinct data need without redundancy, and the count feels appropriately scoped for a trading analysis domain.
The toolset covers crypto and equity orderflow, macro context, liquidation zones, cross-exchange data, market climate, ignition events, and a composite aggregate. Minor gaps include no direct tool for historical data or sentiment text, but the core pre-trade intelligence workflow is well covered.