Fahali MCP server

What it does

Fahali exposes financial risk assessment tools for AI agents, covering portfolio risk, stress testing, flash-crash precursors, and market verdicts for crypto and US equities. It provides read-only market intelligence with signed receipts and a public track record of lead times scored against actual outcomes, designed for agents that need to interpret price data in the context of capital risk.

• Run a pre-trade risk check before opening a position by querying flash-crash precursors, market verdicts, and the lead-time record for that signal.
• Stress-test a portfolio against hypothetical market scenarios to understand potential losses under different conditions.
• Monitor contagion and tail-dependence across asset clusters to understand correlated crash risk and cross-asset exposure.

Tools this server exposes

Tool	Does
fahali_get_market_verdict	Returns per-symbol verdict including direction, confidence, reasoning, expected move, and time horizon.
fahali_get_lead_time	Returns the verified, outcome-scored lead-time record showing median hours ahead of actual moves, publicly available.
fahali_get_forecast	Returns probabilistic forecast over the signal's registered horizon with an uncertainty cone and Brier score.
fahali_get_flash_crash_risk	Returns flash-crash precursor strength for a symbol or an explicit abstention if data is unavailable.
fahali_get_track_record_scorecard	Returns the judged record with per-horizon base rates and lift for each analytical engine.
fahali_get_contagion_map	Returns cross-asset tail-dependence and correlated clusters.
fahali_get_microstructure_proxy	Returns absorption inferred from public microstructure data only.
fahali_get_capital_flow	Returns order-flow imbalance proxy without fabricated institutional or retail attribution.
fahali_get_market_regime	Returns the current market regime classification.
fahali_run_shock_test	Stress-tests a portfolio against a specified scenario and returns potential losses.

Before you enable it

An MCP server runs with whatever access you give it. Start with a development account rather than production, and check which tools the server exposes before you let an agent call them unattended.