Remote MCP · Endpoint

LiquiLens — the Failure Radar MCP server

No. LiquiLens — the Failure Radar answered an MCP handshake 1 hour ago.

UpLast checked 1 hour ago

Server URL

https://api.liquilens.in/mcp

The last check completed an MCP handshake.

Registry name
io.github.beepboop2025/liquilens
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
317 ms
Tools exposed
25 tools
Uptime, last 30 days
100% from 18 checks
Described by its publisher as
Free bank-filing and counterparty research; cited evidence limits; public MCP needs no API key.
Website
https://liquilens.in/agents/
Repository
https://github.com/beepboop2025/liquilens-mcp
Listing
From the official MCP registry (active).
Recent checks of LiquiLens — the Failure Radar
CheckedResultHandshake
1 hour agoHandshake completed317 ms
1 day agoHandshake completed329 ms
2 days agoHandshake completed318 ms
3 days agoHandshake completed323 ms
4 days agoHandshake completed313 ms
5 days agoHandshake completed324 ms
6 days agoHandshake completed513 ms
9 days agoHandshake completed319 ms
12 days agoHandshake completed308 ms
14 days agoHandshake completed324 ms
16 days agoHandshake completed337 ms
18 days agoHandshake completed410 ms
20 days agoHandshake completed708 ms
22 days agoHandshake completed404 ms
24 days agoHandshake completed294 ms
26 days agoHandshake completed299 ms
27 days agoHandshake completed331 ms
29 days agoHandshake completed459 ms

The last 18 checks. Full history is kept for 30 days; the all-time counter stands at 29 responding of 29.

How to read this

  • ·Handshake latency is one measurement from one probe, from our infrastructure. It is a smoke signal about the endpoint, not a benchmark of your own connection to it.
  • ·An authentication challenge counts as responding. A hosted server that refuses an anonymous prober is behaving correctly.
  • ·A tool count of “behind credentials” means the handshake worked but listing tools needed a token we do not hold.
  • ·Uptime covers the last 30 days of our own checks, at most one an hour, and says how many checks it is drawn from.

Related

All hosted MCP serversGlide connector for AI assistantsGlide for AI agents

Listing data comes from the official MCP registry. Glide is not affiliated with LiquiLens — the Failure Radar and makes no claim about it beyond what these checks measured.