# 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.

- Trust score: 75/100 (medium)
- Change this week: +3
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-05

## Components

- remote · `flow.horustek.pro`: 75/100 (this document), [markdown](https://verifymcp.io/servers/pro-horustek-horus-flow-mcp/flow.md), [page](https://verifymcp.io/servers/pro-horustek-horus-flow-mcp/flow)

## Channel facts

- Endpoint: `https://flow.horustek.pro/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `3.1.0`

## Trust breakdown

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. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-11-05.

- **Endpoint Security**: 80/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - No authorisation is required to call this server. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one.
  - HTTPS is enforced; there's no plaintext access path.
  - The HSTS (Strict-Transport-Security) header is present.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 64/100
  - AI-judged instruction clarity (good).
  - 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.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 43/100
  - Stability observed for 13 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 71/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 0% of tool parameters carry a description.
  - Structured output schemas are declared (100% of tools); any adoption earns full credit.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 15 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 16 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.

## Install

### 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.

### Claude

```bash
claude mcp add --transport http pro-horustek-horus-flow-mcp 'https://flow.horustek.pro/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "pro-horustek-horus-flow-mcp": {
      "url": "https://flow.horustek.pro/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "pro-horustek-horus-flow-mcp": {
      "type": "http",
      "url": "https://flow.horustek.pro/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.pro-horustek-horus-flow-mcp]
url = "https://flow.horustek.pro/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "pro-horustek-horus-flow-mcp": {
      "type": "remote",
      "url": "https://flow.horustek.pro/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add pro-horustek-horus-flow-mcp --url 'https://flow.horustek.pro/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  pro-horustek-horus-flow-mcp:
    url: "https://flow.horustek.pro/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "pro-horustek-horus-flow-mcp": {
      "Transport": "http",
      "Url": "https://flow.horustek.pro/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add pro-horustek-horus-flow-mcp -t streamable-http -u 'https://flow.horustek.pro/mcp'
```

### Other

```json
{
  "mcpServers": {
    "pro-horustek-horus-flow-mcp": {
      "type": "http",
      "url": "https://flow.horustek.pro/mcp"
    }
  }
}
```

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-11-04 (score 75, +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.

### 2026-11-02 (score 74, +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.

### 2026-10-31 (score 73, +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.

### 2026-10-28 (score 72, +1)

- [security] 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
- [functional regression] Schema quality: 1621 → 1889
- [functional] New tool “get_book_pressure”

### 2026-10-25 (score 71, +1)

- [security] 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
- [functional regression] Schema quality: pass → fail

### 2026-10-24 (score 70, 0)

- [functional improvement] Stability: unverified → 0.03

### 2026-10-23 (score 70)

First indexed and scored.

## MCP tools (15)

### `get_crypto_flow` (~90 tokens)

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.

Input parameters:

- `symbol` (string)

### `get_flow_history` (~98 tokens)

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.

Input parameters:

- `minutes` (integer)
- `symbol` (string)

### `get_market_overview` (~88 tokens)

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.

### `get_derivatives` (~110 tokens)

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.

Input parameters:

- `symbol` (string)

### `get_cortex` (~67 tokens)

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.

### `get_ignitions` (~76 tokens)

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.

Input parameters:

- `limit` (integer)

### `scan_market` (~204 tokens)

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.

Input parameters:

- `limit` (integer)
- `min_volume_24h_usd` (number)
- `preset` (string)

### `get_book_pressure` (~205 tokens)

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.

Input parameters:

- `limit` (integer)
- `sort` (string)

### `get_track_record` (~98 tokens)

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.

Input parameters:

- `signal`
- `window` (string)

### `get_signal_ledger` (~116 tokens)

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.

Input parameters:

- `end`
- `limit` (integer)
- `start`
- `symbol` (string)

### `get_recent_events` (~112 tokens)

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.

Input parameters:

- `limit` (integer)
- `since_id` (integer)
- `types`

### `get_us_market_session` (~68 tokens)

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.

### `get_cross_asset` (~105 tokens)

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.

### `get_equity_flow` (~87 tokens)

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.

Input parameters:

- `symbol` (string)

### `get_service_status` (~32 tokens)

Freshness and uptime of every Horus data source. Check this if a tool returns data_stale. Free.

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/pro-horustek-horus-flow-mcp/flow#diagnostics

## Score history

- 2026-11-05: 75
- 2026-11-04: 75
- 2026-11-03: 74
- 2026-11-02: 74
- 2026-11-01: 73
- 2026-10-31: 73
- 2026-10-30: 72
- 2026-10-29: 72
- 2026-10-28: 72
- 2026-10-27: 71
- 2026-10-26: 71
- 2026-10-25: 71
- 2026-10-24: 70
- 2026-10-23: 70

## Common questions

### 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.

## Links

- Remote endpoint: https://flow.horustek.pro/mcp
- Repository: https://github.com/horustechltd/horus-flow-mcp
- Changelog RSS feed: https://verifymcp.io/servers/pro-horustek-horus-flow-mcp/flow.xml
- Changelog JSON feed: https://verifymcp.io/servers/pro-horustek-horus-flow-mcp/flow.json
- HTML version of this page: https://verifymcp.io/servers/pro-horustek-horus-flow-mcp/flow
