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/Abhigyan-Shekhar/Waggle-mcpWrote 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/abhigyan-shekhar/waggle-mcp/waggle)<a href="https://agentmods.dev/mcp/abhigyan-shekhar/waggle-mcp/waggle"><img src="https://agentmods.dev/badge/mcp/abhigyan-shekhar/waggle-mcp/waggle/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/abhigyan-shekhar/waggle-mcp/waggle"><img src="https://agentmods.dev/badge/mcp/abhigyan-shekhar/waggle-mcp/waggle.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
waggle 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 10d 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
{
"waggle": {
"command": "node",
"cwd": "./plugins/waggle",
"args": [
"./plugins/waggle/bin/waggle-server-launcher.js",
"serve",
"--transport",
"stdio"
],
"env": {
"WAGGLE_BACKEND": "sqlite",
"WAGGLE_DB_PATH": "~/.waggle/waggle.db",
"WAGGLE_DEFAULT_TENANT_ID": "local-default",
"WAGGLE_MODEL": "deterministic",
"WAGGLE_STARTUP_MODE": "normal",
"WAGGLE_TRANSPORT": "stdio"
}
}
}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.
- 10d ago First seen · 20 lines scan A 584405ca9ee5
waggle is an MCP server published in the GitHub repository Abhigyan-Shekhar/Waggle-mcp (39 stars, last pushed 6d 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
verbative-memory
On-device memory system for AI coding agents — dual-layer engine (distilled facts + lossless event ledger), automatically captured and injected, exposed over MCP. Shared across agents, persistent across sessions; files in your repo. Runs locally from the verbative-memory npm package.
lycheemem
MCP server "lycheemem", hosted remotely at 127.0.0.1, as configured in LycheeMem/LycheeMem.
ori-memory
Persistent memory infrastructure for AI agents. Identity, knowledge graph, and search. Runs locally from the ori-memory npm package.
veracium
Provenance-aware memory for AI agents. Runs locally from the veracium Python package. Needs 3 environment variables to run.
superlocalmemory
MCP server "superlocalmemory" as configured in qualixar/superlocalmemory. Launched with ${CLAUDE_PLUGIN_ROOT}/scripts/slm-launch. Needs 1 environment variable to run.
inspeximus
MCP server "inspeximus" as configured in DanceNitra/inspeximus. Runs locally from the inspeximus[mcp] Python package. Needs 1 environment variable to run.