Ext Ops Panel
Open dashboard
Comparison

Attest vs GroundLens

Attest is an MCP server published by dev-prathap. Marketplaces we read that list it: 1 (Official MCP Registry). GroundLens is an MCP server published by groundlens-dev. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-16. This pair was picked by a reader, not by our comparison rule, so search engines are asked not to index the page.

Where each is published

Where each is published
MarketplaceAttestGroundLens
Official MCP Registry Listed
Version: 0.1.0
Downloads/month (PyPI): 206
Downloads/week (PyPI): 22
Forks (GitHub): 0
Stars (GitHub): 1
Not marked · First seen
Listed
Version: 6.0.5
Downloads/month (PyPI): 1 229
Downloads/week (PyPI): 154
Forks (GitHub): 4
Stars (GitHub): 7
Not marked · First seen

Each figure is the marketplace's own and is never added up across marketplaces. A marketplace that publishes no figure shows none: no number is not zero.

The facts side by side

Attest vs GroundLens
FactAttestGroundLens
Marketplaces that list it11
Stars (GitHub) (differs)1 (worse)7 (better)
Forks (GitHub) (differs)0 (worse)4 (better)
Last release (differs)Not published2026-10-16
Where it runs (differs)On your machine (attestlayer)On your machine (groundlens)
Transportstdiostdio
Tools it declaresNot publishedNot published
Environment variables it asks for (differs)11, secrets among them: 7Not published
LicenceNot statedNot stated
Repository (differs)github.com/dev-prathap/attestgithub.com/groundlens-dev/groundlens
Changes in the last 7 days (differs)07
First seen2026-10-112026-10-11

Lines where the two differ have a tinted background and bold values. Where the data itself says which value is better (more marketplaces, a larger figure of the same marketplace, a fresher release, a verified mark on a marketplace that lists both), the better one is also marked green with ▲ and the worse one red with ▼. Where it runs, the transport, the tools, the settings, hooks, the bundle's parts, the licence and the week's changes are marked only as different: more or fewer is not better in itself.

What each says it does

Attest

In its own words, on Official MCP Registry:

Decide by policy, gate behind a human, verify by read-back, record a hash-chained ledger.

GroundLens

In its own words, on Official MCP Registry:

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

How to run each

Attest As a local MCP server: PyPI package

Claude Code
claude mcp add --env "GMAIL_TOKEN=<YOUR_GMAIL_TOKEN>" --env "GOOGLE_TOKEN=<YOUR_GOOGLE_TOKEN>" --env "GRAPH_TOKEN=<YOUR_GRAPH_TOKEN>" --env "HUBSPOT_TOKEN=<YOUR_HUBSPOT_TOKEN>" --env "LINEAR_API_KEY=<YOUR_LINEAR_API_KEY>" --env "NOTION_TOKEN=<YOUR_NOTION_TOKEN>" --env "SLACK_BOT_TOKEN=<YOUR_SLACK_BOT_TOKEN>" --transport stdio attest -- uvx attestlayer

Requires: GMAIL_TOKEN (secret), GOOGLE_TOKEN (secret), GRAPH_TOKEN (secret), HUBSPOT_TOKEN (secret), LINEAR_API_KEY (secret), NOTION_TOKEN (secret), SLACK_BOT_TOKEN (secret)

GroundLens As a local MCP server: PyPI package

Claude Code
claude mcp add --transport stdio groundlens -- uvx --from "groundlens[mcp]" groundlens mcp

Commands built only from what the marketplaces declare; the full set for every client is on each card.

Tools each declares

Neither one's marketplaces publish a list of tools, so there is nothing to compare.

Settings each asks for

The marketplaces of GroundLens publish no settings it asks for, so we do not compare settings.

What it can do: Attest · What it can do: GroundLens · Compare two other plugins

Data comes from the Official MCP Registry (registry.modelcontextprotocol.io), CC0 1.0. Figures come from our own regular passes over the marketplaces, last read on . We publish no contact details for plugin publishers.

Where the data comes from: how the catalog is built