Alpaca Trading API integration for Model Context Protocol (MCP)
Nothing to run from here
Horus Flow is installed from its publisher's own source and answers where it runs, so this marketplace is not in the path of a single call. There is no address here to send one to, and a panel that pretended otherwise would be showing you an answer we made up. Install it and call it from your own client — the Installation tab has the entry for each one.
96/100
tool-list score
15
tools declared
remote
at its publisher
—
calls last 7d
What it does
Crypto order flow, cross-venue derivatives and US market context for AI agents, with a track record.
Quickstart
# 1 — add it to Claude Code
claude mcp add --scope user --transport http horustek-horus-flow-mcp https://flow.horustek.pro/mcp
# 2 — ask your agent for something these tools do
# get_crypto_flow, get_flow_history, get_market_overview and 12 more
Horus Flow costs nothing on mcprush: there is no plan to choose here, no cap to set and nothing mcprush can bill you for.
Publisher
Installation
Where are you running it?
Every route below installs the same thing and ends at the same approval screen. Nothing here runs on your machine and nothing runs on ours: this server answers at its publisher’s own address, and what you install is the connection straight to it.
Claude Codedeclared by this listing
This is a public server: it answers at its publisher’s own address and this marketplace is not in the path. Claude Code registers it in one command; --scope user makes it available in every project. The transport below is http, as the publisher's own manifest declares it.
claude mcp add --scope user --transport http horustek-horus-flow-mcp https://flow.horustek.pro/mcpReconnect, or start a new session, and the tools appear in the model’s tool list.
Free on mcprush, and it answers at its publisher’s own address: this marketplace is not in the path, so there is no key of ours to hold and no card to add.
What it asks of you
Nothing is required, but it can take X-API-Key header (Your Horus Flow API key. Optional: without it the free tier applies.) if you want to set it.
What it writes
One config entry pointing straight at the publisher’s own address — this marketplace is not in the path, and nothing from this listing executes on your machine.
What you approve
15 tools, with what each one reads, writes and reaches shown before you agree — the same list on every route above. Read the tool surface.
Tool surface
What the model actually sees. Descriptions are diffed on every release — see version history.
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| symbol | string | no | — |
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| symbol | string | no | — |
| minutes | integer | no | — |
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.
No parameter schema on file.
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| symbol | string | no | — |
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.
No parameter schema on file.
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| limit | integer | no | — |
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_b
| Parameter | Type | Required | Notes |
|---|---|---|---|
| preset | string | no | — |
| limit | integer | no | — |
| min_volume_24h_usd | number | no | — |
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
| Parameter | Type | Required | Notes |
|---|---|---|---|
| sort | string | no | — |
| limit | integer | no | — |
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| signal | no | — | |
| window | string | no | — |
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| symbol | string | no | — |
| start | no | — | |
| end | no | — | |
| limit | integer | no | — |
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| since_id | integer | no | — |
| types | no | — | |
| limit | integer | no | — |
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.
No parameter schema on file.
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.
No parameter schema on file.
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| symbol | string | no | — |
Freshness and uptime of every Horus data source. Check this if a tool returns data_stale. Free.
No parameter schema on file.
Free
$0 forever
- Every tool — any call limit is its publisher’s, not ours
- No card, and mcprush charges nothing for it
- Runs at its publisher’s own address — this marketplace is not in the path
- Nothing to cap, because mcprush bills nothing
What counts against your monthly calls
| Tool | Unit | Calls used | Out of the allowance |
|---|
Nothing here is billable: mcprush charges nothing to install Horus Flow or to call it, at any volume.
Call allowance · this installenforced at the gateway
Monthly allowance, in calls
—
—
Alert at 80% · then the tool returns a normal MCP error
Used this month: —
ATool-list grade · score 96 / 100
Release 3.1.0 · scanned 28 Oct 2026
Graded from the tools this server lists, not from its source code.
Two independent axes, because powerful and malicious are different questions. The grade is threat only. The capability level is blast radius, and it is never a penalty on the grade — it is priced as one subtract-only term in the score, where you can see it.
Threat score100
Client score96
Findings0 threat · 0 capability
Capabilityminimal
Coveragemanifest
Verificationnot in this report
Surface digest9e48eb43268160998e93e216093e205e501a06ed10512b7a9d8a376f6dc53eb8
Score vectorthreat 100 → client 96
| Term | Level | What it prices | Points |
|---|---|---|---|
| capability-exposure | minimal | capability blast radius (minimal) — client exposure if the model is manipulated | −0 |
| coverage-honesty | manifest | inspection depth (manifest) — how much of the target the scan could see | −4 |
score = clamp(round(threatScore − E_cap − E_ver − E_cov), 0, 100). No model, no opinion, no network call at scoring time: the same methodology version against the same bytes always produces this number, and every line above is a field of the report rather than a summary of it.
What the scan could actually read
A grade is only as meaningful as its coverage, so the scanner publishes its own depth before it publishes its result.
The scan read each tool’s name, description, input schema and annotations exactly as the server listed them the last time it answered us; no code was reviewed. We ask the server again about once a month, and a list that changed is graded again.
Tool surfaceread
Implementation sourcenot available
Package metadatanot available
Live transportnot available
The implementation source was not read — this reflects the declared tool metadata only.
Capability — what it could do if the model were manipulated
Tags derived from each tool’s schema and the implementation, not from what the tool calls itself. minimal is the level these add up to.
| Tool | Capability tags | Why the tag was assigned |
|---|---|---|
| get_crypto_flow | untrusted-input | untrusted-input: declares openWorldHint: true (interacts with entities outside the server) |
| get_flow_history | untrusted-input | untrusted-input: declares openWorldHint: true (interacts with entities outside the server) |
| get_market_overview | untrusted-input | untrusted-input: declares openWorldHint: true (interacts with entities outside the server) |
| get_derivatives | untrusted-input | untrusted-input: declares openWorldHint: true (interacts with entities outside the server) |
| get_cortex | untrusted-input | untrusted-input: declares openWorldHint: true (interacts with entities outside the server) |
| get_ignitions | untrusted-input | untrusted-input: declares openWorldHint: true (interacts with entities outside the server) |
| scan_market | untrusted-input | untrusted-input: declares openWorldHint: true (interacts with entities outside the server) |
| get_book_pressure | untrusted-input | untrusted-input: declares openWorldHint: true (interacts with entities outside the server) |
| get_track_record | untrusted-input | untrusted-input: declares openWorldHint: true (interacts with entities outside the server) |
| get_signal_ledger | untrusted-input | untrusted-input: declares openWorldHint: true (interacts with entities outside the server) |
| get_recent_events | untrusted-input | untrusted-input: declares openWorldHint: true (interacts with entities outside the server) |
| get_us_market_session | untrusted-input | untrusted-input: declares openWorldHint: true (interacts with entities outside the server) |
| get_cross_asset | untrusted-input | untrusted-input: declares openWorldHint: true (interacts with entities outside the server) |
| get_equity_flow | untrusted-input | untrusted-input: declares openWorldHint: true (interacts with entities outside the server) |
| get_service_status | untrusted-input | untrusted-input: declares openWorldHint: true (interacts with entities outside the server) |
Toxic-flow graph
The lethal trifecta, checked as a graph rather than as a checklist: untrusted input, a sensitive source and an external sink have to meet before there is a path worth worrying about.
The public result for this release does not print the flow graph, so there is nothing to show here. That is not the same as "no paths were found": what the scan did read is above, under coverage.
Supply chain and provenance
Integrityfirst-seen
Surface digest9e48eb4326816099
Scanned2026-10-28
This is the first scan of this surface here, so there is nothing yet to compare it against.
Every result on this tab comes from one deterministic pass over the published package — offline, rule by rule, and auditable line by line above. Same methodology version, same bytes, same score.
Release history
This is an address its publisher runs: which release it serves is theirs to choose, so there is nothing here to pin. The history below is for reading; the current release on file is 3.1.0.
3.1.0
undated
latestNo release note was published with this version.
—
no reviews yet
Who can review
One review per account, from a signed-in account that does not publish this listing. Nothing else is asked — you can say what you think before you install it. Publishers can reply once per review, and a review can be edited or deleted by whoever wrote it.
Sign in to write one
Any signed-in account that does not publish Horus Flow can review it, once — before installing it or after. A review from an account that has installed it is marked as one.
No reviews yet
Nobody has reviewed this listing. The rating on the card is the mean of the reviews written here and nothing else, so there is no rating until somebody writes the first — which takes a signed-in account that does not publish it, and nothing else.