Context7
Up-to-date docs for AI agents
作者提供的说明(英文原文)
Guardrails for LLM answers: exact checks against sources, PASS/REVIEW/FAIL, signed records.
这三项永远不会合并成一个分数:意见、测量和人气是不同的东西。
我们还没有为它写通俗的介绍。下面是我们从注册中心读取到的事实。
选择你使用的 AI 应用,然后复制设置。
你需要
你用的是哪个应用?
在上方选择你的应用。我们会记住它,下次按钮会显示“安装到 …”。
打开 Claude Desktop → Settings → Developer → Edit Config,把下面的内容粘贴到 claude_desktop_config.json
{
"mcpServers": {
"groundlens": {
"command": "uvx",
"args": [
"groundlens",
"mcp"
]
}
}
}在终端中运行这条命令
claude mcp add groundlens -- uvx groundlens mcp粘贴到项目中的 .cursor/mcp.json,或 ~/.cursor/mcp.json
{
"mcpServers": {
"groundlens": {
"command": "uvx",
"args": [
"groundlens",
"mcp"
]
}
}
}浏览器会先询问是否打开应用,然后应用会显示设置并请你确认。密钥的值会留空,由你自己填写。
粘贴到项目中的 .vscode/mcp.json
{
"servers": {
"groundlens": {
"type": "stdio",
"command": "uvx",
"args": [
"groundlens",
"mcp"
]
}
}
}浏览器会先询问是否打开应用,然后应用会显示设置并请你确认。密钥的值会留空,由你自己填写。
这个服务器在你的电脑上运行,而 ChatGPT 只能连接互联网上的服务器。请选择其他应用。
你的选择通过 Cookie 保存在这台设备上,无需账户。
这些设置是根据作者在注册中心的条目生成的。如果 README 的写法不同,请以 README 为准。
它在你的电脑上运行;安装后,工具列表会显示在你的 AI 应用中。
我们检查的是任何人都能看到的信息;我们没有阅读代码。不适用的检查项不计入总数。 · 检查于 2026年11月7日
注册名称已通过 GitHub 账户 groundlens-dev 验证,该账户拥有此仓库
我们还没有从 GitHub 读取这个仓库
我们还没有从 GitHub 读取这个仓库
它在你的电脑上运行,没有互联网端点
在你的电脑上运行,改用本地设置
它在你的电脑上运行;我们只能读取互联网端点的工具列表
与注册中心里这个分类中所有活跃的服务器比较。只有当发布者拥有该仓库时,星标数才计入。
它在 1 项适用的基础检查中通过了 1 项。我们没有阅读代码。在添加密钥或令牌之前,请先看看这个服务器要求哪些权限,并使用只具备所需权限的密钥。
注册中心没有列出必需的密钥,不过有些服务器会在首次使用时要求你登录。
它在你的电脑上运行。你的 AI 应用会在需要时启动它,数据不会经过作者的服务器(除非它自己调用在线服务)。
GitHub 仓库最后更新于–,最新版本(6.0.5)于21天前进入注册中心。
支持 MCP 的应用,例如 Claude Desktop、Claude Code、Cursor 和 VS Code。你的电脑上还需要有 Python (uv)。
同一分类中有:Context7, Codebase Memory, Exa
同一分类中其他作者的服务器,按星标数排序。
如何看卡片:★ GitHub 星标i三大支柱:评价 · 检查 · 使用情况i更新 = 最新版本发布到注册中心的时间i
Up-to-date docs for AI agents
Codebase knowledge graph for AI agents — 162 languages, sub-ms queries, 99% fewer tokens.
Connect AI agents to Exa for web search, content fetching, and multi-step research.
按原文从作者的仓库复制。PopNx MCP 没有审查或背书其内容。HTML、图片和脚本已被移除。链接会离开本站。
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
# 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.
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:
PASS, REVIEW or FAIL, on the check and on its trace. Filter traces by it, chart it, export it.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.groundlens.scope.contradicted), policy, and the id and hash of the signed record behind it.generation observation with the model name, next to your own model calls.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.
groundlens_decisions_total{decision, policy}, groundlens_reasons_total{reason, decision}, groundlens_check_duration_seconds{stage} with stage total, engine, judge, sign, store.groundlens.check with groundlens.decision, groundlens.reasons, record id and hash; children per verifier, the judge (gen_ai.*) and the store.gl.integrations.grafana_dashboard() returns the path of its JSON; import it in Dashboards → New → Import. sum(rate(groundlens_decisions_total{decision="FAIL"}[15m])) / sum(rate(groundlens_decisions_total[15m]))
- alert: GroundLensFailRateHigh
expr: sum(rate(groundlens_decisions_total{decision="FAIL"}[15m])) / sum(rate(groundlens_decisions_total[15m])) > 0.05 for: 10m
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 plugin marketplace add groundlens-dev/groundlens
claude plugin install groundlens@groundlens
codex mcp add groundlens -- uvx --from "groundlens[mcp]" groundlens mcp
{ "mcpServers": { "groundlens": { "command": "uvx", "args": ["--from", "groundlens[mcp]", "groundlens", "mcp"] } } }
With the package installed (pip install "groundlens[mcp]"), "command": "groundlens-mcp" is enough.
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:
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.
| Sink | What you pass | How it stays append-only |
|---|---|---|
gl.sinks.jsonl("records/") | a directory or a .jsonl path | one 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 Lock | one 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.ContainerClient | one blob per record, never overwritten; give the container a time-based immutability policy |
gl.sinks.postgres(psycopg.connect(...)) | any DB-API connection | one 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只显示了开头部分;其余内容请在仓库中阅读