Prototype · Preview: every server in the official registry, synced every 30 minutes. Sign in with Google to write reviews.Prototype · updated every 30 min
PopNx MCPMCP servers for people who use AI · explained in plain words Sign in

LiquiLens Trade Safety Gateway

by beepboop2025version 0.2.2i★ 0iRuns in the cloudOfficial site ↗
Registry nameio.github.beepboop2025/liquilens-trade-safety-gateway

How to install

What it does

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

  • Connects Runs in the cloud
  • Account or key No key needed
  • Category Online shops & payments

Why it ranks here

Lists are ordered by a usage score (out of 100) built from these parts

Popularity0/80GitHub stars or weekly downloads: the larger counts 60, the smaller 20
Freshness12/12Full marks for a release or code change within 30 days
Still answering0/8The cloud endpoint answered at the last check
Usage score12/100

Quality: Passed 3/4 basic checks (shown, not used for ordering) · Momentum: No data yet (Used only on the Trending tab)

Install

Pick the AI app you use, then copy the settings.

Passed 3/4 checks · Runs on your computer

We hid some of the commands

Connect by URL: the server address did not answer when we checked

No install path has passed yet. See the maker’s instructions or pick another server in this category · Maker’s install instructions · Others in this category

First: which AI do you use?

Pick your app and the steps appear below.

Claude cannot connect LiquiLens Trade Safety Gateway yet

No install path has passed yet. See the maker’s instructions or pick another server in this category

ChatGPT cannot connect LiquiLens Trade Safety Gateway yet

No install path has passed yet. See the maker’s instructions or pick another server in this category

What you can do instead

B · Others in Online shops & payments that work with ChatGPT

Picked from the most used in the same category, only ones that connect by address with no key

Claude Code cannot connect LiquiLens Trade Safety Gateway yet

No install path has passed yet. See the maker’s instructions or pick another server in this category

Cursor cannot connect LiquiLens Trade Safety Gateway yet

No install path has passed yet. See the maker’s instructions or pick another server in this category

VS Code cannot connect LiquiLens Trade Safety Gateway yet

No install path has passed yet. See the maker’s instructions or pick another server in this category

No install path has passed yet. See the maker’s instructions or pick another server in this category

Stuck? Ask people who use LiquiLens Trade Safety Gateway💬 Discussion →

At a glance

Downloads per weeki
Not on npm/PyPI
Licencei
Apache-2.0
Connection
Runs in the cloud
Transport
streamable-http
Latest versioni
0.2.2
Published to registryi
Sep 5, 2026
Code last changedi
Nov 12, 2026
Last checked
Nov 15, 2026
Maker
beepboop2025
Registry status
Active

Which apps can use it

Based on how this server connects and on each app’s own docs, checked Nov 10, 2026.

Connect over the internet in

GooseLM StudioMsty StudioCherry StudioVisual StudioWindsurf (Devin Desktop)ZedKiroClineContinueJetBrains AI AssistantCodex CLIGemini CLIOpenCodenodecodeWarpLibreChatOpen WebUIRaycast

All apps, with pros and cons →

Related guides

What it can do

The server did not answer when we last checked, so we could not read its tools.

Basic checksi

We check information anyone can see; we have not read the code. Checks that do not apply are left out of the count. · Checked Nov 20, 2026

  • ✓ Pass

    Maker matches the repo

    The registry name was verified with the GitHub account beepboop2025, which owns the repo

  • ✓ Pass

    Still maintained

    Code last changed 8 days ago

  • ✓ Pass

    Has a licence

    Uses Apache-2.0

  • ✕ Fail

    Endpoint responds

    Did not respond within 6 seconds when we checked

  • – Not applicable

    Sign-in with OAuth

    Did not respond within 6 seconds when we checked

  • … Not checked yet

    No hidden instructions in tool descriptions

    Not checked yet; we read the tool list when we check the endpoint

What we check → · JSON

Makers: ask for a re-check or report wrong info
For makers: add a badge to your README

If you made this, paste this code into your README. The badge links back to this page.

