Prototype · Preview: every server in the official registry, synced every 30 minutes. Reviews and accounts come in a later step.
PopNx MCPMCP servers for people who use AI · explained in plain words

GroundLens

by groundlens-devversion 6.0.5i★ –iRuns on your computer
Registry nameio.github.groundlens-dev/groundlens

Install

Overview

Description from the maker (original English)

Guardrails for LLM answers: exact checks against sources, PASS/REVIEW/FAIL, signed records.

PopNx MCP’s three pillars

These three are never merged into one score: opinions, measurements and popularity are different things.

What you can do with it

We have not written a plain-language summary for this one yet. Below are the facts we read from the registry.

  • Connection: Runs on your computer
  • Transport: stdio
  • Category: Search & AI memory

Install

Pick the AI app you use, then copy the settings.

Before you install

  • Basic checks: 1 of 1 passed
  • Runs on your computer with your user’s permissions (files, network, apps).
  • The registry lists no key to fill in.

You need

  • PyPIPython’s uv installed (for the uvx command)

Which app do you use?

Pick your app above. We remember it, so next time the button says “Install in …”.

Open Claude Desktop → Settings → Developer → Edit Config, and paste this into claude_desktop_config.json

{
  "mcpServers": {
    "groundlens": {
      "command": "uvx",
      "args": [
        "groundlens",
        "mcp"
      ]
    }
  }
}

Run this in your terminal

claude mcp add groundlens -- uvx groundlens mcp

Open in Cursor

Or copy the settings yourself

Paste into .cursor/mcp.json in your project, or ~/.cursor/mcp.json

{
  "mcpServers": {
    "groundlens": {
      "command": "uvx",
      "args": [
        "groundlens",
        "mcp"
      ]
    }
  }
}

Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.

Open in VS Code

Or copy the settings yourself

Paste into .vscode/mcp.json in your project

{
  "servers": {
    "groundlens": {
      "type": "stdio",
      "command": "uvx",
      "args": [
        "groundlens",
        "mcp"
      ]
    }
  }
}

Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.

This one runs on your computer, and ChatGPT can only connect to servers on the internet. Pick another app.

Your choice stays on this device in a cookie; no account needed.

These settings are generated from the maker’s registry entry. If the README says otherwise, follow the README.

What it can do

Runs on your computer; the tool list appears in your AI app after you install it.

Basic checksi

We check information anyone can see; we have not read the code. Checks that do not apply are left out of the count. · Checked Nov 7, 2026

  • ✓ Pass

    Maker matches the repo

    The registry name was verified with the GitHub account groundlens-dev, which owns the repo

  • … Not checked yet

    Still maintained

    We have not read this repo from GitHub yet

  • … Not checked yet

    Has a licence

    We have not read this repo from GitHub yet

  • – Not applicable

    Endpoint responds

    This one runs on your computer; there is no internet endpoint

  • – Not applicable

    Sign-in with OAuth

    Runs on your computer and uses local settings instead

  • … Not checked yet

    No hidden instructions in tool descriptions

    Runs on your computer; we can only read tool lists from internet endpoints

Compared with others in Search & AI memoryi

  • More stars than 0% of the other 7249 servers in this category
  • Published to the registry more recently than 64% of the other 7249 servers in this category
  • Basic checks equal to or better than 100% of the other 7249 servers in this category

Compared with every active server in this category in the registry. Stars count only when the publisher owns the repo.

Common questions

Is GroundLens safe?

It passed 1 of 1 applicable basic checks. We have not read the code. Before adding a key or token, see what access the server asks for and use a key with only the permissions you need.

What keys or codes does it need?

The registry does not list a required key, though some servers ask you to sign in on first use.

Does it run on my computer or in the cloud?

It runs on your computer. Your AI app starts it when needed, and data does not pass through the maker’s servers (unless it calls an online service itself).

Is it still maintained?

The GitHub repo last changed –, and the latest version (6.0.5) reached the registry 21 days ago.

Which apps can use it?

Apps that support MCP, such as Claude Desktop, Claude Code, Cursor and VS Code. You also need Python (uv) on your computer.

What can I use instead?

In the same category: Context7, Codebase Memory, Exa

Alternatives

Servers in the same category from other makers, sorted by stars.

Reading a card:★ GitHub starsiThree pillars: reviews · checks · usageiUpdated = latest version published to the registryi

Context7

by upstash

Feeds AI the latest docs for libraries and frameworks before it answers, so code it writes does not use outdated, removed functions.

Computer or cloud★ 64,224MITUpdated today
Install

Codebase Memory

by DeusData

Codebase knowledge graph for AI agents — 162 languages, sub-ms queries, 99% fewer tokens.

Runs on your computer★ 48,148MITUpdated 20 days ago
Install

Exa

by exa-labs

Connect AI agents to Exa for web search, content fetching, and multi-step research.

Runs in the cloud★ 5,213MITUpdated last month
Install

README from the maker

Open the README

Copied from the maker’s repo as written. PopNx MCP has not reviewed or endorsed it. HTML, images and scripts are removed. Links lead off this site.

Guardrails for LLM answers

GroundLens checks AI answers against your documents: the figures, who they are about, and whether they answer the question.

On financial answers it had never seen, it stopped 3 of 4 wrong ones; on public claims with numbers, half of the unsupported ones. About 10 ms per check, deterministic, no LLM in the loop. 1

🤔 Already running an LLM‑as‑judge? Keep it. GroundLens runs the exact checks first, and a FAIL never reaches the judge. Your judge only sees the answers the exact checks could not reject.

Deterministic Exact checks first, no LLM judge needed

Provable PASS, REVIEW or FAIL, with a signed record

