← Index

GRAFOMEM CGR Capture

com.grafomem/cgr-capturev0.1.0Other

Record agent judgments and their real outcomes on GRAFOMEM Cloud. Capture now, score later.

The current version, v0.1.0, was published to the official MCP registry on 2026-08-24. It is distributed as grafomem-cgr on PyPI, filed under Other by this index, and declares 6 environment variables. Removals and unreachable sources are measured across every server this index tracks, contract drift across the servers that answer in consecutive snapshots; the index's current counts put this record in context.

In-path gate · all MCP tools

Using GRAFOMEM CGR Capture in Claude, Cursor, Gemini CLI, Cline, or Zed?

MCP tool contracts can change remotely with no version bump. The mcpindex gate pins each contract and HOLDs the call when it drifts-before your agent acts. Zero credentials. This is not the package install for this server itself (use Install this server for that).

Install the mcpindex gate (one command)

Rewrites your MCP host config so each server launches behind the gate. Inspect first: curl -fsSL https://mcpindex.ai/install.sh | less

uv tool install mcpindex-gate && mcpindex-config-wire
Trust verdict · v1 advisory · method
NOT YET SCREENEDno verdict on file

Verdict not yet evaluated for this tool. The semantic screen takes adversarial cases first; coverage rolls out as the corpus expands (15/150 labels to graduation). The deterministic conformance probe is built but has not yet run on the public corpus, so a recorded verdict here is REVIEW or UNVERIFIED, never a clearing ALLOW. Until a verdict is recorded, an agent should treat this tool as not-yet-cleared and fall back to its own checks. Method: the eval, four-state verdict, honest limits.

Own this server? Screen its description →

That verdict was true at screening time (snapshot 2026-08-24).

Contracts can change after screening, with no version bump. The gate pins GRAFOMEM CGR Capture’s tool contracts on first sight and holds any silent change before your agent acts - the check that keeps being true on Tuesday.

See your first HOLD in 2 minutes →

Related: how to trust an MCP server · screen before install · silent contract drift

Environment variables
GRAFOMEM_CGR_TENANT_KEY
requiredsecret

Your GRAFOMEM Cloud tenant API key (X-API-Key). Needs decisions:read for the durability guard.

GRAFOMEM_CGR_TENANT
required

The tenant id you expect that key to resolve to. If the key resolves to any other tenant, every write is refused.

GRAFOMEM_CGR_ROLE_KEYS_JSON

Role handles to public agent_key (64-hex Ed25519), inline as JSON. Example: {"cc-builder@acme":"<64-hex>"}. Use this or GRAFOMEM_CGR_ROLE_KEYS.

GRAFOMEM_CGR_ROLE_KEYS

Path to a JSON file with the same role-handle to public agent_key mapping. Use this or GRAFOMEM_CGR_ROLE_KEYS_JSON.

GRAFOMEM_CGR_FORBIDDEN_TENANTS

Comma-separated tenant ids to always refuse, even if pinned by mistake. Put your production tenant here.

GRAFOMEM_API

GRAFOMEM Cloud base URL. Defaults to https://api.grafomem.com.

MCP quality score · maturity, not trust · methodology
freshness
25
completeness
20
installability
25
documentation
15
stability
5
Alternatives in Other