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/acryldev/acrylInstalling this writes the configuration, not the program: `graft` has to be on your PATH already, or the server will not start.
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/acryldev/acryl/graft)<a href="https://agentmods.dev/mcp/acryldev/acryl/graft"><img src="https://agentmods.dev/badge/mcp/acryldev/acryl/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/acryldev/acryl/graft"><img src="https://agentmods.dev/badge/mcp/acryldev/acryl/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 27d 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.
This is a copy
100% identical to graft — 0 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
What it actually says
{
"graft": {
"command": "graft",
"args": [
"mcp"
]
}
}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.
- 27d ago First seen · 8 lines scan A b240b3c98e96
graft is an MCP server published in the GitHub repository acryldev/acryl (256 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. It is 100% identical to graft, differing in 0 lines, and is treated as a copy.
Other mcp servers, from other repositories
dsh-feed
A local index that combines GitHub data about the dsh-plugin topic with npm registry data. It can be queried by agent tools, a command-line program, or an MCP server.
dsh-mcp-gateway
MCP server "dsh-mcp-gateway" as configured in siddhartha-yz/dsh-mcp-gateway. Runs locally from the dsh-mcp-gateway Python package.
repogate
Reusable repository structure baselines for architecture-aware pull request gates. Runs locally from the repogate npm package.
dsh-mediacrawler
MCP server "dsh-mediacrawler" as configured in xwh-01/dsh-mediacrawler. Runs locally from the dsh-mediacrawler Python package.
gpt-dsh-bridge
MCP server "gpt-dsh-bridge" as configured in baochaofan0404/gpt-dsh-bridge. Runs locally from the gpt-dsh-bridge npm package.
dsh-artifact-promotion-proof
MCP server "dsh-artifact-promotion-proof" as configured in dongsheng123132/dsh-artifact-promotion-proof. Runs ${PLUGIN_ROOT}/mcp-server.mjs with node.