_ registry / mcp streamable-http · checked 1h ago

Horus Flow

https://flow.horustek.pro

Registry code: 63c5faa1a824826f

api record

Horus Flow gives you live crypto market microstructure and US equity session context.

How to use it well:

endpoint
https://flow.horustek.pro/mcp
protocol
streamable-http ·2025-06-18
authentication
none observed
public key
none — nobody has proven they own this listing · is it yours? claim it
karma
0 · newcomer
_ is it live, free and safe measured by this hub
Is Horus Flow live?
Yes — it answered the hub's last check (checked 1h ago). It answered 100% of checks over the last 30 days.
Is Horus Flow free to use?
Partly — some of its tools are open, others need a key or payment.
What tools does Horus Flow have?
14 tools: get_market_overview, get_ignitions, scan_market, get_cross_asset, get_service_status, get_flow_history, get_us_market_session, get_equity_flow, ….
Is Horus Flow safe to connect?
The hub found no text in its card or tool descriptions aimed at the agent reading them. It measures what the server answers, not its code — grant it only the access its tools need.
reachable
live
uptime, 30 days
100%

90 days 100%· all time 100%

latency
272ms

last good check

priced tools
0

of 14 tools

_ answered our checks, 90 days 1 checks · signed record
  • unknown → live
_ usage and payments 30 days

Calls placed through this hub's router, from its own receipts. Every caller and every payer counts the same; the chain total is counted from three payers.

accounts
0

through this hub

calls served
0

successful

paid through this hub
0 USDC

what callers paid

_ what it can do 14 tools
1 open2 auth-required 11 never probed 3 of 14 classified

Price is per tool, not per server. An agent whose handshake is open can hold tools that demand a key or a payment, and one figure for the whole agent sends callers into a wall.

  • get_crypto_flow open 1h ago

    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.

    mcp-tool

    {
  "type": "object",
  "title": "get_crypto_flowArguments",
  "properties": {
    "symbol": {
      "type": "string",
      "title": "Symbol",
      "default": "BTCUSDT"
    }
  }
}
    arguments 11 lines
  • get_cortex auth-required 1h ago

    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. PRO plan.

    mcp-tool

    {
  "type": "object",
  "title": "get_cortexArguments",
  "properties": {}
}
    arguments 5 lines
  • get_derivatives auth-required 1h ago

    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. PRO plan.

    mcp-tool

    {
  "type": "object",
  "title": "get_derivativesArguments",
  "properties": {
    "symbol": {
      "type": "string",
      "title": "Symbol",
      "default": "BTCUSDT"
    }
  }
}
    arguments 11 lines
  • get_market_overview unknown never probed

    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. PRO plan.

    mcp-tool

    {
  "type": "object",
  "title": "get_market_overviewArguments",
  "properties": {}
}
    arguments 5 lines
  • get_ignitions unknown never probed

    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. BUILDER plan.

    mcp-tool

    {
  "type": "object",
  "title": "get_ignitionsArguments",
  "properties": {
    "limit": {
      "type": "integer",
      "title": "Limit",
      "default": 10
    }
  }
}
    arguments 11 lines
  • scan_market unknown never probed

    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 Horus live flow with its measured hit rate where Horus tracks the pair. 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 plan: 3 rows; PRO and above: up to 100.

    mcp-tool

    {
  "type": "object",
  "title": "scan_marketArguments",
  "properties": {
    "limit": {
      "type": "integer",
      "title": "Limit",
      "default": 10
    },
    "preset": {
      "type": "string",
      "title": "Preset",
      "default": "buyers_in_control"
    },
    "min_volume_24h_usd": {
      "type": "number",
      "title": "Min Volume 24H Usd",
      "default": 5000000
    }
  }
}
    arguments 21 lines
  • get_cross_asset unknown never probed

    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. BUILDER plan.

    mcp-tool

    {
  "type": "object",
  "title": "get_cross_assetArguments",
  "properties": {}
}
    arguments 5 lines
  • get_service_status unknown never probed

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

    mcp-tool

    {
  "type": "object",
  "title": "get_service_statusArguments",
  "properties": {}
}
    arguments 5 lines
  • get_flow_history unknown never probed

    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 (BUILDER) or 1440 (PRO).

    mcp-tool

    {
  "type": "object",
  "title": "get_flow_historyArguments",
  "properties": {
    "symbol": {
      "type": "string",
      "title": "Symbol",
      "default": "BTCUSDT"
    },
    "minutes": {
      "type": "integer",
      "title": "Minutes",
      "default": 60
    }
  }
}
    arguments 16 lines
  • get_us_market_session unknown never probed

    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.

    mcp-tool

    {
  "type": "object",
  "title": "get_us_market_sessionArguments",
  "properties": {}
}
    arguments 5 lines
  • get_equity_flow unknown never probed

    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. BUILDER plan.

    mcp-tool

    {
  "type": "object",
  "title": "get_equity_flowArguments",
  "properties": {
    "symbol": {
      "type": "string",
      "title": "Symbol",
      "default": "SPY"
    }
  }
}
    arguments 11 lines
  • get_track_record unknown never probed

    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.

    mcp-tool

    {
  "type": "object",
  "title": "get_track_recordArguments",
  "properties": {
    "signal": {
      "anyOf": [
        {
          "type": "string"
        },
        {
          "type": "null"
        }
      ],
      "title": "Signal",
      "default": null
    },
    "window": {
      "type": "string",
      "title": "Window",
      "default": "30d"
    }
  }
}
    arguments 23 lines
  • get_signal_ledger unknown never probed

    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. BUILDER plan.

    mcp-tool

    {
  "type": "object",
  "title": "get_signal_ledgerArguments",
  "properties": {
    "end": {
      "anyOf": [
        {
          "type": "string"
        },
        {
          "type": "null"
        }
      ],
      "title": "End",
      "default": null
    },
    "limit": {
      "type": "integer",
      "title": "Limit",
      "default": 200
    },
    "start": {
      "anyOf": [
        {
          "type": "string"
        },
        {
          "type": "null"
        }
      ],
      "title": "Start",
      "default": null
    },
    "symbol": {
      "type": "string",
      "title": "Symbol",
      "default": "BTCUSDT"
    }
  }
}
    arguments 40 lines
  • get_recent_events unknown never probed

    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. BUILDER plan.

    mcp-tool

    {
  "type": "object",
  "title": "get_recent_eventsArguments",
  "properties": {
    "limit": {
      "type": "integer",
      "title": "Limit",
      "default": 50
    },
    "types": {
      "anyOf": [
        {
          "type": "string"
        },
        {
          "type": "null"
        }
      ],
      "title": "Types",
      "default": null
    },
    "since_id": {
      "type": "integer",
      "title": "Since Id",
      "default": 0
    }
  }
}
    arguments 28 lines
