LiquiLens — the Failure Radar
REMOTE · API.LIQUILENS.IN · SCANNED AUG 3
Bank and lender failure early warning, with the validated record served beside every claim.
Available components
How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score →
Endpoint Security66
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation not fully verified: no authorisation is required to call this server, and 13 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe. See how to fix → View diagnostics → Unverified
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
- DNSSEC is configured correctly; the domain's records validate against the full chain to the root. View diagnostics → Pass
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability74
- 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
- AI-judged instruction clarity (good).Pass
- Context-footprint check failed: tool/resource definitions use about 2439 tokens (~187/item across 13 items; 13 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management27
- Stability observed for 8 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Add this component to your MCP client. Where a client-specific snippet is available, pick your client below and copy it straight into your config; otherwise use the connection detail shown.
remote · api.liquilens.in
claude mcp add --transport http beepboop2025-liquilens https://api.liquilens.in/mcp
[mcp_servers.beepboop2025-liquilens] url = "https://api.liquilens.in/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"beepboop2025-liquilens": {
"type": "remote",
"url": "https://api.liquilens.in/mcp",
"enabled": true
}
}
} openclaw mcp add beepboop2025-liquilens --url https://api.liquilens.in/mcp --transport streamable-http
mcp_servers:
beepboop2025-liquilens:
url: "https://api.liquilens.in/mcp" {
"mcpServers": {
"beepboop2025-liquilens": {
"type": "http",
"url": "https://api.liquilens.in/mcp"
}
}
} The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 2 Aug 26 +2
- Schema quality: 2088 → 2439 ▼ functional
- The server now declares the “prompts” capability functional
- First check of Schema quality: 100 functional
- Schema quality: excellent → good functional
- New prompt “stress_evidence_pack” functional
- New prompt “institution_health_check” functional
- New prompt “failure_radar_briefing” functional
- Server version: 1.1.0 → 1.2.0 functional
- 1 Aug 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 17 to 20. That category is still filling its 30-day observation window: 5 days of observed history at the previous scan, 6 at this one. The score rises as the window fills, whether or not the server changes.
- 31 Jul 26 +3
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 30 Jul 26 0
- Schema quality: 1712 → 2038 ▼ functional
- Server version: 1.0.0 → 1.1.0 functional
- New tool “household_credit_board” functional
- New tool “corporate_transmission_board” functional
- 29 Jul 26 −1
- The server rewrote its instructions, which are the text every model session reads security
- Schema quality: excellent → good functional
- 28 Jul 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 3 to 7. That category is still filling its 30-day observation window: 1 days of observed history at the previous scan, 2 at this one. The score rises as the window fills, whether or not the server changes.
- 27 Jul 26 +10
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 26 Jul 26 54
First indexed and scored.
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 3 Aug 2026 · Probed https://api.liquilens.in/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=liquilens.in | CN=WE1,O=Google Trust Services,C=US | 4 Jul 2026 | 2 Oct 2026 | ECDSA 256 | ECDSA-SHA256 | 6f49bbdecc1ef5a10ef2dfba28cf73f0 |
| SANs: liquilens.in, *.liquilens.in | ||||||
| CN=WE1,O=Google Trust Services,C=US (CA) | CN=GTS Root R4,O=Google Trust Services LLC,C=US | 13 Dec 2023 | 20 Feb 2029 | ECDSA 256 | ECDSA-SHA384 | 7ff31977972c224a76155d13b6d685e3 |
| CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) | CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE | 15 Nov 2023 | 28 Jan 2028 | ECDSA 384 | SHA256-RSA | 7fe530bf331343bedd821610493d8a1b |
DNSSEC secure
Validation of api.liquilens.in. — Secure
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| in. | present | 10094 | 13 | Verified |
| liquilens.in. | present | 2371 | 13 | Verified |
| api.liquilens.in. | Verified address RRset verified with the apex keys |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 200 |
| Header | Value |
|---|---|
| strict-transport-security | max-age=31536000; includeSubDomains; preload |
| content-security-policy | default-src 'none'; style-src 'unsafe-inline'; img-src 'self' data:; base-uri 'none'; form-action 'none'; frame-ancestors 'none'; |
| x-content-type-options | nosniff |
| x-frame-options | DENY |
| referrer-policy | strict-origin-when-cross-origin |
| permissions-policy | camera=(), microphone=(), geolocation=() |
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://api.liquilens.in/mcp | Verified | 200 | |
| http (plaintext) | http://api.liquilens.in/mcp | HTTPS enforced | 301 | https://api.liquilens.in/mcp |
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability.
corporate_transmission_board Corporate Transmission board (US) ~260
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.
| Name | Type | Req | Description |
|---|---|---|---|
| full | boolean | — | also return method_note, thresholds and per-leg basis prose (larger payload); default false |
No output schema declared.
No examples provided.
evidence_europe Validation record: European case files ~144
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.
| Name | Type | Req | Description |
|---|---|---|---|
| slug | string | — | optional kebab-case case-file slug, e.g. 'credit-suisse'; omit for all seven summaries |
No output schema declared.
No examples provided.
evidence_india Validation record: India backtest ~75
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.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
evidence_institution Validation record: one Indian replay ~115
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.
| Name | Type | Req | Description |
|---|---|---|---|
| slug | string | yes | kebab-case slug of a replayed institution, e.g. 'dhfl' or 'global-trust-bank' |
No output schema declared.
No examples provided.
evidence_markets Validation record: all markets ~93
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.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
evidence_us Validation record: US watchlist backtest ~198
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.
| Name | Type | Req | Description |
|---|---|---|---|
| include_trajectories | boolean | — | also return per-quarter score series for the marquee replays (large payload); default false |
No output schema declared.
No examples provided.
failure_radar_board Failure Radar board (India) ~146
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.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
failure_radar_institution Failure Radar institution dossier ~116
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.
| Name | Type | Req | Description |
|---|---|---|---|
| slug | string | yes | kebab-case institution slug from a failure_radar_board row, e.g. 'esaf-sfb' |
No output schema declared.
No examples provided.
forward_odds Markov forward odds per layer ~118
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.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
household_credit_board Household Credit board (US) ~238
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.
| Name | Type | Req | Description |
|---|---|---|---|
| full | boolean | — | also return method_note, thresholds, labels and full sparklines (larger payload); default false |
No output schema declared.
No examples provided.
rbi_supervisory_tape RBI supervisory tape ~79
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.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
universe_search RBI NBFC register search ~162
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.
| Name | Type | Req | Description |
|---|---|---|---|
| classification | string | — | exact RBI classification as it appears in the register, e.g. 'MFI' or 'HFC' |
| layer | string | — | Scale Based Regulation layer filter |
| limit | integer | — | maximum rows to return (default 20, capped at 50) |
| q | string | — | case-insensitive substring of the registered name or CIN |
No output schema declared.
No examples provided.
verify_published_record Verify the published record ~103
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.
| Name | Type | Req | Description |
|---|---|---|---|
| stream | string | — | ledger stream name to verify (default 'mfi_watchlist') |
No output schema declared.
No examples provided.