Measured Measure the error rate of what passes, on your answers

Portable Rust engine: the same hash on every OS

Works with

Quickstart

# pip install groundlens

import groundlens as gl

verifier = gl.Verifier(sink=gl.sinks.jsonl("records/")) record = verifier.check(answer="Revenue was €42.1 million.", passages=["Revenue reached €41.2 million."]) print(record.decision, record.reasons)

FAIL ['c2: groundlens.numeric contradicted: €42.1 million not in sources; nearest 41200000 EUR in ctx-0 (relative distance 0.021)']

Runs locally: no account, no API key, no model, no network. The signed record is in records/ before check returns.

Integration

The same check, wired into your stack:

Langfuse · pip install "groundlens[langfuse]"

from langfuse import get_client

verifier = gl.Verifier(sink=gl.sinks.jsonl("records/"), observers=[gl.integrations.langfuse(get_client())])

Call check inside the observation that produced the answer, and its trace gets:

  • Score `groundlens.decision`: categorical, PASS, REVIEW or FAIL, on the check and on its trace. Filter traces by it, chart it, export it.
  • Observation `groundlens.check`: type guardrail. The reasons are its status message, one per line. Its level follows Langfuse's own scale: PASS is DEFAULT, REVIEW is WARNING, FAIL is ERROR.
  • Metadata of the check: decision, reason codes (groundlens.scope.contradicted), policy, and the id and hash of the signed record behind it.
  • Judge: a generation observation with the model name, next to your own model calls.
  • Spans: one per verifier, plus the store, each with its duration. Log View shows them in milliseconds.
  • SDK: Python v3 and v4. Tested on Langfuse Cloud and self-hosted Langfuse 4.58.

Grafana and OpenTelemetry · pip install "groundlens[otel]"

verifier = gl.Verifier(sink=gl.sinks.jsonl("records/"), observers=[gl.integrations.otel()])

Spans and metrics go through the providers your application already configured: Tempo, Prometheus, or any OpenTelemetry backend.

  • Metrics: groundlens_decisions_total{decision, policy}, groundlens_reasons_total{reason, decision}, groundlens_check_duration_seconds{stage} with stage total, engine, judge, sign, store.
  • Spans: groundlens.check with groundlens.decision, groundlens.reasons, record id and hash; children per verifier, the judge (gen_ai.*) and the store.
  • Dashboard: the one in the image. gl.integrations.grafana_dashboard() returns the path of its JSON; import it in Dashboards → New → Import.
  • PromQL, share of answers that failed:
  sum(rate(groundlens_decisions_total{decision="FAIL"}[15m])) / sum(rate(groundlens_decisions_total[15m]))
  • Alert when more than 5 % fail:
  - alert: GroundLensFailRateHigh

expr: sum(rate(groundlens_decisions_total{decision="FAIL"}[15m])) / sum(rate(groundlens_decisions_total[15m])) > 0.05 for: 10m

  • Try it: docker run -p 3000:3000 -p 4318:4318 grafana/otel-lgtm, then python examples/observability/credit_copilot.py grafana --minutes 5. Tested on Grafana 12 with Tempo and Prometheus.

Claude, Codex, Cursor, VS Code and other MCP clients · uvx --from "groundlens[mcp]" groundlens mcp

Your assistant checks its own draft before it answers. Three read-only tools over stdio: verify_answer, verify_run, verify_records. Needs uv.

  • Claude Code (plugin: the MCP server plus a skill that tells Claude when to check):
  claude plugin marketplace add groundlens-dev/groundlens

claude plugin install groundlens@groundlens

  • Codex:
  codex mcp add groundlens -- uvx --from "groundlens[mcp]" groundlens mcp
  • Any MCP client (Claude Desktop, Windsurf, Zed...):
  { "mcpServers": { "groundlens": { "command": "uvx", "args": ["--from", "groundlens[mcp]", "groundlens", "mcp"] } } }

With the package installed (pip install "groundlens[mcp]"), "command": "groundlens-mcp" is enough.

  • Nothing to install: the Hugging Face Space is also a remote MCP server, with verify_answer, at https://groundlens-groundlens.hf.space/gradio_api/mcp/.

OpenClaw · clawhub install groundlens

A skill on ClawHub, the skill registry of OpenClaw. Before your assistant sends an answer with figures taken from your documents, it runs groundlens verify on its draft:

  • PASS: the answer goes out.
  • FAIL: it fixes the figure from the source and checks again.
  • REVIEW: the answer goes out, saying which figure it could not confirm.

Runs on your machine, with no API key and no second model. The skill is in plugins/groundlens/skills/groundlens, the same one the Claude Code plugin uses. OpenClaw can also use the MCP server directly, with openclaw mcp add.

Where records are kept · sink=

check() returns only after the signed record is stored. If it cannot be stored, check() raises and no decision comes back. Each sink keeps a chain: every record carries the hash of the one before it.

SinkWhat you passHow it stays append-only
gl.sinks.jsonl("records/")a directory or a .jsonl pathone JSON line per record, flushed to disk and locked on every write. For development and single machines
gl.sinks.s3_object_lock(boto3.client("s3"), "bucket")your S3 client and a bucket created with Object Lockone object per record, written only if absent; retain_days= adds a retention date (COMPLIANCE mode by default)
gl.sinks.azure_blob(container_client)an azure.storage.blob.ContainerClientone blob per record, never overwritten; give the container a time-based immutability policy
gl.sinks.postgres(psycopg.connect(...))any DB-API connectionone row per record; the table is created if missing, and its keys stop a position from being written twice or a chain from forking
impo

Only the beginning is shown; read the rest in the repo

Ask PopNx