mcpbeat

LiquiLens — the Failure Radar MCP Server

io.github.beepboop2025/liquilens
answering

LiquiLens — the Failure Radar is answering right now. Last checked 7 min ago. It exposes 13 tools.

Bank and lender failure early warning, with the validated record served beside every claim.

The linked repository no longer exists on GitHub — it was deleted or made private.

Uptime history 40 hours of history · worst hour 75%
40 hours agonow
98.9%
Uptime 24h
90 of 91 checks
13
Tools
read from the server
360 ms
Response time
average over 24h
open, no key
Access
streamable-http

Connect this server

Endpoint below is the one we actually reach during checks — not the one copied from a README. Last verified 7 min ago.

run in your terminal
claude mcp add liquilens --transport http https://api.liquilens.in/mcp
~/Library/Application Support/Claude/claude_desktop_config.json
{
  "mcpServers": {
    "liquilens": {
      "url": "https://api.liquilens.in/mcp"
    }
  }
}
~/.codex/config.toml
[mcp_servers.liquilens]
url = "https://api.liquilens.in/mcp"
.cursor/mcp.json
{
  "mcpServers": {
    "liquilens": {
      "url": "https://api.liquilens.in/mcp"
    }
  }
}
.vscode/mcp.json
{
  "mcpServers": {
    "liquilens": {
      "url": "https://api.liquilens.in/mcp"
    }
  }
}

Available tools 13

Read directly from the server with tools/list, grouped by what they act on. If a tool disappears, we record the date.

