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.
npx agentmods add mcp/grainulation/grainulator/silogit clone --depth 1 https://github.com/grainulation/grainulatorGrade A, and why
silo 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 yesterday.
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
{
"silo": {
"type": "stdio",
"command": "npx",
"args": [
"-y",
"@grainulation/silo",
"serve-mcp"
],
"env": {
"SILO_STORE": "${CLAUDE_PLUGIN_DATA}/silo"
}
}
}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.
- yesterday First seen · 14 lines scan A 173a07fab1ab
silo is an MCP server published in the GitHub repository grainulation/grainulator (87 stars, last pushed 4mo 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-30.
Other mcp servers, from other repositories
fedlex-sparql
MCP server "fedlex-sparql", hosted remotely at mcp.bettercallclaude.ch, as configured in fedec65/bettercallclaude.
megaplan
MCP server for Megaplan — tasks, deals, project management (Russia). Runs locally from the @theyahia/megaplan-mcp npm package. Needs 2 environment variables to run.
megaplan-mcp
MCP server for Megaplan — tasks, deals management via API v3. Runs locally from the @theyahia/megaplan-mcp npm package. Needs 1 environment variable to run.
p4plan-mcp
MCP server for P4 Plan — tasks, sprints, bugs, comments, custom fields via GraphQL API. Runs locally from the @perforce/p4plan-mcp npm package. Needs 3 environment variables to run.
backlog-mcp
Context & memory engineering for AI agents — a markdown-backed, local-first storage engine (substrates, agent memory, progressive disclosure). Your backlog is your agent's memory. Runs locally from the backlog-mcp npm package.
docs-langchain
MCP server "docs-langchain", hosted remotely at docs.langchain.com, as configured in langchain-ai/langchain.