LiquiLens — the Failure Radar
REMOTE · API.LIQUILENS.IN · SCANNED SEP 20
Free bank research: NPA reconciliation, small finance banks, UCBs and cited evidence limits.
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 → Why this is hard to 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 22 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 Usability87
- 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 2349 tokens (~106/item across 22 items; 22 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 Management100
- No destabilizing schema changes in the last 30 days.Pass
Tool Coverage89
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 67% of tool parameters carry a description.Partial
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 22 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 23 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a current MCP spec version (2026-07-28).Pass
How do I install the LiquiLens — the Failure Radar MCP server?
LiquiLens — the Failure Radar is a hosted endpoint at https://api.liquilens.in/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
remote · api.liquilens.in
claude mcp add --transport http beepboop2025-liquilens 'https://api.liquilens.in/mcp'
{
"mcpServers": {
"beepboop2025-liquilens": {
"url": "https://api.liquilens.in/mcp"
}
}
} {
"servers": {
"beepboop2025-liquilens": {
"type": "http",
"url": "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": {
"Transport": "http",
"Url": "https://api.liquilens.in/mcp"
}
}
} assistant mcp add beepboop2025-liquilens -t streamable-http -u '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.
- 9 Sept 26 −1
- Tool coverage: 78% → 67% ▼ functional
- New tool “research_network” functional
- 5 Sept 26 +1
- The server rewrote its instructions, which are the text every model session reads security
- Tool “corporate_transmission_board” rewrote its description, which is the text the model reads security
- Tool “evidence_europe” rewrote its description, which is the text the model reads security
- Tool “evidence_india” rewrote its description, which is the text the model reads security
- Tool “evidence_institution” rewrote its description, which is the text the model reads security
- Tool “evidence_us” rewrote its description, which is the text the model reads security
- Tool “failure_radar_board” rewrote its description, which is the text the model reads security
- Tool “failure_radar_institution” rewrote its description, which is the text the model reads security
- Tool “forward_odds” rewrote its description, which is the text the model reads security
- Tool “household_credit_board” rewrote its description, which is the text the model reads security
- Tool “institution_review_packet” rewrote its description, which is the text the model reads security
- Tool “universe_search” rewrote its description, which is the text the model reads security
- Tool “verify_published_record” rewrote its description, which is the text the model reads security
- Tool coverage: 100% → 78% ▼ functional
- Schema quality: 167 → 107 ▲ functional
- New prompt “bank_asset_quality_brief” functional
- Server version: 1.7.0 → 1.8.0 functional
- New tool “bank_asset_quality_review” functional
- New tool “bank_npa_reconciliation” functional
- New tool “banking_specialisation_coverage” functional
- 2 Sept 26 0
- Tool “failure_radar_board” rewrote its description, which is the text the model reads security
- 26 Aug 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 25 Aug 26 0
- Stability: 0.97 → pass security
- 24 Aug 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 93 to 97. That category is still filling its 30-day observation window: 28 days of observed history at the previous scan, 29 at this one. The score rises as the window fills, whether or not the server changes.
- 15 Aug 26 0
- The server now declares the “resources” capability functional
- MCP protocol: Implements a current MCP spec version (2026-07-28). functional
- MCP protocol version: 2025-11-25 → 2026-07-28 functional
- Server version: 1.5.0 → 1.7.0 functional
- New tool “latest_article” functional
- 11 Aug 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
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 20 Sept 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 | 1 Sept 2026 | 30 Nov 2026 | ECDSA 256 | ECDSA-SHA256 | a675bed3665aa10c0e03a98c6dff0acd |
| 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 |
Background: What to check on a remote MCP endpoint →
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=() |
Background: How OAuth 2.1 works in the 2026 MCP spec →
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. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
bank_asset_quality_review NPA, SFB and cooperative-bank review ~105
Read a bank's sourced GNPA/NNPA history, percentage-point changes, distinct PCR definitions, capital scope and disclosed NPA stock reconciliation. SFB and UCB review questions are tailored to their funding and supervisory context. Free; no new score, credit approval or execution authority.
| Name | Type | Req | Description |
|---|---|---|---|
| as_of | string | – | Optional end-of-day evidence cutoff; YYYY-MM-DD, not in the future. |
| include_history | boolean | – | – |
| slug | string | yes | – |
No output schema declared.
No examples provided.
bank_npa_reconciliation Reconcile a disclosed NPA movement ~69
Reconcile a caller-supplied closed NPA movement table: opening stock plus additions less classified reductions equals closing stock. Keeps write-offs, sales, upgrades and cash recoveries distinct. Free arithmetic check; does not authenticate the input or classify individual loans.
| Name | Type | Req | Description |
|---|---|---|---|
| statement | object | yes | – |
No output schema declared.
No examples provided.
banking_specialisation_coverage Indian banking evidence coverage ~77
Discover covered Indian commercial, small finance and urban cooperative banks. Separates observed, stale, historical and absent evidence. Free read-only research; this is not a census or rating.
| Name | Type | Req | Description |
|---|---|---|---|
| as_of | string | – | Optional end-of-day evidence cutoff; YYYY-MM-DD, not in the future. |
| sector | string | – | – |
No output schema declared.
No examples provided.
corporate_transmission_board Corporate Transmission board (US) ~96
Answers ONE question: is US funding stress reaching nonfinancial firms? Use household_credit_board for households. CP, bank credit lines and real-economy confirmation; cannot_see preserves gaps. Seiche context never enters regime or transmission. Display-only; no institution score or tier. full:true adds methods.
| 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.
crypto_exposure_board Bank/crypto exposure register ~67
Read the compact cited bank/crypto exposure register: disclosed quantum, stablecoin and venue links, exposure channels, Undertow run-risk cross-read and compound flags. Detailed disclosures stay on the public REST detail route. Takes no arguments; display-only, never an institution score or investment advice.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
crypto_regime_board Crypto Regime board (BTC/ETH) ~72
Read the compact BTC/ETH Crypto Regime board: current change-point state, log-SR statistic, last shift, observation count and the display-only cross-read against disclosed bank exposure. Time-series paths stay on the public REST detail route. Takes no arguments; feeds no institution score and is not investment advice.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
evidence_europe Historical evidence: European named case files ~85
Read seven cited European retrospective case files through unrecalibrated Indian lenses. Named case studies, not a cohort: no European recall percentage to quote. Omit slug for summaries, or supply a returned slug for a full quarterly case file.
| 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 Historical diagnostic: India construction-PIT replay ~59
Read the 48-institution Indian construction-PIT crisis diagnostic, including misses and false alarms. Uses publication clocks where present and a +60-day filing-lag proxy otherwise; overwritten amendments are unreconstructable. evidence_institution returns a full replay.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
evidence_institution Historical diagnostic: one Indian case replay ~83
Read a sourced Indian construction-PIT quarterly replay, lens alert timing and hit/miss/false-alarm verdict. Use evidence_india for exact slugs. Filing-availability proxies do not establish a validated backtest.
| 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 Historical evidence status: all markets ~90
Read the historical-evidence headline for each market: India (48-institution construction-PIT diagnostic), United States (industry-wide current-amended-vintage diagnostic), and Europe (named cited case files, deliberately no cohort claim). Takes no arguments. Start here when asked what LiquiLens has tested, 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 Historical diagnostic: US construction-PIT watchlist ~97
Read US bank current-amended-vintage diagnostics and named replays, including misses. Not a validated point-in-time backtest. Report the quarterly top-decile budgeted watchlist beside recall, uncertainty and lead times; it is not an individual-bank verdict. include_trajectories:true adds histories.
| 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) ~76
Read fresh-vetted Indian lender rows with failure PDs, disclosure, PCA/SAF, funding and listed-name DD. Scalar market_dd requires tier authority; display-only DD retains clocks and refusal reasons in market_dd_evidence. Discover slugs here, then failure_radar_institution. Research screen, not a credit rating.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
failure_radar_institution Failure Radar institution dossier ~86
Read one Indian lender dossier: quarterly PDs and drivers, PCA/SAF headroom, funding, forensic and listed-market evidence. Discover slugs with failure_radar_board. Uncovered institutions remain 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 ~57
Read counted Markov transitions and empirical 5/20-day reach odds. Odds are withheld until 60 observed days; counts stay visible and absence is never precision. Historical frequencies are not calibrated forecasts. Display-only, 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) ~97
Answers ONE question: is stress reaching US household credit? Use corporate_transmission_board for firms. Delinquency, charge-offs, revolving credit and unscored debt-service context; gaps stay in cannot_see. Display-only; no institution score or watchlist tier. full:true adds methods and histories.
| 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.
institution_review_packet Institution review packet (India) ~83
Build a compact cited human review packet from canonical fresh-vetted Indian radar records. Exact slug or uniquely normalized full name only; no fuzzy matching or new score. Preserves stale/dark gaps and validation hashes. Its content hash detects alteration; it is not attestation or a publication-time proof.
| Name | Type | Req | Description |
|---|---|---|---|
| institution | string | yes | exact Failure Radar slug or full institution name |
No output schema declared.
No examples provided.
latest_article Latest evidence-led article ~60
Read today's exact full-text LiquiLens editorial: current institution-risk analysis when the evidence moved, or a labelled historical replay when it did not. Returns the canonical headline, dek, Markdown, evidence clock and passing publication receipt; quote it without regenerating facts.
Input schema present but exposes no named parameters.
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.
research_network ~84
Connect institution research with Palimpsest's complete source catalog, Seiche funding context, Undertow exit-liquidity evidence and NarcoScope global data. Compact default; set limit for full metadata. No institution identifiers, scores or eligibility changes; source rights stay attached.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | – |
| offset | integer | – | – |
| topic | string | – | – |
No output schema declared.
No examples provided.
stablecoin_rails_board Stablecoin Rails board ~100
Read the compact Stablecoin Rails board: every tracked issuer's peg, redemption-run, direct-chain liability validation, coverage-gated reserve and executable-exit evidence, chain concentration and tripwire state plus the aggregate regime. Series and full receipts stay on the public REST detail route. Takes no arguments; the full oracle state never treats partial evidence as CALM (the separate peg/run alert is retained for compatibility), and the board is not investment advice.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
universe_search RBI NBFC register search ~129
Search the RBI NBFC register by name/CIN substring, classification or regulation layer. Returns official register rows. Supply q or a filter; a filter without q browses that slice. Registration does not establish creditworthiness.
| 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 ~65
Verify a ledger stream by recomputing hash-chain commitments and checking enabled signatures and anchors. Returns the actual verifier verdict, including failures. Verifies record integrity, not economic accuracy.
| Name | Type | Req | Description |
|---|---|---|---|
| stream | string | – | ledger stream name to verify (default 'mfi_watchlist') |
No output schema declared.
No examples provided.
What is the LiquiLens — the Failure Radar MCP server?
LiquiLens — the Failure Radar is an MCP server listed in the public MCP registry as io.github.beepboop2025/liquilens. Free bank research: NPA reconciliation, small finance banks, UCBs and cited evidence limits. This page covers its hosted endpoint (https://api.liquilens.in/mcp).
Is the LiquiLens — the Failure Radar MCP server safe to use?
LiquiLens — the Failure Radar scores 83 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the LiquiLens — the Failure Radar MCP server expose?
LiquiLens — the Failure Radar exposes 22 tools: bank_asset_quality_review, bank_npa_reconciliation, banking_specialisation_coverage, corporate_transmission_board, crypto_exposure_board, and 17 more. Their descriptions and schemas cost roughly 1,816 tokens of context every time the server is loaded.
Does the LiquiLens — the Failure Radar MCP server require authentication?
No. We connected to LiquiLens — the Failure Radar without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the LiquiLens — the Failure Radar MCP server still maintained?
LiquiLens — the Failure Radar is still listed as active in the MCP registry. We last reached this channel on 20 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.