MCP.Market

LiquiLens Evidence Carrier MCP server

by beepboop2025·io.github.beepboop2025/liquilens-evidence-carrier·v0.20.1

Offline verification of local evidence carriers, fleet briefs, and hash-only trade-safety receipts.

A88/100grade A
What users say
No reviews yet
Be the first
Safety scan
A88/100

full report

Adoption
New

0 stars

Reviews

Write one

Nobody has reviewed LiquiLens Evidence Carrier yet.

If you have run it, two minutes of your experience saves the next person an afternoon.

LiquiLens Evidence Carrier tools

No tool declarations could be read from the package source. They show once the server is installed.

Public scan report

scanner v0.1.10 · 2026-10-15 · same rubric, same numbers if you re-run it

no findings
  • –Code scanpackage could not be scannedn/a
  • –Live reliabilityno gateway calls yet and no remote to proben/a
  • –Tool poisoningtools not inspected (local package is not executed); not countedn/a
  • Auth qualitylocal package, no credentials required12/15
  • Maintenancelast push 0 days ago15/15
  • Maintainer identityregistry namespace matches repository owner; GitHub account older than a year8/10
Overall 88/100. Components that don't apply are left out of the denominator. Any critical finding is an F.RubricAppeal a findingJSON

How LiquiLens Evidence Carrier compares

Against every graded MCP server, from our own scans and uptime checks. Updated after each scan run.

Safety score
88/100
higher than 75% of 48,255 servers

Install LiquiLens Evidence Carrier in Claude Code, Cursor or VS Code

The registry entry has no remote endpoint or installable package.

What the publisher says

From the LiquiLens Evidence Carrier repository's README, as published. We do not edit it. Read it on GitHub

LiquiLens Evidence Carrier

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.

Shortened. The full README is on GitHub.

Nothing above is checked by us. What we check is on the safety report.

LiquiLens Evidence Carrier: common questions

Is LiquiLens Evidence Carrier MCP server safe?
Yes, by our scan: it is graded A (88/100). Read the LiquiLens Evidence Carrier safety report
Does LiquiLens Evidence Carrier need an API key?
Not as far as the registry entry and our scan can tell: no credentials are declared or required.
Is LiquiLens Evidence Carrier maintained?
The last commit was 20 days ago (2026-10-15). The latest release is v0.20.1.
What can I use instead of LiquiLens Evidence Carrier?
Servers from other publishers that do the same job: Nautilus Compass Memory MCP server.

Alternatives to LiquiLens Evidence Carrier

Same job from other publishers: the closest match first, then the best rated.

  • Nautilus Compass Memory
    Local-first long-term memory for AI agents, with byte-recomputable signed verification receipts.
    B

More from beepboop2025 →