Stratum MCP runs on your own machine — the client starts it, so there is no endpoint to ping. 118 installs a week from npm. Last commit 24 Oct 2026.
Structured execution for coding agents: contracts, postconditions, gates, guardrails.
We read the source, 1 d ago · rules 995398eba69f
What this server is able to do. For an MCP server this is often the job itself — a terminal server runs commands because that is what it is for. Listed so you know what you are plugging in, not as an accusation.
const relativePath = path.join(prefix, filename);
Select review lenses for the implementation results ${execute.output}.
const child = spawnSync(process.execPath, [...extraNodeFlags(), "--import", new URL("./bootstrap.mjs", import.meta.url).href, fileURLToPath(new URL("./stratum.ts", import.meta.url)), ...process.argv.slice(2)], { stdio: "inherit" });
Object.entries(process.env).filter(([name]) => !name.startsWith("GIT_")),
Is this your server and something here is wrong? Tell us — corrections are free and do not require a plan.
We found places where it runs commands, builds paths or queries from values it is given. None of that is a flaw by itself — it becomes one when the code changes, and code changes quietly between releases. We re-read it on every one.
This server runs on your own machine — install it with the package manager and the client starts it for you. Package name taken from the official registry entry.
claude mcp add stratum-mcp -- npx -y @smartmemory/stratum
{
"mcpServers": {
"stratum-mcp": {
"command": "npx",
"args": [
"-y",
"@smartmemory/stratum"
]
}
}
}
[mcp_servers.stratum-mcp]
command = "npx"
args = ["-y", "@smartmemory/stratum"]
{
"mcpServers": {
"stratum-mcp": {
"command": "npx",
"args": [
"-y",
"@smartmemory/stratum"
]
}
}
}
{
"servers": {
"stratum-mcp": {
"type": "stdio",
"command": "npx",
"args": [
"-y",
"@smartmemory/stratum"
]
}
}
}
Merge gates and safety checks for AI coding agents via MCP.
Structured execution trace and span logging for AI agents
Operating contracts for AI agents. Structured instructions compiled into system prompts.
Verifiable execution for AI agents: Ed25519-signed work contracts and audit trails.
Local-first control plane for coding agents: routing, reservations, and guardrails.
Agent-native CLI: provenance, cost governance, and execution contracts for AI agents.
Local-first architecture guardrails and project context for JS/TS AI coding agents.
Kubernetes MCP server with RBAC-style, context-scoped guardrails for AI agents.
Answers built from our own checks of this server.