evidence
evidence_europe
Read the seven European case files replayed point-in-time through the unrecalibrated Indian lenses: Credit Suisse, Banco Popular, Northern Rock and Banco Espirito Santo (failed); Deutsche Bank and Monte dei Paschi (stressed survivors); UBS (control). Every figure is audited against the primary filing it cites. Without arguments, returns all seven verdict summaries; pass slug for one full case file with its per-quarter table. These are case studies with citations, deliberately not a cohort — there is no European recall percentage to quote.
evidence_india
Read the full Indian crisis record: 48 institutions replayed point-in-time from vetted public filings across two decades, with per-institution verdicts, lead times in months, uncertainty intervals and the rigor artifacts — misses and false alarms included, never trimmed. Takes no arguments. Use evidence_institution for one institution's complete replay.
evidence_institution
Read one Indian institution's complete point-in-time crisis replay from the 48-institution validation record: the scored quarterly trajectory, the sourced dossier rows behind each score, first-alert bookkeeping (when each lens first fired relative to the failure), and the plain verdict line — hit, miss or false alarm. Call evidence_india first to list the replayed institutions and their slugs.
evidence_markets
Read the validation record's headline for each market: India (48-institution point-in-time backtest), United States (industry-wide watchlist backtest over 552 failures), and Europe (named audited case files, deliberately no cohort claim). Takes no arguments. Start here when asked whether LiquiLens is validated, then drill into evidence_india, evidence_us or evidence_europe for the full record behind each headline.
evidence_us
Read the US bank validation record: every FDIC-insured bank scored quarterly from free call-report data, replayed against all 552 receivership failures since 2008 — recall 72.8% at a 21.7-month median lead, AUC 0.854. Includes the marquee replays (SVB, Signature, First Republic, both 2026 catches), the fraud-driven miss kept in full view, and the seven named 2023-2026 misses, published the week they failed; the 2026 scoreboard reads 2 of 4 flagged a year early. Read the semantics before quoting: the flag is a budgeted watchlist (top decile per quarter), not an institution-level verdict, so report the budget beside the recall and the misses beside the hits.
failure
failure_radar_board
Read the live Failure Radar board for India: one row per institution with a fresh vetted dossier — banks, small finance banks, co-operative banks, NBFCs, MFIs and HFCs. Each row carries a corpus-calibrated failure PD term structure (12/24/36 months), a disclosure score, RBI PCA/SAF action-zone status, a funding-fragility index, market-implied distance-to-default for listed names, and a watchlist tier assigned under a published rule. Takes no arguments. Call this first to discover institution slugs, then failure_radar_institution for one name's full dossier. Outputs are research screens, not credit ratings.
failure_radar_institution
Read the full radar dossier for one Indian institution: per-quarter score and failure-PD trajectory with named drivers, RBI PCA/SAF headroom history, the funding-fragility read, forensic-screen evidence, and the market reading for listed names. Call failure_radar_board first to discover valid slugs; an institution without a vetted dossier is reported absent, never scored from memory.
corporate
corporate_transmission_board
Answers ONE question: whether FUNDING stress is reaching nonfinancial FIRMS — not banks (failure_radar_board), not households (household_credit_board), not money-market plumbing (the Seiche sibling server). Read the Corporate Transmission board for the US basin: is funding stress reaching nonfinancial firms? Channels from free public data (FRED keyless, AOUSC bankruptcy filings): the nonfinancial CP market (spread over bills + the book failing to roll), bank credit lines (C&I revolver drawdown + SLOOS standards tightening), the real-economy confirmation (claims, capex orders, inventories, openings, business bankruptcies), and a balance-sheet context channel capped at WATCH. Serves a TRANSMISSION verdict (counted co-occurrence of the funding and real sides) and a divergence read against the sibling bond board's served regime. Channels that cannot be read are listed in cannot_see, never reported as calm. Display-only: feeds no institution score and no watchlist tier. Returns ~4KB slim by default; pass full:true for thresholds, per-leg basis and method prose.
forward
forward_odds
Read the Markov forward odds for every state-bearing public-signal layer: the daily CALM/WATCH/ALARM state chain counted into a transition matrix, plus empirical k-day reach odds from today's state ('given today's WATCH, historical odds of ALARM within 5/20 days'). Counted, never fitted. The withhold discipline is the point: odds are withheld until a layer has 60 observed days, and the accrued count is stated — absence is never precision. Takes no arguments. Display-only context, never a state driver.
household
household_credit_board
Answers ONE question: whether stress is reaching US HOUSEHOLD balance sheets — not firms (corporate_transmission_board), not banks (failure_radar_board), not money-market plumbing (the Seiche sibling server). Read the Household Credit board: is stress transmitting through US household balance sheets? From free public data (FRED keyless): Fed quarterly delinquency and charge-off legs (card, consumer, mortgage, card charge-offs — level vs each leg's own trailing decade AND the yoy direction; falling never scores), G.19 revolving-credit velocity (two-sided — both tails historically meant stress), and the debt-service ratio as unscored context. The transmission thesis runs household -> corporate -> institution: this board confirms what the funding boards lead. Channels that cannot be read are listed in cannot_see, never reported as calm. Display-only: feeds no institution score and no watchlist tier. Returns ~4KB slim by default; pass full:true for thresholds, method prose and full sparklines.
rbi
rbi_supervisory_tape
Read the latest RBI enforcement and supervisory actions — monetary penalties, licence cancellations and supervisory directions — parsed from rbi.org.in press releases, newest first, each item carrying the RBI's own source URL. Takes no arguments. When no tape snapshot exists on the deployment, says so in a stated note instead of returning silent emptiness.
universe
universe_search
Search the RBI's official register of NBFCs (9,000+ entries) by name or CIN substring, optionally filtered by RBI classification and Scale Based Regulation layer. Returns matching register rows verbatim from the public record: official name, CIN, classification and layer. Give at least one of q, classification or layer; an empty q with a filter browses that whole slice.
verify
verify_published_record
Independently verify the as-published record for a ledger stream: recompute the hash-chained point-in-time commitments, check signatures and anchors where enabled, server-side, and return the verifier's verdict verbatim — even when unflattering; that is the point. Use this to check whether the published early-warning track record is tamper-evident and intact.

Endpoints

URLTransportStateLatencyChecked
https://api.liquilens.in/mcp streamable-http answering 384 ms 7 min ago

LiquiLens — the Failure Radar — questions

Answers built from our own checks of this server.

What can LiquiLens — the Failure Radar do?
It exposes 13 tools, read directly from the server on our last check. Among them: corporate_transmission_board, evidence_europe, evidence_india, evidence_institution, evidence_markets, evidence_us and 7 more. The full list with descriptions is on this page — we take it from the server itself via tools/list, not from a README. How MCP servers expose tools in the first place →
What is LiquiLens — the Failure Radar mostly used for?
Its tools cluster around evidence and failure. That is what this server is built to work with — the grouping comes from the actual tool names, not from a category we assigned.
Is LiquiLens — the Failure Radar working right now?
We send a real MCP handshake every 15 minutes. Over the last 24 hours 90 of 91 checks got a reply (98.9%), average response time 360 ms. The bar chart above shows every period we have measured.
Is LiquiLens — the Failure Radar still maintained?
The linked repository no longer exists on GitHub — it was deleted or made private. We show this because it changes what you can expect: an unmaintained server may keep answering for months and then stop without warning.
How do I connect LiquiLens — the Failure Radar?
Copy the ready config from this page — we generate it for Claude Code, Claude Desktop, Codex, Cursor and VS Code, each with the file path that client actually reads. It is a remote server, so there is nothing to install — the client connects to the address.
Does LiquiLens — the Failure Radar need an API key?
No. LiquiLens — the Failure Radar completed a full MCP handshake with us as an anonymous client and listed its tools without asking for anything. All 13 of them are readable on this page. This is what we observed, not what the docs claim.
How fast is LiquiLens — the Failure Radar?
It answers our handshake in 360 ms on average, which is faster than 39% of all working MCP servers we measure. The comparison comes from our own checks across the whole registry, every 15 minutes.