LiquiLens Trade Safety Gateway
REMOTE · TRADE-SAFETY.LIQUILENS.IN
Read-only checks for proposed orders against evidence and policy; no trading or payment authority.
Available components
Last scanned (17 hours ago)
Scores higher than 85% of remote servers
Unreachable for 1 day in a row. Last reached 3 Nov 2026.
Category Finance and Payments
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 Security14
- TLS not yet verified: we couldn't open a connection to check the certificate. View diagnostics → Unverified
- Authorisation not yet verified: we couldn't confirm whether this endpoint requires it. View diagnostics → Unverified
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- HSTS not yet verified: we couldn't read the response headers to check for it. View diagnostics → Unverified
- DNSSEC is configured correctly; the domain's records validate against the full chain to the root. View diagnostics → Pass
Transport & Reachability0
- Transport check failed: declared streamable-http, but we couldn't connect to verify it. See how to fix → View diagnostics → Fail
Schema Quality & AI Usability0
- Schema not yet verified: we couldn't read the endpoint's schema, or could read only part of its tool list.Unverified
Stability & Change Management0
- Stability not yet verified: not enough scan history yet (needs a 30-day window).Unverified
Tool Coverage0
- Tool coverage not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.Unverified
Tool Safety0
- Tool safety not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.Unverified
Capabilities0
- Capabilities not yet verified: we couldn't read the endpoint's capabilities.Unverified
Unverified: 5 categories
Categories scored 0 because we could not verify them: authentication we do not have, an unreachable endpoint, or not enough scan history. We only credit what we can confirm.
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.
- 4 Nov 26 0
- Endpoint reachability: reachable → unreachable ▼ security
- HSTS header: fail → unverified ▼ security
- Stability: pass → unverified ▼ security
- Authorization: partial → unverified ▼ security
- Tool safety: pass → unverified ▼ security
- TLS certificate: pass → unverified ▼ security
- Transport: pass → fail ▼ security
- Capabilities: pass → unverified ▼ functional
- Tool coverage: 100 → unverified ▼ functional
- First check of Schema quality: unverified functional
- 29 Oct 26 0
- Server version: 0.2.2 → 0.2.3 functional
- 8 Oct 26 +1
- Stability: 0.97 → pass security
- 3 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 90 to 93. That category is still filling its 30-day observation window: 27 days of observed history at the previous scan, 28 at this one. The score rises as the window fills, whether or not the server changes.
- 28 Sept 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 Sept 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
- 6 Sept 26 0
- Stability: unverified → 0.03 ▲ functional
- 5 Sept 26 0
First indexed and scored.
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 4 Nov 2026 · Probed https://trade-safety.liquilens.in/mcp
TLS unreached
Background: What to check on a remote MCP endpoint →
DNSSEC secure
Validation of trade-safety.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 |
| trade-safety.liquilens.in. | Verified address RRset verified with the apex keys |
Authentication Inconclusive
We could not reach the endpoint well enough to judge its authorisation posture.
| Result | Inconclusive |
|---|
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://trade-safety.liquilens.in/mcp | Unreachable | ||
| http (plaintext) | http://trade-safety.liquilens.in/mcp | HTTPS enforced |
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 →
assess_trade_safety Assess exact-order trade safety ~80
Read fixed public native Trade Safety context from Seiche and Undertow, plus conditional LiquiLens context, and issue a short-lived SHA-256-only sandbox receipt. This tool cannot recommend, preview with a broker, route, resize, custody, settle, or execute an order.
| Name | Type | Req | Description |
|---|---|---|---|
| policy | object | yes | – |
| request | object | yes | – |
No output schema declared.
No examples provided.
trade_safety_capabilities Trade-safety gateway capabilities ~23
Describe the static sandbox authority, fixed sources, and limits.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
How do I install the LiquiLens Trade Safety Gateway MCP server?
LiquiLens Trade Safety Gateway is a hosted endpoint at https://trade-safety.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 · trade-safety.liquilens.in
claude mcp add --transport http beepboop2025-liquilens-trade-safety-gateway 'https://trade-safety.liquilens.in/mcp'
What is the LiquiLens Trade Safety Gateway MCP server?
LiquiLens Trade Safety Gateway is an MCP server listed in the public MCP registry as io.github.beepboop2025/liquilens-trade-safety-gateway. Read-only checks for proposed orders against evidence and policy; no trading or payment authority. This page covers its hosted endpoint (https://trade-safety.liquilens.in/mcp).
Is the LiquiLens Trade Safety Gateway MCP server safe to use?
LiquiLens Trade Safety Gateway scores 82 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 Trade Safety Gateway MCP server expose?
LiquiLens Trade Safety Gateway exposes 2 tools: assess_trade_safety, trade_safety_capabilities. Their descriptions and schemas cost roughly 103 tokens of context every time the server is loaded.
Does the LiquiLens Trade Safety Gateway MCP server require authentication?
Its publisher declares no required credentials for LiquiLens Trade Safety Gateway. We have not been able to confirm that against the live endpoint, and a server can require authorisation without declaring it here.
Is the LiquiLens Trade Safety Gateway MCP server still maintained?
LiquiLens Trade Safety Gateway is still listed in the MCP registry, though our most recent checks did not reach this channel. We last reached this channel on 3 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.