pro.horustek/horus-flow-mcp
pro.horustek/horus-flow-mcp
Is the pro.horustek/horus-flow-mcp MCP server down? No. It is up and needs auth (HTTP 403), probed 2026-11-15.
Crypto order flow, cross-venue derivatives and US market context for AI agents, with a track record.
needs auth probed 2026-11-15 · HTTP 403
The server needs auth, so these tool definitions were read from the publisher's open-source package pypi:horus-flow-mcp, started in a container with placeholder values and the network off, on 2026-11-15. Tool definitions do not depend on the token, so this is what an authorized user loads, unless the server hides tools by plan or role.
Streamable HTTP error: Error POSTing to endpoint: <!DOCTYPE html><html lang="en-US"><head><title>Just a moment...</title><meta http-equiv="Content-Type" content
- Endpoint
- https://flow.horustek.pro/mcp (streamable-http)
- Host
- flow.horustek.pro
- Of a 1M window
- 0.3 % of a 1M context window
- Getting access
- The server answers HTTP 403 with no WWW-Authenticate header and no OAuth metadata, so the publisher's documentation is the only guide.
Read from the server's public OAuth metadata, without a token. Method. - Repository
- https://github.com/horustechltd/horus-flow-mcp
- Registry
- active, updated 2026-10-23 · registry entry
- Changes
- 2 recorded, reachable in 1 of them. A row is added when the result, the tool count or the cost changes.
Compare this server with others.
More servers
Servers that mention horus.
- Chorus com.choruskeepsake/chorus · alive
- Chorus Research io.chorusresearch/chorus · needs auth
- Lumo by HorusBI br.com.horusbi/lumo · needs auth
- io.github.horustechltd/horus-flow-mcp · not found
- Chorus net.chorushq/chorus · needs auth
- Chorus Pay MCP by usefulapi io.usefulapi/chorus-pay · timeout
History
We add a row when the result changes. A server with no change keeps its last row.
| Probed | Result | Init | Tools | Claude | o200k |
|---|---|---|---|---|---|
| 2026-10-24 08:45 | needs auth | ||||
| 2026-10-17 06:20 | crashed on start |
Badge for the README
The result of the latest probe, the tool count and the token cost. The feed has an entry for every probe that changed them.
A mail when this server changes
Stops answering, comes back, tool set or cost changes. One confirmation mail first, a stop link in every mail.
For the publisher
- The server answers HTTP 403 to an unauthenticated initialize, so the probe cannot list its tools. That is correct for a private server. Some public servers answer initialize and tools/list without credentials and ask for auth on tool calls only; those get a token count here.
Fixed something? Probe it now, with the same steps as the daily run. This page updates with the next daily run.