World Monitor
Real-time global intelligence on conflict, markets, energy, trade, shipping and cyber. 100 tools.
Offline verification of local evidence carriers, fleet briefs, and hash-only trade-safety receipts.
作者提供的原文
列表按使用分(满分 100)排序,由以下部分组成
| 热度 | 0/80 | GitHub 星标或每周下载量:较大的计 60,较小的计 20 |
|---|---|---|
| 新鲜度 | 12/12 | 30 天内有发布或代码更新得满分 |
| 仍在响应 | 0/8 | 上次检查时云端端点有响应 |
| 使用分 | 12/100 |
质量: 基础检查通过 3/3 项(仅展示,不用于排序) · 上升势头: 暂无数据 (只用于“上升中”标签)
选择你使用的 AI 应用,然后复制设置。
通过 3/3 项检查 · 在你的电脑上运行
第一步:你用哪个 AI?
选择你用的应用,步骤会显示在下方。
可连接 Claude,但需要先准备
不需要密钥,不用安装程序 · 仅限电脑上的 Claude 应用(Windows 或 Mac),网页和手机不可用
用 LiquiLens Evidence Carrier 告诉我你能帮我做什么,然后做一件给我看✓ 如果 Claude 说正在使用 LiquiLens Evidence Carrier,或回答中出现 LiquiLens Evidence Carrier 的工具名称,就表示连接成功
菜单名称已于 2026年11月11日 对照 Anthropic 帮助页面核实 · 你的界面可能因版本略有不同
ChatGPT 暂时无法连接 LiquiLens Evidence Carrier
LiquiLens Evidence Carrier 需要安装在你的电脑上,而 ChatGPT 只能连接在网上运行的服务器
A · 使用能连接 LiquiLens Evidence Carrier 的应用
B · 其他 类中能连接 ChatGPT 的其他服务器
从同类中使用较多的里挑选,仅限用地址即可连接、无需密钥的
Claude Code 暂时无法连接 LiquiLens Evidence Carrier
开发者只提供了电脑版 Claude 应用的安装文件
A · 使用能连接 LiquiLens Evidence Carrier 的应用
Cursor 暂时无法连接 LiquiLens Evidence Carrier
开发者只提供了电脑版 Claude 应用的安装文件
A · 使用能连接 LiquiLens Evidence Carrier 的应用
VS Code 暂时无法连接 LiquiLens Evidence Carrier
开发者只提供了电脑版 Claude 应用的安装文件
A · 使用能连接 LiquiLens Evidence Carrier 的应用
依据这个服务器的连接方式和各应用自己的文档,检查于 2026年11月10日。
在你的电脑上运行,适用于
ClaudeGooseLM StudioMsty StudioCherry StudioVisual StudioWindsurf (Devin Desktop)ZedKiroClineContinueJetBrains AI AssistantCodex CLIGemini CLIOpenCodenodecodeWarpLibreChatRaycast
它在你的电脑上运行;安装后,工具列表会显示在你的 AI 应用中。
我们检查的是任何人都能看到的信息;我们没有阅读代码。不适用的检查项不计入总数。 · 检查于 2026年11月20日
注册名称已通过 GitHub 账户 beepboop2025 验证,该账户拥有此仓库
代码最后更新于8天前
使用 Apache-2.0
它在你的电脑上运行,没有互联网端点
在你的电脑上运行,改用本地设置
它在你的电脑上运行;我们只能读取互联网端点的工具列表
如果你是作者,可把这段代码贴到 README。徽章会链接回本页。
[](https://mcp.popnx.com/en/servers/beepboop2025-liquilens-evidence-carrier)提问、分享技巧或报告无法使用。按“有帮助”数量排序。
还没有评价
与注册中心里这个分类中所有活跃的服务器比较。只有当发布者拥有该仓库时,星标数才计入。
它在 3 项适用的基础检查中通过了 3 项。我们没有阅读代码。在添加密钥或令牌之前,请先看看这个服务器要求哪些权限,并使用只具备所需权限的密钥。
注册中心没有列出必需的密钥,不过有些服务器会在首次使用时要求你登录。
它在你的电脑上运行。你的 AI 应用会在需要时启动它,数据不会经过作者的服务器(除非它自己调用在线服务)。
GitHub 仓库最后更新于8天前,最新版本(0.20.1)于2个月前进入注册中心。
支持 MCP 的应用,例如 Claude Desktop、Claude Code、Cursor 和 VS Code。你的电脑上还需要有 MCPB。
同一分类中有:World Monitor, openstatus, Oh My Posh Validator, Strata, Jitsu
同一分类、其他作者、命令已通过检查。官方的排在前面,再按星标排序。
如何看卡片:↓ 每周下载量i★ GitHub 星标i三大支柱:评价 · 检查 · 使用情况i更新 = 最新版本发布到注册中心的时间i
Real-time global intelligence on conflict, markets, energy, trade, shipping and cyber. 100 tools.
Manage monitors, status pages, incidents and maintenances in your openstatus workspace.
Validate oh-my-posh configurations and segment snippets against the official schema.
MCP server for progressive tool usage at any scale (see https://klavis.ai)
Manage Jitsu data pipelines: destinations, streams, connections, functions, live events.
| 本项 LiquiLens Evidence Carrier | World Monitor | openstatus | Oh My Posh Validator | Strata | Jitsu | |
|---|---|---|---|---|---|---|
| 运行位置 | 需要安装在电脑上 | 在云端运行,无需安装 | 在云端运行,无需安装 | 在云端运行,无需安装 | 在云端运行,无需安装 | 在云端运行,无需安装 |
| 需要密钥 | 否 | 否 | 否 | 否 | 否 | 否 |
| 可在 Claude 中按 + 添加 | 否 | 否 | 否 | 否 | 否 | 否 |
| 基础检查 | 3/3 | 4/4 | 4/4 | 4/4 | 1/4 | 4/4 |
| 许可证 | Apache-2.0 | AGPL-3.0 | AGPL-3.0 | MIT | Apache-2.0 | MIT |
| 价格 | 登记中未列出费用 | 登记中未列出费用 | 登记中未列出费用 | 登记中未列出费用 | 登记中未列出费用 | 登记中未列出费用 |
按原文从作者的仓库复制。PopNx MCP 没有审查或背书其内容。HTML、图片和脚本已被移除。链接会离开本站。
LiquiLens Evidence Carrier is a transport-neutral contract for moving financial evidence through files, warehouses, event buses, observability systems, data catalogs, FDC3 desktops, notebooks, citations, and AI agents without dropping provenance, rights, freshness, or authority boundaries.
The carrier is infrastructure for inspection and reproducibility. It is not an order, recommendation, credit rating, market-data entitlement, or endorsement by Bloomberg, LSEG, FactSet, FINOS, or any other platform.
The current signed core release is v0.20.1. Its offline routing resource uses Palimpsest's published catalog API while the additional MCP tool awaits approval. All 22 artifact checksums passed; the downloaded wheel and MCP bundle have verified provenance for the exact signed source, and the official MCP Registry advertises the new bundle. See docs/RELEASE-0.20.1.md for the publication receipt. The 0.20.0 receipt remains available. Independent consumer channels retain their own recorded versions.
The following historical core publication receipt describes v0.19.0. Published release v0.19.0 provides the preserved historical wheel and Registry record. Annotated tag object c3239bfc7c4d3c4b7fc5ce26e0f602962e7d4337 targets the allowlisted SSH-signed release commit 8f5738c9e77cc95b9a68543d478b9521f5595d61, tree acca6fa7aab75ebc91bf044e153c6468cd6f9c0c; remote main resolved to the same commit when the receipt was verified. The exact commit passed preflight run 33630656569, and release run 33630790150 published 23 assets at 2026-09-02T12:36:19Z. All 22 entries in the downloaded SHA256SUMS passed; its SHA-256 is c6d52cbf8794db6e478e3b2ea9e1ed8eee7757137650892a6a96fcbb839bb6bc. Attestation 44695012 binds the 22 non-manifest artifacts to the tagged source. The official MCP Registry record was verified active/latest at 0.19.0 for that release and pinned MCPB SHA-256 11db11aefafcc6c4ba558877d1f9892fc708150b3afbaa28a741e74435b9a91a.
Release v0.19.0 preserves every Trade Safety v1 schema byte and adds the deterministic adversarial corpus, dependency-free TypeScript-compatible Node raw-UTF8 verifier and authenticated paper-only order guard, OpenBB 0.2.0 hash-only verification, and MCP corpus discovery. Gateway 0.1.2 pins core 0.19.0 and remains a read-only, hash-only sandbox with no broker route. Container run 33630789998 published and smoke-tested the core multi-platform index at sha256:bdbfed2afa87f25e8ef88dffeb4ba7ab198854705528c0de5abe31552a170b9a; attestation 44695462 binds that digest to the tagged source. Separately, gateway run 33630790011 published and smoke-tested gateway index sha256:b5c43013da1fdddd9e6e56cab0e4f0f562e39ab25cc640869c5008e3457218e3; attestation 44695195 binds it to the same commit. These are package and registry artifacts, not a hosted gateway, live-order activation, or financial authority.
A later independent gateway-only publication used signed annotated tag trade-safety-gateway-v0.1.3, tag object 757c18928c8036910ab50c80ec073679d7434abf, targeting signed commit fa8e25ae8e0e992611706b8d66e951342d594243 and tree 7680694bf3397a0844f2388fb29067ff402f066d. Gateway run 33651560380 published and smoke-tested the amd64/arm64 index sha256:9b8f704547ecf6c43039b34149d6cca842de5d66cba13c040199cf5f3f216d61; attestation 44751184 binds that digest to the tagged source. The run recorded semantic, source-commit, and signed-tag-object aliases without moving latest or a core-* alias. There is no corresponding GitHub Release object and no hosted deployment or paid-route activation is claimed. See the exact gateway 0.1.3 publication receipt.
See docs/RELEASE-0.19.0.md for the complete release, Registry, artifact, and OCI receipt. GitHub reports the Release record itself as immutable: false; version-tag ruleset 21288366 blocks v* tag update and deletion with no bypass, and the current assets are checksum- and transparency-attested, but they are not described as platform-enforced immutable assets. The complete historical v0.18.0 receipt remains docs/RELEASE-0.18.0.md.
The immutable annotated v0.17.0 tag object cb85e527c2b74abf476fd9a01b73b2235ce976b7 targets protected-main merge edde9b92ad9851d2974b91326a8c3877f4386d3a, but its release run 33585764285 failed at the commit-signature gate before any artifact was built, attested, or published. There is no v0.17.0 GitHub release or official MCP Registry record. See docs/RELEASE-0.17.1.md for the unchanged recovery receipt and docs/RELEASE-0.17.0.md for the unchanged failed-attempt record.
One verified JSON object can be embedded in:
Every full carrier preserves event_time <= knowledge_time <= as_of, source hashes, explicit redistribution rights, a content-derived identity, and an all-false execution/recommendation/credit-rating boundary. Restricted or unknown rights fail closed; incomplete or expired evidence is redacted to a separately identified reference rather than silently upgraded.
Want to inspect an explained copilot decision first? The offline copilot demo runs from this source checkout with Python alone. It uses clearly synthetic inputs, shows candidate and HOLD scenarios, and keeps execution blocked without network, credentials or broker setup. It is separate from the signed core package below.
The installation guide covers ordinary conda-forge 0.15.0, the listed Dev Container Feature (Carrier 0.14.0), and SchemaStore editor setup. Those channels have their own versions; use the signed 0.20.0 wheel below for the current core release, connected-research resources and Trade Safety verification.
# Source checkout (main may contain post-release documentation)
uv sync --locked uv run liquilens-evidence --help
python -m pip install 'https://github.com/beepboop2025/liquilens-evidence-carrier/releases/download/v0.20.0/liquilens_evidence-0.20.0-py3-none-any.whl#sha256=d864af722153f66a5cad5855ce00fb70809a4a078d7d972a75ce714ebbdf57cc' liquilens-evidence issue examples/descriptor.json > carrier.json liquilens-evidence verify carrier.json --as-of 2026-08-24T12:00:00Z liquilens-evidence convert carrier.json --format fdc3
Published release v0.20.0 provides a wheel and checksum manifest. The Python runtime has no third-party dependencies. A Node.js verifier is also included for cross-language liquilens-hash-tree-v1 identity checks:
node protocol/verify_hash_tree_v1.mjs --artifact evidence-carrier carrier.json
node protocol/verify_hash_tree_v1.mjs --artifact fleet-brief fleet-brief.json node protocol/verify_hash_tree_v1.mjs --artifact trade-safety-receipt receipt.json
| Contract | Canonical identity | Availability at this source checkpoint |
|---|---|---|
| Full carrier | https://liquilens.in/protocol/liquilens-evidence-carrier-v1.schema.json | Published and hosted |
| Redacted reference | https://liquilens.in/protocol/liquilens-evidence-carrier-reference-v1.schema.json | Published and hosted |
| Four-product fleet brief | https://liquilens.in/protocol/liquilens-fleet-brief-v1.schema.json | Published and hosted |
| Trade Safety request | https://liquilens.in/protocol/liquilens-trade-safety-request-v1.schema.json | Published v0.19.0 release asset and canonically hosted |
| Trade Safety policy | https://liquilens.in/protocol/liquilens-trade-safety-policy-v1.schema.json | Published v0.19.0 release asset and canonically hosted |
| Broker preview reference | https://liquilens.in/protocol/liquilens-broker-preview-reference-v1.schema.json | Published v0.19.0 release asset and canonically hosted |
| Trade Safety receipt | https://liquilens.in/protocol/liquilens-trade-safety-receipt-v1.schema.json | Published v0.19.0 release asset and canonically hosted |
| FDC3 Trade Safety receipt | https://liquilens.in/protocol/fdc3/com.liquilens.trade-safety-receipt.schema.json | Published v0.19.0 release asset and canonically hosted |
| FDC3 context | https://liquilens.in/protocol/fdc3/com.liquilens.evidence.schema.json | Published and hosted |
| OpenLineage facet | https://liquilens.in/protocol/openlineage/liquilens-evidence-facet.schema.json | Published and hosted |
The five Trade Safety identities above are stable schema $id values. LiquiLens Pages run 33592149926 succeeded at 2026-09-02T04:49:12Z for site revision 3ec660175c81c5b282715ee400eea2f771dc2610; its post-deploy gate retrieved all five URLs over HTTPS and matched their exact bytes to the hashes in protocol/catalog.json. This is schema-hosting proof, not a hosted Trade Safety gateway or live-order activation receipt.
The current contracts are v1. Release v0.17.1 added Trade Safety without changing the previously published Carrier or Fleet Brief semantics. Release v0.19.0 preserves the v1 schema bytes and extends cross-language verification; it does not create a new protocol identity. The signed release workflow is run 33630790150, the wheel SHA-256 is 1adccb72376f50456fd16a979e372f802ae73ba35b766633bc3d8bd4ab5abcc8, and the MCPB SHA-256 is 11db11aefafcc6c4ba558877d1f9892fc708150b3afbaa28a741e74435b9a91a. Production integrations can pin v0.19.0; separately released container, skill, plugin, browser, and package-manager channels retain their own verified versions. The canonical URLs are now available for public schema discovery.
liquilens.trade-safety-receipt.v1 composes independent Seiche funding/system context, Undertow position-sized exit conte