Getting it into your agent
One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.
git clone --depth 1 https://github.com/GNS-Foundation/grafomemWrote this? Show the measurements
A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.
[](https://agentmods.dev/mcp/gns-foundation/grafomem/cgr-read-cgr-capture)<a href="https://agentmods.dev/mcp/gns-foundation/grafomem/cgr-read-cgr-capture"><img src="https://agentmods.dev/badge/mcp/gns-foundation/grafomem/cgr-read-cgr-capture/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/mcp/gns-foundation/grafomem/cgr-read-cgr-capture"><img src="https://agentmods.dev/badge/mcp/gns-foundation/grafomem/cgr-read-cgr-capture.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
cgr-capture scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 9d ago.
A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.
Nothing flagged
None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.
What it actually says
{
"cgr-capture": {
"command": "uvx",
"args": [
"grafomem-cgr"
],
"env": {
"GRAFOMEM_CGR_TENANT_KEY": "",
"GRAFOMEM_CGR_TENANT": "",
"GRAFOMEM_CGR_ROLE_KEYS_JSON": "",
"GRAFOMEM_CGR_ROLE_KEYS": "",
"GRAFOMEM_CGR_FORBIDDEN_TENANTS": "",
"GRAFOMEM_API": "https://api.grafomem.com"
}
}
}What else server.json configures
This page is one entry in a file that holds 2. Installing the file brings all of them; each is measured and scanned on its own page.
What this file has done since we first saw it
Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.
- 9d ago First seen · 16 lines scan A e48fe39c8e05
cgr-capture is an MCP server published in the GitHub repository GNS-Foundation/grafomem (2 stars, last pushed today), licensed MIT. Its token cost is not measured: an MCP server costs its tool schemas, not its config file. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other mcp servers, from other repositories
code-review-graph
MCP server "code-review-graph" as configured in varun29ankuS/shodh-memory. Runs code_review_graph with python.
lians
Correct, temporal, and auditable memory infrastructure for AI agents. Runs locally from the lians-sdk Python package. Needs 5 environment variables to run.
mnemo-mcp
Open-source MCP Server for persistent AI memory with embedded sync. Runs locally from the mnemo-mcp Python package. Needs 1 environment variable to run.
memory
A Python library for control memory. Runs locally from the memory Python package. Needs 1 environment variable to run.
mcp
Model Context Protocol server for Citadel: encrypted memory as MCP tools. Runs locally from the citadeldb-mcp Python package. Needs 1 environment variable to run.
governed-brain
MCP server "governed-brain" as configured in jeremylongshore/bobs-big-brain-plugin. Runs plugin-runtime/bootstrap.cjs with node. Needs 3 environment variables to run.