LiquiLens — the Failure Radar

io.github.beepboop2025/liquilens

Free bank-filing and counterparty research; cited evidence limits; public MCP needs no API key.

View repository →Homepage →

Connect this server

Add this to your MCP client config — claude_desktop_config.json (Claude Desktop) or .cursor/mcp.json (Cursor).Suits: Cursor · HTTP clients.

{
  "mcpServers": {
    "liquilens": {
      "url": "https://api.liquilens.in/mcp"
    }
  }
}

A starting point — check the repository for exact arguments and setup. Restart your client after editing the config.

Category
Developer Tools
Version
1.8.1
Registry
active
Published
9/24/2026

Remotes

  • streamable-httphttps://api.liquilens.in/mcp

More Developer Tools servers

Browse all Developer Tools →

LiquiLens Evidence Carrier

beepboop2025

Offline verification of local evidence carriers, fleet briefs, and hash-only trade-safety receipts.

Developer ToolsAdded 2 months ago

LiquiLens Trade Safety Gateway

beepboop2025

Read-only checks for proposed orders against evidence and policy; no trading or payment authority.

Developer ToolsAdded 2 months ago

io.github.beepboop2025/lucent

beepboop2025

Call-scoped Clear Signing presentation checks for EVM signing agents.

Developer ToolsAdded 3 months ago

my quant — finite market briefing

beepboop2025

Read-only discovery for a finite, offline-capable market briefing with explicit evidence boundaries.

Developer ToolsAdded 2 months ago

my quant doesn’t speak english — editorial discovery

beepboop2025

Read-only discovery and bounded access to a finite market briefing with evidence boundaries.

Developer ToolsAdded 2 months ago

NarcoScope — illicit-economy evidence atlas

beepboop2025

Read bounded illicit-economy evidence with provenance, privacy, availability, and federation intact.

Developer ToolsAdded 2 months ago

Add the badge to your site

Show visitors that LiquiLens — the Failure Radar is listed here — it’s also the link we check for a free listing.

LiquiLens — the Failure Radar — listed on Serverdex

HTML — for your website

<a href="https://serverdex.io/server/io-github-beepboop2025-liquilens?utm_source=badge"><img src="https://serverdex.io/brand/badge.svg" alt="LiquiLens — the Failure Radar — listed on Serverdex" width="123" height="40" loading="lazy"></a>

Recommended. A dofollow link from your own domain is the one that counts for search engines, and it's the link we check for a free listing.

Markdown — for your README

[![LiquiLens — the Failure Radar — listed on Serverdex](https://serverdex.io/brand/badge.svg)](https://serverdex.io/server/io-github-beepboop2025-liquilens?utm_source=badge)

Nice for visibility, but GitHub marks README links nofollow, so it doesn't pass authority. Use the HTML badge on your site as well.