LiquiLens Evidence Carrier
MCPB · LIQUILENS-EVIDENCE-CARRIER-MCP-0.20.1.MCPB
Offline verification of local evidence carriers, fleet briefs, and hash-only trade-safety receipts.
Available components
Last scanned (17 hours ago)
Scores higher than 99% of MCPB servers
Category Security
How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score → Why this is hard to score →
Supply Chain Security0
- No malware scan is available for this kind of package: the supply-chain vendors we use do not cover it. This is a permanent gap in our coverage, not a finding about the package.Unverified
- Known CVEs could not be checked: we found no dependency list to check in this bundle: either it runs a compiled binary, whose bundled manifests we do not read, or none of the package.json, requirements.txt, pyproject.toml or uv.lock files it ships for its runtime declares a dependency we can read (a requirements.txt that only points at a setup.py project, a local path, or a nested requirements file we cannot follow counts as none).Unverified
- Install-script risk not yet assessed.Unverified
- Dependency health could not be checked: we found no dependency list to check in this bundle: either it runs a compiled binary, whose bundled manifests we do not read, or none of the package.json, requirements.txt, pyproject.toml or uv.lock files it ships for its runtime declares a dependency we can read (a requirements.txt that only points at a setup.py project, a local path, or a nested requirements file we cannot follow counts as none).Unverified
Provenance & Transparency100
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Cryptographically verified build provenance (signed, bound to beepboop2025/liquilens-evidence-carrier). View diagnostics → Pass
- Clear OSI-approved license (Apache-2.0).Pass
- Actively maintained (last published 56 days ago).Pass
- Publishes a security disclosure policy (SECURITY.md).Pass
Schema Quality & AI Usability85
- 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
- AI-judged instruction clarity (good).Pass
- Tool/resource definitions use about 710 tokens (~47/item across 15 items; 4 tools + 11 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management100
- No destabilizing schema changes in the last 30 days.Pass
Tool Coverage96
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 89% of tool parameters carry a description.Partial
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 4 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 6 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a current MCP spec version (2026-07-28).Pass
Unverified: 1 category
A category scored 0 because we could not verify it: a data source with nothing on this package, evidence we could not reach, or a check we could not run. 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
- Stability: 0.97 → pass security
- 3 Nov 26 0
- Stability: pass → 0.97 functional
- 28 Oct 26 0
- Stability: 0.97 → pass security
- 27 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 93 to 97. That category is still filling its 30-day observation window: 28 days of observed history at the previous scan, 29 at this one. The score rises as the window fills, whether or not the server changes.
- 25 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 87 to 90. That category is still filling its 30-day observation window: 26 days of observed history at the previous scan, 27 at this one. The score rises as the window fills, whether or not the server changes.
- 23 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 80 to 83. That category is still filling its 30-day observation window: 24 days of observed history at the previous scan, 25 at this one. The score rises as the window fills, whether or not the server changes.
- 21 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 73 to 77. That category is still filling its 30-day observation window: 22 days of observed history at the previous scan, 23 at this one. The score rises as the window fills, whether or not the server changes.
- 19 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 67 to 70. That category is still filling its 30-day observation window: 20 days of observed history at the previous scan, 21 at this one. The score rises as the window fills, whether or not the server changes.
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 · Analysed mcpb/https://github.com/beepboop2025/liquilens-evidence-carrier/releases/download/v0.20.1/liquilens-evidence-carrier-mcp-0.20.1.mcpb
Provenance Verified
A signed build attestation was found and verified, binding this exact artifact to the source repository it claims to come from.
| Result | Verified |
|---|---|
| Ecosystem | mcpb |
| Reason | Verified |
| Discovered via | GitHub artifact attestations |
| Source repo | beepboop2025/liquilens-evidence-carrier |
| Certificate issuer | https://token.actions.githubusercontent.com |
| Certificate SAN | https://github.com/beepboop2025/liquilens-evidence-carrier/.github/workflows/release.yml@refs/tags/v0.20.1 |
| Rekor log index | 2764110327 |
| Predicate type | SLSA build provenance https://slsa.dev/provenance/v1 |
| Subject digest | sha256:09b25571f61f4ba2bd5e1c367a580355a6e08eccf0d1c34bdde0bbd460be0ed6 |
Background: How many MCP packages publish verified provenance →
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 →
project_carrier Project verified evidence carrier ~97
Verify one local carrier and project it to a bounded transport format. Restricted, unsafe, or expired payloads remain blocked or redacted by policy.
| Name | Type | Req | Description |
|---|---|---|---|
| evaluated_at | string | – | Optional policy evaluation clock as an RFC 3339 UTC timestamp ending in Z. The current UTC time is recorded when omitted. |
| format | string | yes | – |
| path | string | yes | Carrier JSON path, relative to the allowed root or absolute within it. |
No output schema declared.
No examples provided.
verify_carrier Verify local evidence carrier ~84
Verify one local carrier JSON file under the configured root. Returns identity and rights-aware export disposition, never market advice.
| Name | Type | Req | Description |
|---|---|---|---|
| evaluated_at | string | – | Optional policy evaluation clock as an RFC 3339 UTC timestamp ending in Z. The current UTC time is recorded when omitted. |
| path | string | yes | Carrier JSON path, relative to the allowed root or absolute within it. |
No output schema declared.
No examples provided.
verify_fleet_brief Verify local LiquiLens fleet brief ~84
Verify one local, content-addressed fleet brief under the configured root. Replays the exact recorded evaluation clock without fetching or mutating data.
| Name | Type | Req | Description |
|---|---|---|---|
| evaluated_at | string | yes | Required RFC 3339 UTC clock ending in Z; it must match the brief. |
| path | string | yes | Fleet brief JSON path, relative to the allowed root or absolute within it. |
No output schema declared.
No examples provided.
verify_trade_safety_receipt Verify local hash-only trade-safety receipt ~104
Verify one local order-bound receipt under the configured root at an explicit clock. This v1 tool accepts no authentication secrets, so HMAC receipts fail closed and require tenant-local verification. It never fetches market data, recommends, or executes an order.
| Name | Type | Req | Description |
|---|---|---|---|
| evaluated_at | string | yes | Required verification clock as an RFC 3339 UTC timestamp ending in Z. |
| path | string | yes | Receipt JSON path, relative to the allowed root or absolute within it. |
No output schema declared.
No examples provided.
How do I install the LiquiLens Evidence Carrier MCP server?
LiquiLens Evidence Carrier ships as an MCPB bundle, a single file you download and open in an MCP host that supports MCPB bundles, such as Claude Desktop. The host reads the launch command from the bundle's own manifest, so there is no command to copy. The MCP registry declares no SHA-256 for this bundle, so there is no published digest to check the download against.
mcpb · liquilens-evidence-carrier-mcp-0.20.1.mcpb
Download bundleThe MCP registry declares no SHA-256 for this bundle, so there is no published digest to check it against. Open it with an MCPB-capable host such as Claude Desktop.
What is the LiquiLens Evidence Carrier MCP server?
LiquiLens Evidence Carrier is an MCP server listed in the public MCP registry as io.github.beepboop2025/liquilens-evidence-carrier. Offline verification of local evidence carriers, fleet briefs, and hash-only trade-safety receipts. This page covers its MCPB bundle (https://github.com/beepboop2025/liquilens-evidence-carrier/releases/download/v0.20.1/liquilens-evidence-carrier-mcp-0.2…).
Is the LiquiLens Evidence Carrier MCP server safe to use?
LiquiLens Evidence Carrier scores 67 out of 100 on VerifyMCP. Its build provenance is signed and verified. 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 Evidence Carrier MCP server expose?
LiquiLens Evidence Carrier exposes 4 tools: verify_carrier, project_carrier, verify_fleet_brief, verify_trade_safety_receipt. Their descriptions and schemas cost roughly 369 tokens of context every time the server is loaded.
What licence is the LiquiLens Evidence Carrier MCP server under?
LiquiLens Evidence Carrier declares the Apache-2.0 licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.