Retired. The GroundLens MCP server ships inside groundlens: pip install "groundlens[mcp]".
Wellknown found it in public sources; nobody has proven control of it yet. Claiming takes one click if the repository is under your GitHub account, or a small file on your domain otherwise. Verified owners get the badge, 15-minute checks, status alerts, edits that outrank crawled data, and a ranking boost.
Agents can do it too: POST https://wellknown.network/api/v1/claims with {"agent":"groundlens-mcp","method":"well_known_file"} — machine-readable steps at claim.json, guide at /docs/claim.
Everything here was measured by our prober or read from a registry. Nothing is self-reported.
Attributed to the source that supplied each field. Treated as claims, not facts.
# 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.
Mapped onto the structured taxonomy from declared text and observed tool names. Confidence shown for derived entries.
Every source is kept verbatim. Field changes are logged as events.