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

Safety scan

A88/100

Adoption

New

0 stars

Reviews

Nobody has reviewed LiquiLens Evidence Carrier yet.

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

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

scanner v0.1.9 · 2026-09-19 · 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 11 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.Rubric Appeal a finding JSON

The registry entry has no remote endpoint or installable package.

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 11 days ago (2026-09-09). 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.

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.
not reviewed
Established
B