agentmods.dev

governed-memory

governed-memory is an MCP server for Claude Code from leonardoeverling-spec/governed-context. Its token cost is not measured, scanned A, original, MIT.

A local MCP server for reading and managing governed memories from the governed-context project. It runs with Node.js and uses configured files and a memory directory.

In plain words
What is it for?
Use it to connect an agent to governed Markdown memories, optional decision records, and an optional document describing the current work state.
Why use it?
It provides the server component needed to use controlled memory storage with an agent.

MCP server for Claude Code

Written for Claude Code: ${CLAUDE_PLUGIN_ROOT} variable. Also seen: listed in a Claude config.

Runs only inside its plugin — its command needs a path that Claude Code sets for a plugin’s own hooks and for nothing else. Install the plugin, not this.

Part of the governed-context plugin — 1 skill, 1 MCP server shipped together

not rated 0 1mo ago A scan tokens not measured original MIT
View the source file leonardoeverling-spec/governed-context
Install

Getting it into your agent

This one installs as part of its plugin. Adding the marketplace and installing the plugin brings it with everything else the plugin ships.

Claude Code
/plugin marketplace add leonardoeverling-spec/governed-context
Claude Code
/plugin install governed-context

Made for: Claude Code.

Or install governed-context, the plugin that ships this one along with the rest of its 1 skill, 1 MCP server.

Wrote 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.

agentmods badge for governed-memory

README.md
[![agentmods](https://agentmods.dev/badge/mcp/leonardoeverling-spec/governed-context/governed-memory.svg)](https://agentmods.dev/mcp/leonardoeverling-spec/governed-context/governed-memory)
Your own site
<a href="https://agentmods.dev/mcp/leonardoeverling-spec/governed-context/governed-memory"><img src="https://agentmods.dev/badge/mcp/leonardoeverling-spec/governed-context/governed-memory.svg" alt="Measured on agentmods" height="20"></a>
Per session not measured What this adds to a session before it is invoked.
When invoked not measured Not applicable: nothing here is loaded into a session.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found in the catalogue.
Security

Grade A, and why

governed-memory 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 5d 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.

.mcp.json · 14 lines

What it actually says

{
  "governed-memory": {
    "type": "stdio",
    "command": "node",
    "args": [
      "${CLAUDE_PLUGIN_ROOT}/mcp/server.mjs"
    ],
    "env": {
      "GOVERNED_MEMORY_DIR": "${user_config.governed_memory_dir}",
      "GOVERNED_DECISIONS_FILE": "${user_config.governed_decisions_file}",
      "GOVERNED_STATE_FILE": "${user_config.governed_state_file}"
    }
  }
}
Changes

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.

  1. 5d ago First seen · 14 lines scan A 3fe08bf6ec27

Subscribe to this mod's changes

governed-memory is an MCP server published in the GitHub repository leonardoeverling-spec/governed-context (0 stars, last pushed 1mo 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.

EvaluationMemory and contextai-memoryclaude-codeclaude-plugincontext-engineeringmcp
Related

Other mcp servers, from other repositories

omega-memory

MCP server "omega-memory" as configured in omega-memory/omega-memory. Launched with python3.11 -m omega.server.mcp_server.

omega-memory/omega-memory · not measured

memseek

MCP server "memseek", hosted remotely, as configured in memseekai/memseek.

memseekai/memseek · not measured

aidimag

Persistent, verified memory for AI coding agents: recall, capture, guardrails, review queue. Runs locally from the aidimag npm package. Needs 3 environment variables to run.

AiDimag/aidimag · not measured

id

Git-like protocol and tooling for portable human-AI identity context. Runs locally from the id-protocol Python package.

markoblogo/ID · not measured

groundmemory

Persistent, semantic memory for AI agents - mcp-native, local-first, framework-agnostic, production-ready. Runs locally from the groundmemory Python package.

huss-mo/GroundMemory · not measured

logic-server

Agent reasoning, memory, and token-optimized context for AI applications. Runs locally from the nocturnusai-mcp npm package. Needs 4 environment variables to run.

Auctalis/nocturnusai · not measured