GroundLens
PYPI · GROUNDLENS
Guardrails for LLM answers: exact checks against sources, PASS/REVIEW/FAIL, signed records.
Available components
Last scanned (17 hours ago)
Scores higher than 68% of PyPI 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 Security50
- Malware scan not yet available for this package.Unverified
- No known CVEs affecting this package version or its production dependencies.Pass
- Runs maturin at install time, a recognised build step with no custom scripting around it. View diagnostics → Pass
- No production dependencies, so there is no dependency health to assess. View diagnostics → Pass
Provenance & Transparency100
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Cryptographically verified build provenance (signed, bound to groundlens-dev/groundlens). View diagnostics → Pass
- Clear OSI-approved license (Apache-2.0).Pass
- Actively maintained (last published 35 days ago).Pass
- Publishes a security disclosure policy (SECURITY.md).Pass
Schema Quality & AI Usability58
- AI-judged instruction clarity (good).Pass
- Context-footprint check failed: tool/resource definitions use about 542 tokens (~180/item across 3 items; 3 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management97
- Stability observed for 29 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage71
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 0% of tool parameters carry a description.Fail
- Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 3 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 4 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
Checks we ran (15)
- Known CVEs
- Install scripts
- Dependency health
- Source repository
- Provenance
- License
- Maintenance
- Security disclosure
- Schema quality
- Stability
- Tool coverage
- Injection markers
- Destructive annotations
- Judged manipulation
- MCP protocol
Checks we could not complete (1)
These are gaps on our side, not findings about this package. We only credit what we can confirm, so a category made up entirely of them scores 0.
- Malware scan in Supply Chain SecurityMalware scan not yet available for this package.
Does not apply to this package (2)
- Endpoint SecurityScored on hosted endpoints only. A package has no live endpoint of its own for us to probe.
- Transport & ReachabilityScored on hosted endpoints only. A package has no live endpoint of its own for us to probe.
The score does not measure everything. What the score does not measure →
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.
- 21 Nov 26 0
- Stability: pass → 0.97 functional
- 15 Nov 26 0
- Package version: 5.2.0 → 6.0.5 functional
- 14 Nov 26 0
- Stability: 0.97 → pass security
- 13 Nov 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.
- 11 Nov 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.
- 10 Nov 26 −15
- Malware scan: pass → unverified ▼ security
- 9 Nov 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.
- 7 Nov 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.
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 21 Nov 2026 · Analysed pypi/groundlens@6.0.5
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 | pypi |
| Reason | Verified |
| Discovered via | Registry attestation endpoint |
| Source repo | groundlens-dev/groundlens |
| Certificate issuer | https://token.actions.githubusercontent.com |
| Certificate SAN | https://github.com/groundlens-dev/groundlens/.github/workflows/release.yml@refs/tags/v6.0.5 |
| Rekor log index | 3277572732 |
| Predicate type | PyPI publish attestation https://docs.pypi.org/attestations/publish/v1 |
| Subject digest | sha256:18a806c8657863eb9ca8d4fa7512ec5b3ea39b7ada3295a0175e27497254db11 |
Background: How many MCP packages publish verified provenance →
Install scripts 1 script
| Hook | Tier | Command |
|---|---|---|
| build_backend | Known build tool | maturin |
Background: Why install scripts are a supply-chain risk →
Dependencies 0 packages
| Packages resolved | 0 |
|---|---|
| Tree resolution | Complete |
Background: SBOMs and build attestations, explained →
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 →
verify_answer ~225
Check an answer against the passages it was written from, before you send it. Every figure must be in the passages or follow from figures that are; no model is used. Returns PASS, REVIEW or FAIL with the reasons, and the signed record. sources: (id, text) pairs, {"id","text","provenance"} dicts, or bare strings. policy: a built-in name (e.g. "eu_ai_act_high_risk_v1"), a path, or YAML. scope: what the request is about, e.g. {"entity": "UPS"}; a figure taken from a source whose provenance is another entity fails. risk_class: the request's risk class, when the policy defines them. Returns the decision (PASS/REVIEW/FAIL), the evidence, the regulatory mapping and the record with its content hash.
| Name | Type | Req | Description |
|---|---|---|---|
| answer | string | yes | – |
| locale | string | – | – |
| policy | – | – | – |
| question | – | – | – |
| risk_class | – | – | – |
| scope | – | – | – |
| sources | array | yes | – |
Structured output declared, but exposes no named fields.
No examples provided.
verify_records ~66
Verify a log of records offline: every hash, every link, every signature. records: the JSON Lines text of an answer-record or run-record log. Returns {"ok", "verified", "kind"}; fails if any record or link was altered.
| Name | Type | Req | Description |
|---|---|---|---|
| records | string | yes | – |
Structured output declared, but exposes no named fields.
No examples provided.
verify_run ~114
Verify an MCP execution trace under an execution policy and return the run record. trace: the MCP session as JSON-RPC messages (JSON Lines). policy: the execution policy, as YAML/JSON text or a path. Returns the gate (ALLOW/REVIEW/DENY), any breaches, and the signed run record.
| Name | Type | Req | Description |
|---|---|---|---|
| policy | string | yes | – |
| run_id | string | yes | – |
| started_at | – | – | – |
| system | string | yes | – |
| system_version | – | – | – |
| trace | string | yes | – |
Structured output declared, but exposes no named fields.
No examples provided.
How do I install the GroundLens MCP server?
GroundLens runs locally as a PyPI package, launched with uvx --from 'groundlens[mcp]' groundlens mcp. Ready-made configuration for Claude, Cursor, VS Code, Codex and 3 more is on this page, copied from each client's own documentation.
pypi · groundlens
claude mcp add groundlens-dev-groundlens -- uvx --from 'groundlens[mcp]' groundlens mcp
What is the GroundLens MCP server?
GroundLens is an MCP server listed in the public MCP registry as io.github.groundlens-dev/groundlens. Guardrails for LLM answers: exact checks against sources, PASS/REVIEW/FAIL, signed records. This page covers its PyPI package (groundlens).
Is the GroundLens MCP server safe to use?
GroundLens scores 75 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 21 November 2026. 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 GroundLens MCP server expose?
GroundLens exposes 3 tools: verify_answer, verify_run, verify_records. Their descriptions and schemas cost roughly 405 tokens of context every time the server is loaded.
Is the GroundLens MCP server still maintained?
GroundLens is still listed as active in the MCP registry. We last reached this channel on 21 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.
What licence is the GroundLens MCP server under?
GroundLens 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.
What did VerifyMCP test on the GroundLens MCP server?
VerifyMCP ran 15 checks on GroundLens, covering Known CVEs, Install scripts, Dependency health, Source repository and 11 more. One item could not be completed, a gap on our side rather than a finding about GroundLens: Malware scan. Endpoint Security and Transport & Reachability do not apply to a PyPI package, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.