[![Featured on PopNx MCP](https://mcp.popnx.com/badge/beepboop2025-liquilens-trade-safety-gateway.svg)](https://mcp.popnx.com/en/servers/beepboop2025-liquilens-trade-safety-gateway)

Discussion

Ask, share a tip or report that it does not work. Sorted by what people marked helpful.

No posts yet. Be the first to ask or share.

Posts here are written by users, not the PopNx team.

Sign in to post

User reviews

No reviews yet

Sign in to write a review

Compared with others in Online shops & paymentsi

  • More stars than 0% of the other 2985 servers in this category
  • Published to the registry more recently than 26% of the other 2985 servers in this category
  • Basic checks equal to or better than 60% of the other 2985 servers in this category

Compared with every active server in this category in the registry. Stars count only when the publisher owns the repo.

Common questions

Is LiquiLens Trade Safety Gateway safe?

It passed 3 of 4 applicable basic checks. We have not read the code. Before adding a key or token, see what access the server asks for and use a key with only the permissions you need.

What keys or codes does it need?

The registry does not list a required key, though some servers ask you to sign in on first use.

Does it run on my computer or in the cloud?

It runs in the maker’s cloud. Connect over the internet with nothing to install, but what you send passes through the maker’s servers.

Is it still maintained?

The GitHub repo last changed 8 days ago, and the latest version (0.2.2) reached the registry 3 months ago.

Which apps can use it?

Apps that support MCP, such as Claude Desktop, Claude Code, Cursor and VS Code. It connects by URL, so apps that accept remote MCP servers work too, such as ChatGPT on the web (full MCP on Business and above; Pro read-only).

What can I use instead?

In the same category: Stripe MCP, flightclaw, Trade It, Marketplace Ad Pros: Amazon Ads & Seller Central, idealo MCP Server

Similar alternatives

Same category, other makers, commands already checked. Official ones first, then by stars.

Reading a card:↓ Downloads per weeki★ GitHub starsiThree pillars: reviews · checks · usageiUpdated = latest version published to the registryi

Stripe MCP

Stripe’s official server lets AI view and manage customers, products, payments and invoices. Connect to Stripe’s cloud and sign in with OAuth.

by stripeWidely used★ 2.1KUpdated 13 months ago

Runs in the cloud✓ service owner · stripe.com

flightclaw

Search ~300 airlines and book flights with a checkout link. OAuth sign-in by email code.

by flightclawGrowing★ 87Updated 2 months ago

Runs in the cloud✓ service owner · flightclaw.com

Trade It

Connect brokerage accounts to AI assistants: holdings, orders, asset lookup, and approved trading.

by trade-it-incEarly★ 62Updated 35 days ago

Runs in the cloud✓ service owner · tradeit.app

idealo MCP Server

Search products, compare prices and discover deals across 6 European markets with your AI assistant.

by idealoEarly★ 28Updated 6 months ago

Runs in the cloud✓ service owner · mcp.idealo.com
Compared with similar ones
This one
LiquiLens Trade Safety Gateway
Stripe MCPflightclawTrade ItMarketplace Ad Pros: Amazon Ads & Seller Centralidealo MCP Server
Runs whereRuns in the cloud, nothing to installRuns in the cloud, nothing to installRuns in the cloud, nothing to installRuns in the cloud, nothing to installRuns in the cloud, nothing to installRuns in the cloud, nothing to install
Needs a keyNoNoNoNoNoNo
Add with + in ClaudeNoYesNoNoNoNo
Basic checks3/44/44/45/54/44/4
LicenseApache-2.0MITMITCC0-1.0MITMIT
PriceNo cost listed in the registryNo cost listed in the registryNo cost listed in the registryNo cost listed in the registryNo cost listed in the registryNo cost listed in the registry

README from the maker

Open the README

Copied from the maker’s repo as written. PopNx MCP has not reviewed or endorsed it. HTML, images and scripts are removed. Links lead off this site.

LiquiLens Trade Safety Gateway

This integration is a read-only sandbox adapter for AI trading copilots. It accepts one exact Trade Safety Request and one operator policy, reads a small set of fixed public evidence endpoints, and issues the deterministic SHA-256-only receipt defined by liquilens_evidence.trade_safety.

It is not an order gateway. It has no broker credentials, broker preview, order-submission route, recommendation route, automatic resize behavior, custody, trade settlement, or real-money authority. An optional x402 route can settle a payment for access to the same assessment; payment cannot alter the policy, evidence, outcome, receipt authority, or order path. Every response carries X-Trade-Safety-Mode: sandbox, X-Trade-Safety-Authority: read-only, and X-Trade-Safety-Execution: disabled. Live-mode assessments deterministically return unavailable because the evidence is context-only, the receipt is not tenant-authenticated, and the broker-preview reference is not_applicable.

HTTP and MCP surface

  • GET /healthz reports process health without probing or masking source state.
  • GET /v1/capabilities describes static limits, sources, and authority.

Anonymous POST requests share a budget within each gateway worker: 16 requests in flight, 20 new requests per second, a burst of 40, and a 20-second total deadline covering body upload and processing. Rate exhaustion returns HTTP 429; occupied capacity or an expired deadline returns HTTP 503. These responses carry Retry-After: 1, Cache-Control: no-store, and the usual read-only headers. MCP errors retain the JSON-RPC envelope. Retry with backoff and jitter; paid requests, when separately enabled, must also follow the settlement journal's reconciliation rules.

Health and discovery GET requests remain available when the POST budget is full. No IP address or installation identity is stored by this control, and changing forwarding, installation, or monitoring headers cannot bypass it. The limits are per worker, not a fleet-wide quota or a substitute for edge network protection. Operators can lower or raise the bounded budget with TRADE_SAFETY_MAX_IN_FLIGHT (1–64), TRADE_SAFETY_REQUESTS_PER_SECOND (1–100), and TRADE_SAFETY_REQUEST_BURST (1–200); invalid values fail startup. The effective settings are exposed under limits.admission in the capability response.

  • POST /v1/check accepts exactly {"request": {...}, "policy": {...}}.
  • POST /v1/x402/check is registered only under a complete x402 configuration; it challenges and settles paid access to an otherwise identical assessment.
  • POST /mcp supports initialize, ping, tools/list, and tools/call.
  • MCP exposes only assess_trade_safety and trade_safety_capabilities.
  • MCP negotiates initialization-based 2025-11-25 and stateless 2026-07-28; the latter exposes server/discover metadata and requires matching MCP-Protocol-Version, Mcp-Method, and applicable Mcp-Name headers. Invalid versions or header/body mismatches return HTTP 400.
  • After legacy initialization, every subsequent legacy POST must carry MCP-Protocol-Version: 2025-11-25; accepted notifications return HTTP 202 without a JSON-RPC body.
  • Browser-originated MCP requests accept only the canonical HTTPS issuer origin; non-browser clients may omit Origin, while any other origin returns HTTP 403. Accepted legacy notifications/initialized posts return HTTP 202 with no body.
  • FastAPI publishes generated OpenAPI at /openapi.json and Swagger UI at /docs.

There is deliberately no execution-shaped MCP tool.

Server-owned policy admission

The protocol accepts operator-authored policies, but the public gateway does not let an anonymous caller redefine its safety floor. Before any source request or x402 verification, it admits the supplied policy against a server-owned envelope:

  • Seiche and Undertow remain mandatory and STRESS remains a held regime;
  • source-age ceilings cannot exceed 8 days for Seiche or 1 day for Undertow and LiquiLens;
  • notional, exit-cost, and venue-spread limits must be present and cannot exceed USD 100,000, 50 bps, and 20 bps respectively;
  • missing evidence remains fail-closed, live still requires an executable quote and broker preview, and automatic resize remains forbidden; and
  • an operator may tighten any limit or admit only exact canonical policy hashes.

Recognized TRADE_SAFETY_POLICY_* settings are documented by trade_safety_gateway.policy_guard. Unknown, malformed, or looser settings fail startup. GET /v1/capabilities publishes the active non-secret envelope.

SettingFormat and tighten-only meaning
TRADE_SAFETY_POLICY_REQUIRED_PRODUCTSUnique comma-separated subset of seiche,undertow,liquilens; it must include Seiche and Undertow
TRADE_SAFETY_POLICY_HOLD_REGIMESUnique comma-separated subset of CALM,EROSION,STRAIN,STRESS; it must include STRESS
TRADE_SAFETY_POLICY_MAX_SEICHE_AGE_SECONDSPositive integer no greater than 691200
TRADE_SAFETY_POLICY_MAX_UNDERTOW_AGE_SECONDSPositive integer no greater than 86400
TRADE_SAFETY_POLICY_MAX_LIQUILENS_AGE_SECONDSPositive integer no greater than 86400
TRADE_SAFETY_POLICY_MAX_NOTIONAL_USDPositive finite number no greater than 100000
TRADE_SAFETY_POLICY_MAX_EXIT_COST_BPSPositive finite number no greater than 50
TRADE_SAFETY_POLICY_MAX_VENUE_SPREAD_BPSPositive finite number no greater than 20
TRADE_SAFETY_POLICY_SHA256_ALLOWLISTUnique comma-separated lowercase canonical policy SHA-256 values

x402 access and agent discovery

x402 is disabled when every TRADE_SAFETY_X402_* setting is absent. A complete configuration adds the paid route and publishes an exact x402 v2 offer with HTTP Bazaar discovery metadata. The offer binds the canonical request body, resource, price, asset, payee, ResourceInfo, and required extensions with a dedicated quote key. The runtime verifies before assessment, settles only after the protected response exists, and releases only the exact journaled bytes.

Payment identity and transaction provenance stay in the private settlement journal, never in the Trade Safety receipt or adoption telemetry. A settled payment does not turn context-only evidence into an executable quote and does not make a safety result fresh forever. See TRADE-SAFETY-X402.md for configuration, the local liquilens-trade-safety-x402-reconcile operator command, state recovery, and activation gates. The command never calls the facilitator; operators must independently establish settled or definitely-unsettled state before changing an uncertain journal entry.

Fixed evidence adapters

ProductFixed requestReceipt state and boundary
SeicheGET https://api.seiche.info/api/trade-safety/risk-context, schema seiche.risk-context.v1context_only; the native cache-only projection, conservative evidence clocks, rights state, staleness counts, attestation boundary, and projection digest are validated and retained. Seiche is not order-bound upstream, so the receipt explicitly binds its exact projection digest to the canonical Trade Safety request hash.
UndertowPOST https://api.seiche.info/undertow/mcp, tool trade_safety_exit_contextcontext_only; the gateway sends the canonical Trade Safety request hash with an exact observe/paper BTC/USD sell rung. Undertow must echo that binding and provide a verified PIT head/chain, deployed SHA, approved derived-metadata rights, complete six-venue coverage, coherent clocks, and an intact context digest.
LiquiLensGET https://api.liquilens.in/api/failure-radar/institution/{quoted_slug}Called only for a validated request.order.instrument.identifiers.liquilens_institution_slug; only latest period end and historical-evidence status/eligibility are projected. Otherwise not_applicable.

Undertow JSON-RPC text content is ignored. The gateway consumes structuredContent only; Seiche is consumed from its fixed REST representation. Both native objects use exact-key validation, have their unkeyed canonical digests recomputed, and are checked for cross-field consistency after the digest check. The exact uncompressed HTTP entity is hashed independently. Source, observation/as-of, knowledge, producer retrieval, gateway retrieval, native expiry, and local receipt-expiry clocks remain separate.

Undertow completeness is roster-scoped, not a claim about the whole market. The gateway requires exact set equality with its declared six-CEX roster and cross-checks quote conversion, required depth band, per-venue basis-point and dollar costs, best/worst venue, spread, peg, proof, rights, and expiry before using a result. Off-roster CEXs, DEXs, and agent-native venues remain unmeasured by construction; adding or changing a venue requires a reviewed contract update rather than silent acceptance.

Fail-closed and network boundary

  • The request and policy—including their cross-reference, current lifetime, and the optional institution slug—are validated before any outbound call.
  • The caller policy is admitted against the immutable server safety floor before any outbound call or payment challenge/verification.
  • Destinations, methods, MCP tool names, and URL bases are constants. Request bodies cannot provide a URL.
  • Redirects, environment proxies, cookies, compression, non-JSON bodies, non-200 responses, malformed/duplicate-key JSON, MCP errors, and missing structuredContent are rejected.
  • Request bodies are capped at 64 KiB; source bodies at 1 MiB; gateway responses at 512 KiB. Each upstream operation has a five-second total timeout and a two-second connect timeout.
  • Independent eligible sources are fetched concurrently. A source error, producer-declared unavailable state, stale native clock, digest failure, request-hash mismatch, proof failure, or rights mismatch becomes that product's typed unavailable evidence section. Because Seiche and Undertow are mandatory products, the receipt then fails closed.
  • The service does not log request bodies, response bodies, secrets, account data, or source exceptions. The bundled command disables access logs.
  • Every evidence section and the broker-preview reference carries trade_safety_request_hash(request). Undertow also receives and echoes it; Seiche's native projection digest and request hash receive a separate local binding digest inside the hash-sealed receipt. No nearest-rung result is promoted to exact-order evidence.
  • Observe and paper are the only modes sent to Undertow. Live and buy requests never reach its sell-side paper-context tool; they produce typed unavailable evidence instead.
  • Requests carrying both notional and a non-null quantity do not reach Undertow until a broker-normalized economic-order digest and reference-price contract can prove both fields describe the same exposure.

Public-source access does not imply real-money or redistribution rights. All three adapters therefore declare metadata_only, context_only, real_money_eligible: false, and executable_quote: false where applicable.

Local development

From this directory, install the repository protocol package and the gateway in one environment:

python3 -m venv .venv

. .venv/bin/activate python -m pip install -e ../.. -e '.[test]' pytest liquilens-trade-safety-gateway

The server listens on 0.0.0.0:8080. Free sandbox mode accepts no API key or broker secret. Enabling x402 requires its dedicated quote-binding secret but still accepts no wallet private key or broker credential. Adoption telemetry is also off by default; an operator can explicitly select a private append-only JSONL path as described in [TRADE-SAFETY-TRACTION.md](https://github.com/beepboop2025/liquile

Only the beginning is shown; read the rest in the repo