Fahali MCP Server

Fahali MCP server exists for a simple reason — assistants are far more useful when they can act on Fahali directly instead of describing what you should do. Real-time market-risk intelligence for AI agents — 18 engines, crypto + US equities. Not advice.

What you get

Coverage is crypto 24/7 and US equities and ETFs during market hours. Live coverage and engine counts are reported at GET /api/public/stats rather than asserted here, because the active set changes.

• Signed receipts. — Every verdict carries a SHA-256 receipt and a provenance root. When your agent quotes Fahali, it can attach proof of what was said and when
• Honest absence. — Missing data says so. Quiet markets resolve as unresolved, never as wins. Some tools abstain by design: whale tracking returns an explicit "no on-chain data source" rather than inventing positions

Setting it up

Being a remote server, there is no local install. You register the endpoint with your client, authorise it once, and the tools appear.

What the assistant can call

Once Fahali is connected, these are the calls the assistant has available:

• fahali_get_market_verdict — Per-symbol verdict: direction, confidence, reasoning, expected move, horizon
• fahali_get_lead_time — The verified, outcome-scored lead-time record (public)
• fahali_get_72h_forecast — Probabilistic 72h forecast with an uncertainty cone, Brier-scored
• fahali_get_flash_crash_risk — Flash-crash precursor strength, or an explicit abstention
• fahali_get_track_record_scorecard — The judged record with per-horizon base rates and lift
• fahali_get_contagion_map — Cross-asset tail-dependence and correlated clusters
• fahali_get_dark_pool_activity — Off-tape absorption, labeled as a microstructure proxy
• fahali_get_capital_flow — Order-flow imbalance proxy (no fabricated institutional/retail split)
• fahali_get_market_regime — Current regime read
• fahali_run_shock_test — Stress-test a portfolio against a scenario

Configuration and credentials

You will need one environment variable: FAHALI_API_KEY. The server will not start without them, which is usually why the tools fail to appear on a first run. Keep credentials in your client's env block or a secrets manager rather than in a file you might commit.

Before you rely on it

• Your data travels to the provider's service, so the usual questions apply about what you send and what they retain.
• With 10 tools registered it takes up a noticeable share of the context window; turn it off in projects that never touch Fahali.
• Missing credentials fail quietly in some clients — if no tools show up, check the environment block first.
• MCP clients confirm each tool call by default. Leave that on until you have watched what the fahali mcp server does with a few real requests.

Choosing this one

Among the developer tooling options, the useful question is rarely "what can it do" but "what does it cost you to run" — permissions, credentials, and how much of your context its toolset consumes. Fahali's toolset — fahali_get_market_verdict, fahali_get_lead_time, fahali_get_72h_forecast and 7 more — is a fair guide to whether it matches your workflow. It is maintained by com.fahaliai; worth a glance at recent repository activity before you build anything load-bearing on it.

SyncDev reviews every entry in this directory against the project's own documentation before publishing, and revisits them as servers change.