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/AEndrix03/GraftInstalling this writes the configuration, not the program: `python` runs a file from the repository, so clone it first and make the path in the command match where you put it.
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.
[](https://agentmods.dev/mcp/aendrix03/graft/claude-ai-graft)<a href="https://agentmods.dev/mcp/aendrix03/graft/claude-ai-graft"><img src="https://agentmods.dev/badge/mcp/aendrix03/graft/claude-ai-graft/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/aendrix03/graft/claude-ai-graft"><img src="https://agentmods.dev/badge/mcp/aendrix03/graft/claude-ai-graft.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
graft 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 1mo 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
{
"graft": {
"command": "python",
"args": [
"C:/personal/Graft/integrations/mcp-server/server.py"
],
"env": {
"GRAFT_BIN": "C:/Users/aredegalli/.graft/bin/graft.exe"
}
}
}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.
- 1mo ago First seen · 11 lines scan A afefaed07610
graft is an MCP server published in the GitHub repository AEndrix03/Graft (50 stars, last pushed 19d ago), licensed Apache-2.0. 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-30.
Other mcp servers, from other repositories
ori-memory
Persistent memory infrastructure for AI agents. Identity, knowledge graph, and search. Runs locally from the ori-memory npm package.
atomicmemory
MCP server "atomicmemory" as configured in atomicstrata/atomicmemory. Runs locally from the atomicmemory-mcp npm package. Needs 7 environment variables to run.
mitos
Architectural decision memory for LLM-native workflows — markdown for humans, a graph for agents. Runs locally from the mitos-adr Python package.
kernal-mcp
Graph-native memory for AI agents: a knowledge graph built from conversation, via MCP. Runs locally from the kernal-mcp npm package.
centered-agent-memory
MCP server "centered-agent-memory" as configured in arlinamid/centered-agent-memory. Runs locally from the centered-agent-memory npm package.
engram
Your local, private memory layer. Index your notes and files, then recall anything with citations and temporal reasoning — 100% on your machine. Runs locally from the @jnmetacode/engram npm package.