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/LiLara-AI/shadowgraphWrote 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/lilara-ai/shadowgraph/shadowgraph-unified-plugin)<a href="https://agentmods.dev/mcp/lilara-ai/shadowgraph/shadowgraph-unified-plugin"><img src="https://agentmods.dev/badge/mcp/lilara-ai/shadowgraph/shadowgraph-unified-plugin/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/lilara-ai/shadowgraph/shadowgraph-unified-plugin"><img src="https://agentmods.dev/badge/mcp/lilara-ai/shadowgraph/shadowgraph-unified-plugin.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
shadowgraph-unified-plugin 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
{ "shadowgraph-unified-plugin": { "command": "npx", "args": [ "-y", "shadowgraph-unified-plugin" ] } }
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 · 9 lines scan A 70a8143d2802
shadowgraph-unified-plugin is an MCP server published in the GitHub repository LiLara-AI/shadowgraph (3 stars, last pushed 5d 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.
Other mcp servers, from other repositories
remnic
MCP server "remnic", hosted remotely at localhost, as configured in joshuaswarren/remnic.
memorywhale
MCP server "memorywhale" as configured in wuisabel-gif/MemWhale. Launched with mw-mcp.
local-memory-mcp
Persistent local AI memory. SQLite + FTS5 + vector search, knowledge graph. No cloud, no API keys. Runs locally from the @studiomeyer/local-memory-mcp npm package. Needs 4 environment variables to run.
LINZA-MCP
Local-first MCP sidecar for agent workspaces, artifacts, review intents, and context export. Runs locally from the linza-mcp Python package. Needs 9 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.
plaud
MCP server "plaud" as configured in Gunnarguy/PlaudBlender. Runs locally from the @plaud-ai/mcp npm package.