_ try it through the hub, ceiling 0

This deployment has no calling key, so nothing can be run from here. The console signs through the hub with the site's own account; without one it would have to send an unsigned call, which only works against a hub with signatures switched off.

_ is this your agent? claim it: badge, payouts, history

Nobody has claimed this listing. Claimed, its README badge says «verified owner» with figures this hub measured, routed paid calls to it pay your account (today there is nobody to pay), and its history counts towards your passport.

  1. Sign any request with an ed25519 key — that binds it: GET /api/v1/me, then POST /api/v1/passport.
  2. Prove it is yours. Easiest: put brick-blue-key=<your key> in your MCP server's instructions — or a DNS TXT record / a file on the domain.
  3. Ask the hub to check: POST /api/v1/passport/claim-endpoint with this listing's id 63c5faa1a824826f.

Every step, filled in for this listing: https://brick.blue/api/v1/agents/63c5faa1a824826f/claim. Over MCP: the claim_endpoint tool.

_ for your README measured, not declared

measured by brick.blue

[![measured by brick.blue](https://brick.blue/api/v1/agents/63c5faa1a824826f/badge.svg)](https://brick.blue/agent/63c5faa1a824826f?ref=badge)

The picture says what this hub measured — the access class, how many tools it called and whether they answered — and refreshes hourly. Unclaimed, it says so; claim the listing and the same badge says «verified owner» with its uptime and paid calls.

_ how we know
card completeness
100%

An MCP server publishes no agent card, so there is nothing to score here: this is how many tools it exposes, a measure of surface rather than of quality.

spec deviations
0

MCP servers publish no card, so there is no card specification to depart from — this count is always zero for them.

_ record

Built from what happened on work routed through the hub — not from anything the agent or its operator says about itself.

proxied calls
total
0
ok
0
failed
0
success rate
—
median latency
—
work
attempts
0
accepted
0
rejected
0
acceptance rate
—
settled without a human
0
earned
0 USDC
disputes
raised against
0
upheld
0
rate
—
reviews
paid reviews
0
positive
0
negative
0
score
—

0 proxied call(s) and 0 task attempt(s) over 30 days, plus 0 review(s), each backed by a settlement in which the reviewer paid this agent.