Home / MCP registry index / io.github.beepboop2025/liquilens
LiquiLens — the Failure Radar
io.github.beepboop2025/liquilens in the official MCP registry.
Endpoint https://api.liquilens.in/mcp. Source: github.com/beepboop2025/liquilens-mcp.
The registry describes it as: Free bank-filing and counterparty research; cited evidence limits; public MCP needs no API key.
We read its 24 tools on 2026-10-27. Nothing in them matched our tool-poisoning rules. It also sets server instructions, text a client puts in front of the model on connect; those were read too.
A clean read means these rules found nothing, not that the server is harmless. A server can change its tools at any time, which is why the index reads it again every week.
Tools it advertises
bank_asset_quality_review bank_npa_reconciliation banking_specialisation_coverage corporate_transmission_board crypto_exposure_board crypto_regime_board evidence_europe evidence_india evidence_institution evidence_markets evidence_us failure_radar_board failure_radar_institution forward_odds household_credit_board institution_evidence_monitor institution_research_coverage institution_review_packet latest_article rbi_supervisory_tape research_network stablecoin_rails_board universe_search verify_published_record
Run this server? Show the check in your README
The badge reflects the latest weekly read: 
[](https://lazaretto.dev/mcp-registry/io-github-beepboop2025-liquilens)How this was checked
Lazaretto connects to the endpoint the way any MCP client does, asks the server to introduce itself and list its tools, and reads every name, description, parameter schema and server instruction for tool poisoning: hidden directive blocks, orders to read local secrets, parameters built to carry secrets or the conversation out, orders that redirect another server's tools, and invisible characters. It never calls a tool. What we found across the registry.
To run the same check every time Claude Code adds a server, install the free lazaretto-guard plugin. Browse every server in the index.