pro.horustek/horus-flow-mcp
REMOTE · FLOW.HORUSTEK.PRO
Crypto order flow, cross-venue derivatives and US market context for AI agents, with a track record.
Available components
Last scanned (7 hours ago)
Scores higher than 64% of remote servers
Reachable. Last reached 5 Nov 2026.
Category Finance and Payments
How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →
Endpoint Security80
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- No authorisation is required to call this server. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one. See how to fix → View diagnostics → Partial
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability64
- AI-judged instruction clarity (good).Pass
- Context-footprint check failed: tool/resource definitions use about 1889 tokens (~125/item across 15 items; 15 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management43
- Stability observed for 13 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage71
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 0% of tool parameters carry a description.Fail
- Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 15 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 16 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 4 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 37 to 40. That category is still filling its 30-day observation window: 11 days of observed history at the previous scan, 12 at this one. The score rises as the window fills, whether or not the server changes.
- 2 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 30 to 33. That category is still filling its 30-day observation window: 9 days of observed history at the previous scan, 10 at this one. The score rises as the window fills, whether or not the server changes.
- 31 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 23 to 27. That category is still filling its 30-day observation window: 7 days of observed history at the previous scan, 8 at this one. The score rises as the window fills, whether or not the server changes.
- 28 Oct 26 +1
- The server rewrote its instructions, which are the text every model session reads security
- Tool “get_cross_asset” rewrote its description, which is the text the model reads security
- Tool “get_equity_flow” rewrote its description, which is the text the model reads security
- Tool “get_flow_history” rewrote its description, which is the text the model reads security
- Tool “get_ignitions” rewrote its description, which is the text the model reads security
- Tool “get_recent_events” rewrote its description, which is the text the model reads security
- Tool “get_signal_ledger” rewrote its description, which is the text the model reads security
- Tool “scan_market” rewrote its description, which is the text the model reads security
- Schema quality: 1621 → 1889 ▼ functional
- New tool “get_book_pressure” functional
- 25 Oct 26 +1
- The server rewrote its instructions, which are the text every model session reads security
- Tool “get_cortex” rewrote its description, which is the text the model reads security
- Tool “get_cross_asset” rewrote its description, which is the text the model reads security
- Tool “get_derivatives” rewrote its description, which is the text the model reads security
- Tool “get_equity_flow” rewrote its description, which is the text the model reads security
- Tool “get_flow_history” rewrote its description, which is the text the model reads security
- Tool “get_ignitions” rewrote its description, which is the text the model reads security
- Tool “get_market_overview” rewrote its description, which is the text the model reads security
- Tool “get_recent_events” rewrote its description, which is the text the model reads security
- Tool “get_signal_ledger” rewrote its description, which is the text the model reads security
- Tool “scan_market” rewrote its description, which is the text the model reads security
- Schema quality: pass → fail ▼ functional
- 24 Oct 26 0
- Stability: unverified → 0.03 ▲ functional
- 23 Oct 26 70
First indexed and scored.
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 5 Nov 2026 · Probed https://flow.horustek.pro/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=horustek.pro | CN=WE1,O=Google Trust Services,C=US | 4 Oct 2026 | 2 Jan 2027 | ECDSA 256 | ECDSA-SHA256 | 8f696da838396f220efdf32c7bc30dcf |
| SANs: horustek.pro, *.horustek.pro | ||||||
| CN=WE1,O=Google Trust Services,C=US (CA) | CN=GTS Root R4,O=Google Trust Services LLC,C=US | 13 Dec 2023 | 20 Feb 2029 | ECDSA 256 | ECDSA-SHA384 | 7ff31977972c224a76155d13b6d685e3 |
| CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) | CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE | 15 Nov 2023 | 28 Jan 2028 | ECDSA 384 | SHA256-RSA | 7fe530bf331343bedd821610493d8a1b |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of flow.horustek.pro. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| pro. | present | 33289 | 8 | Verified |
| horustek.pro. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 200 |
| Header | Value |
|---|---|
| strict-transport-security | max-age=31536000; includeSubDomains; preload |
| x-content-type-options | nosniff |
| x-frame-options | DENY |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://flow.horustek.pro/mcp | Verified | 200 | |
| http (plaintext) | http://flow.horustek.pro/mcp | HTTPS enforced | 301 | https://flow.horustek.pro/mcp |
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
get_book_pressure ~205
Read the spot order book of 30 deep Binance USDT pairs in one call, refreshed every 15 seconds: the share of the top five levels' size on the bid side (top5_imbalance, 0.5 = even), the bid/ask size ratio and the last 30 seconds of taker flow. sort=bid lists the most bid-heavy books first, sort=ask the most ask-heavy. 'measured' gives the rank correlation of top5_imbalance with the next minute's return over the last 30 days: a small, steady tilt below trading costs, useful as context or for timing an order, not as a signal. An agent cannot hold Binance's live streams; this is the book in one request. Free plans: 3 rows; TRADER / RapidAPI PRO and above: all 30.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | – |
| sort | string | – | – |
Structured output declared, but exposes no named fields.
No examples provided.
get_cortex ~67
Horus Cortex: the BTC market regime, trust score (0-100), active contradictions between evidence families, invalidation and breakout levels, and position-size multipliers by strategy type. Full: PRO / RapidAPI ULTRA; lower plans get regime, trust score and headline.
Input schema present but exposes no named parameters.
Structured output declared, but exposes no named fields.
No examples provided.
get_cross_asset ~105
BTC order flow side by side with US equities flow (SPY, QQQ) and crypto-linked stocks and ETFs (COIN, MSTR, IBIT): are crypto and stocks risk-on together, risk-off together, or diverging? When US markets are closed, says so and keeps BTC as the live gauge. Equity flow is an IEX sample. Full: TRADER / RapidAPI PRO; free plans get SPY and QQQ only.
Input schema present but exposes no named parameters.
Structured output declared, but exposes no named fields.
No examples provided.
get_crypto_flow ~90
Live order flow for one Binance spot pair: signal, direction, 30-second buy/sell delta in USD, order book depth ratio, large sells in the last 5 minutes, and the signal's measured hit rate. Use for "what is the market doing right now in X". Symbols like BTCUSDT, ETHUSDT, SOLUSDT.
| Name | Type | Req | Description |
|---|---|---|---|
| symbol | string | – | – |
Structured output declared, but exposes no named fields.
No examples provided.
get_derivatives ~110
Derivatives positioning for one of 10 majors: funding (per venue and OI-weighted), open interest and its 10/30-minute change, futures/spot volume vs its 7-day median, crowd long/short vs its 24h median, top-trader divergence, estimated liquidation levels, liquidations seen in the last 5 minutes. Full: PRO / RapidAPI ULTRA; lower plans get a BTCUSDT preview.
| Name | Type | Req | Description |
|---|---|---|---|
| symbol | string | – | – |
Structured output declared, but exposes no named fields.
No examples provided.
get_equity_flow ~87
Order flow for one US stock or ETF from the IEX feed (about 3% of US volume, a sample): signal, buy/sell ratio, delta, large IEX prints. Extreme verdicts are capped because of the sample size. Full: TRADER / RapidAPI PRO; free plans get SPY and QQQ.
| Name | Type | Req | Description |
|---|---|---|---|
| symbol | string | – | – |
Structured output declared, but exposes no named fields.
No examples provided.
get_flow_history ~98
Recent order-flow snapshots (every 15s) for a crypto pair with a summary: signal counts, price change, cumulative 30s delta. Use to see whether pressure is building or fading. minutes up to 60 (TRADER / RapidAPI PRO) or 1440 (PRO / RapidAPI ULTRA); free plans get the last 15 minutes.
| Name | Type | Req | Description |
|---|---|---|---|
| minutes | integer | – | – |
| symbol | string | – | – |
Structured output declared, but exposes no named fields.
No examples provided.
get_ignitions ~76
Volatility-breakout scanner across ~750 crypto assets, refreshed every minute: global regime and the assets with the highest ignition score (0-1). A ranking of breakout conditions, not a probability. Full: TRADER / RapidAPI PRO; free plans get the top 3.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | – |
Structured output declared, but exposes no named fields.
No examples provided.
get_market_overview ~88
One call for the crypto market: BTC climate, ignition regime, Cortex regime, and for 10 majors the composite score, derivatives positioning (crowd vs its 24h median, liquidation gravity), futures/spot activity and open interest across Binance, Bybit and OKX. Full: PRO / RapidAPI ULTRA; lower plans get a BTCUSDT preview.
Input schema present but exposes no named parameters.
Structured output declared, but exposes no named fields.
No examples provided.
get_recent_events ~112
What changed since your last check: liquidation cascades, strong flow signals, composite changes, Cortex regime changes, climate changes, ignition alerts, US session changes, new US trading halts. Pass the last event id you saw as since_id. types is a comma-separated filter. Full: TRADER / RapidAPI PRO; free plans get the last 3 events, 15 minutes late.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | – |
| since_id | integer | – | – |
| types | – | – | – |
Structured output declared, but exposes no named fields.
No examples provided.
get_service_status ~32
Freshness and uptime of every Horus data source. Check this if a tool returns data_stale. Free.
Input schema present but exposes no named parameters.
Structured output declared, but exposes no named fields.
No examples provided.
get_signal_ledger ~116
Point-in-time ledger: every signal Horus emitted for BTCUSDT, ETHUSDT or SOLUSDT between start and end (ISO dates, max 31 days), with the price and what the market did 1/5/15/30 minutes later. For backtesting. Full: TRADER / RapidAPI PRO; free plans get 20 signals from the last 24 hours.
| Name | Type | Req | Description |
|---|---|---|---|
| end | – | – | – |
| limit | integer | – | – |
| start | – | – | – |
| symbol | string | – | – |
Structured output declared, but exposes no named fields.
No examples provided.
get_track_record ~98
Measured hit rates of Horus signals at 1, 5, 15 and 30 minutes (window 30d or all), from every signal recorded live since August 2026. Pass a signal name (e.g. STRONG_BUY_PRESSURE) for just that signal. Use this to decide how much weight to give a reading. Free.
| Name | Type | Req | Description |
|---|---|---|---|
| signal | – | – | – |
| window | string | – | – |
Structured output declared, but exposes no named fields.
No examples provided.
get_us_market_session ~68
US equity market right now: session phase (pre-market, regular, after-hours, closed), holidays and early closes, next open and close in New York time, minutes to close, and currently active trading halts. Call this before reasoning about US stock trades. Free.
Input schema present but exposes no named parameters.
Structured output declared, but exposes no named fields.
No examples provided.
scan_market ~204
Scan about 190 Binance perpetual markets in one call and get a ranked list. preset is one of: buyers_in_control, sellers_in_control, volume_surge, breakout_candidates, crowded_funding, top_movers. Each row: price, 15m and 1h change, aggressive buy share, net taker flow in USD, volume surge, funding, ignition score, and, for the 30 pairs Horus records, the spot order book's tilt (spot_book) with its measured link to the next minute (spot_book_measured). Use it to find where to look before calling get_crypto_flow or get_derivatives on a specific market. Rankings of current conditions, not predictions. Free plans: 3 rows; TRADER / RapidAPI PRO and above: up to 100.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | – |
| min_volume_24h_usd | number | – | – |
| preset | string | – | – |
Structured output declared, but exposes no named fields.
No examples provided.
How do I install the pro.horustek/horus-flow-mcp server?
pro.horustek/horus-flow-mcp is a hosted endpoint at https://flow.horustek.pro/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
remote · flow.horustek.pro
claude mcp add --transport http pro-horustek-horus-flow-mcp 'https://flow.horustek.pro/mcp'
What is the pro.horustek/horus-flow-mcp server?
pro.horustek/horus-flow-mcp is listed in the public MCP registry as pro.horustek/horus-flow-mcp. Crypto order flow, cross-venue derivatives and US market context for AI agents, with a track record. This page covers its hosted endpoint (https://flow.horustek.pro/mcp).
Is the pro.horustek/horus-flow-mcp server safe to use?
pro.horustek/horus-flow-mcp scores 75 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the pro.horustek/horus-flow-mcp server expose?
pro.horustek/horus-flow-mcp exposes 15 tools: get_crypto_flow, get_flow_history, get_market_overview, get_derivatives, get_cortex, and 10 more. Their descriptions and schemas cost roughly 1,556 tokens of context every time the server is loaded.
Does the pro.horustek/horus-flow-mcp server require authentication?
No. We connected to pro.horustek/horus-flow-mcp without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the pro.horustek/horus-flow-mcp server still maintained?
pro.horustek/horus-flow-mcp is still listed as active in the MCP registry. We last reached this channel on 5 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.