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/jrullan/ducklabInstalling this writes the configuration, not the program: `https://github.com/jrullan/ducklab/releases/download/v0.7.0/ducklab-mcp.mcpb` 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/jrullan/ducklab/mcp-registry-ducklab)<a href="https://agentmods.dev/mcp/jrullan/ducklab/mcp-registry-ducklab"><img src="https://agentmods.dev/badge/mcp/jrullan/ducklab/mcp-registry-ducklab/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/jrullan/ducklab/mcp-registry-ducklab"><img src="https://agentmods.dev/badge/mcp/jrullan/ducklab/mcp-registry-ducklab.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
ducklab 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 2mo 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
{
"ducklab": {
"command": "https://github.com/jrullan/ducklab/releases/download/v0.7.0/ducklab-mcp.mcpb",
"args": [],
"env": {}
}
}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.
- 2mo ago First seen · 7 lines scan A 7727a04e9f08
ducklab is an MCP server published in the GitHub repository jrullan/ducklab (11 stars, last pushed 2d 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-31.
Other mcp servers, from other repositories
orchestrator
MCP server "orchestrator" as configured in synaptixs/spine. Runs locally from the synaptixs-spine[mcp,docs,c,cpp,csharp,go,java,kotlin,perl,php,sql,typescript]@latest Python package.
neuraforge-office-pptx
MCP server for creating, reading, and editing PowerPoint, Word, Excel, and CSV documents. 32 tools. Runs locally from the @neuraforge/office-mcp npm package.
neuraforge-loadtest
MCP server for load testing APIs. Run load tests, stress tests, and regression detection from any AI agent. Runs locally from the @neuraforge/loadtest-mcp npm package.
a11y-mcp
MCP server for performing accessibility audits on webpages. Runs locally from the a11y-mcp npm package.
ffmpeg-mcp
MCP server "ffmpeg-mcp" as configured in vikisingh23/neuraforge-ai. Runs locally from the ffmpeg-mcp npm package.
style-dna-ghostwriter
MCP server "style-dna-ghostwriter" as configured in Kaifazad/Style-DNA-Ghostwriter. Runs locally from the style-dna-ghostwriter Python package.