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-read)<a href="https://agentmods.dev/mcp/gns-foundation/grafomem/cgr-read-cgr-read"><img src="https://agentmods.dev/badge/mcp/gns-foundation/grafomem/cgr-read-cgr-read/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-read"><img src="https://agentmods.dev/badge/mcp/gns-foundation/grafomem/cgr-read-cgr-read.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
cgr-read 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 8d 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-read": {
"url": "https://mcp.grafomem.com/mcp",
"type": "streamable-http"
}
}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.
- 8d ago First seen · 6 lines scan A 99fa53144e73
cgr-read is an MCP server published in the GitHub repository GNS-Foundation/grafomem (2 stars, last pushed 2d ago), 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
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.
portable-agent-memory
MCP server "portable-agent-memory" as configured in skywaller0/Portable-Agent-Memory. Runs locally from the portable-agent-memory Python package.
tuskpoint
TuskPoint: a verifiable LangGraph checkpointer backed by Walrus decentralized storage, with semantic recall via MemWal. Drop-in MCP plugin: 'uvx tuskpoint-mcp'. Runs locally from the tuskpoint-mcp Python package. Needs 3 environment variables to run.
procheiron
Review gate for shared agent memory: an unreviewed or hand-edited memory never reaches your agents. MCP-native, zero dependencies. Runs locally from the procheiron Python package. Needs 1 environment variable to run.
agenthold
Shared versioned state for multi-agent AI workflows. Runs locally from the agenthold Python package.
comem
Local MCP server for append-only multi-agent coordination memory with an integrator-owned accepted projection and goal-level acceptance contracts. Runs locally from the coordination-memory-mcp Python package.