groundlens-deprecated
Official# groundlens-mcp
**Moved.** The GroundLens MCP server ships inside the `groundlens` package.
This repository is archived, and the `groundlens-mcp` package on PyPI installs
nothing but a message that says so.
```bash
pip install "groundlens[mcp]"
groundlens-mcp
```
```json
{ "mcpServers": { "groundlens": { "command": "groundlens-mcp" } } }
```
With nothing installed, through [uv](https://docs.astral.sh/uv/):
```json
{
"mcpServers": {
"groundlens": {
"command": "uvx",
"args": ["--from", "groundlens[mcp]", "groundlens-mcp"]
}
}
}
```
Keep `--from "groundlens[mcp]"`: a bare `uvx groundlens-mcp` installs this
old package instead of the server.
The server has three tools: `verify_answer`, `verify_run` and
`verify_records`. GroundLens is guardrails for LLM answers: it checks an LLM
answer against its sources without a model, decides PASS, REVIEW or FAIL under
your policy, and keeps a signed record.
- Source: https://github.com/groundlens-dev/groundlens
- Site: https://groundlens.dev
- MCP registry: `io.github.groundlens-dev/groundlens`
Apache-2.0.
TDQS
Scored across 3 tools
groundlens_check is a wrapper that automatically dispatches to the same SGI and DGI methods exposed as separate tools, so the purposes overlap by design. The descriptions help clarify context vs. no-context usage, but an agent could still be unsure whether to call the main check tool or the method-specific one.
All tools share the groundlens_ prefix and use lowercase snake_case, which is readable and predictable. The pattern is slightly inconsistent because check is a verb while sgi and dgi are method acronyms, but this is a minor deviation rather than chaotic naming.
Three tools is a well-scoped count for a focused grounding-check server. The auto-selecting dispatcher plus the two explicit methods is compact and each tool has a documented role.
The set covers the full grounding-check lifecycle: automatic selection, context-based SGI, and context-free DGI. Fact-level verification is explicitly out of scope and delegated via handoff, so there is no obvious missing tool for the server's stated purpose.