Is the Beepboop2025 Liquilens MCP server down?

mcp-registry/io.github.beepboop2025/liquilens · v1.8.1

Also listed as github/beepboop2025/liquilens-mcp, mcp-registry/io.github.beepboop2025/financial-source-data

healthy
Last checked 2026-10-17 10:00 UTC · handshake 1.1s

As of 2026-10-17 10:00 UTC, the Beepboop2025 Liquilens MCP server is up with a Glimind reliability score of 82/100 (grade B). Over the last 30 days it answered 99.8% of Glimind's liveness checks. It had 37 outages in 90 days, with a median recovery of 2 minutes.

uptime (30d checks)
99.8%
checks observed
3,634
outages (90d)
37
tools
24

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

Install Beepboop2025 Liquilens MCP server

Add to Cursor Add to VS Code

Claude Code

claude mcp add --transport http beepboop2025-liquilens-mcp-server https://api.liquilens.in/mcp

Claude Desktop · Windsurf · Cline (mcpServers JSON)

{
  "mcpServers": {
    "beepboop2025-liquilens-mcp-server": {
      "type": "http",
      "url": "https://api.liquilens.in/mcp"
    }
  }
}

Third-party server, listed as discovered. Review its source before installing.

Agent-readiness: B (84/100)

B (84/100): 0 error(s), 3 warning(s) across 24 tool(s); ~3,453 tokens of tool definitions.
Scores higher than 46% of 15,265 MCP servers Glimind has audited.
Its tool list costs an agent ~3,453 tokens per session — more than 55% of servers.
no tool-poisoning patterns
Schemas100
Descriptions70
Safety hints83
Token cost100
Client compatibility70
Protocol100
Reliability85
Stability80

What to fix (5)

17 parameter(s) across 7 tool(s) have no description.

Add a "description" to each parameter with its format and an example ("ISO 8601 date, e.g. 2026-10-17"). This is the commonest cause of wrong arguments on the first call.

Tools: bank_asset_quality_review, bank_npa_reconciliation, banking_specialisation_coverage, institution_evidence_monitor, institution_research_coverage and 2 more

2 tool(s) look like they change state (create/send/delete/pay…) but declare no destructiveHint.

Set annotations {"readOnlyHint": false, "destructiveHint": true|false, "idempotentHint": …}. Clients use these to ask the user before a side effect and to auto-approve safe reads.

Tools: bank_npa_reconciliation, verify_published_record

Handshake + tools/list takes ~1,731 ms.

Serve tools/list from memory, keep the process warm, and host close to your users. Every new agent session pays this before its first call.

No tool declares an outputSchema.

Declare outputSchema and return structuredContent (MCP 2025-06-18+). Agents can then parse results without guessing, and chain tools reliably.

In the last 30 days: 0 tool(s) removed and 5 schema change(s).

Add new tools or optional parameters instead of renaming or removing; deprecate first (say so in the description) and remove later. Agents cache tool contracts.

Get alerted

Get an email or webhook when this server's readiness drops by 10+ points, tool-poisoning text appears, or a tool breaks:

curl -X POST https://glimind.com/v1/subscriptions -H 'content-type: application/json' -d '{"tools":["mcp-registry/io.github.beepboop2025/liquilens"],"email":"[email protected]"}'

Agents: watch_tool({"toolId": "mcp-registry/io.github.beepboop2025/liquilens"}) over MCP.

Passed

Largest tool definitions

Static checks of the advertised tools/list (schema, descriptions, annotations, tool-poisoning patterns, names, size) plus observed protocol, uptime, latency and contract changes. Read-only: no tool is ever called. Weights: schema 15, docs 20, safety 15, efficiency 15, compatibility 15, protocol 5, reliability 10, stability 5. Token counts are estimates (~3.6 characters per token).

Operator? Fix these, then re-check live. Embed the readiness badge:

Markdown
[![MCP agent-readiness](https://glimind.com/v1/readiness/badge/mcp-registry%2Fio.github.beepboop2025%2Fliquilens.svg)](https://glimind.com/server/mcp-registry%2Fio.github.beepboop2025%2Fliquilens?ref=badge)
HTML
<a href="https://glimind.com/server/mcp-registry%2Fio.github.beepboop2025%2Fliquilens?ref=badge"><img src="https://glimind.com/v1/readiness/badge/mcp-registry%2Fio.github.beepboop2025%2Fliquilens.svg" alt="MCP agent-readiness"></a>
reStructuredText
.. image:: https://glimind.com/v1/readiness/badge/mcp-registry%2Fio.github.beepboop2025%2Fliquilens.svg
   :target: https://glimind.com/server/mcp-registry%2Fio.github.beepboop2025%2Fliquilens?ref=badge
   :alt: MCP agent-readiness

Tool-definition log

Glimind records every version of this server's tool definitions in a signed, append-only transparency log. Current manifest sha256:f015132427a7d2ac…, first seen 2026-10-17, included at leaf 4842 of 17,365. Version history · verify what your client received.

Tools (24)

Compare: most reliable finance servers · most reliable knowledge servers · most reliable data servers · most reliable other servers · most reliable search servers

Know before your agent calls it

Glimind tells agents whether a server is up right now and how to call it, then fails over to a live alternative when it isn't.

Add Glimind — free, no signup:

Add to Cursor Add to VS Code

Claude Code

claude mcp add --transport http glimind https://glimind.com/mcp

Claude Desktop · Windsurf · Cline (mcpServers JSON)

{
  "mcpServers": {
    "glimind": {
      "type": "http",
      "url": "https://glimind.com/mcp"
    }
  }
}

FAQ

Is the Beepboop2025 Liquilens MCP server down right now?

As of 2026-10-17 10:00 UTC, the Beepboop2025 Liquilens MCP server is up with a Glimind reliability score of 82/100 (grade B). Over the last 30 days it answered 99.8% of Glimind's liveness checks. It had 37 outages in 90 days, with a median recovery of 2 minutes.

How many tools does Beepboop2025 Liquilens MCP server provide?

Beepboop2025 Liquilens MCP server advertises 24 tools, including bank_asset_quality_review, bank_npa_reconciliation, banking_specialisation_coverage, corporate_transmission_board, crypto_exposure_board.

How do I install Beepboop2025 Liquilens MCP server?

Point your MCP client at this streamable-http endpoint: https://api.liquilens.in/mcp

Is the Beepboop2025 Liquilens MCP server safe to connect to an AI agent?

Glimind scanned all 24 tool definitions for tool-poisoning patterns — hidden or invisible characters, instructions that override the model, concealment from the user, requests to read credential or MCP config files, conversation exfiltration and cross-tool shadowing — and found none. This checks what the server tells the model, not what its code does; review the source before granting access to sensitive data.

Operator of Beepboop2025 Liquilens MCP server?

Status page: 90-day uptime, every outage and how long it lasted.

Claim this listing to get the Verified operator marker, a remediation checklist and owner analytics, or embed the live badge from any of the tool pages above. Maintainers: alerts, deploy attestation and monthly reports.

Status is an automated estimate from Glimind's liveness checks (handshake and tool listing only; no tool is ever called) and may lag or differ from your network. Glimind is not affiliated with this server or its operator. Operator? Request a correction or opt out at https://glimind.com/opt-out.