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/jaytyagiwithai-wq/tooldock_1.0Wrote 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/jaytyagiwithai-wq/tooldock_1.0/tooldock-ai)<a href="https://agentmods.dev/mcp/jaytyagiwithai-wq/tooldock_1.0/tooldock-ai"><img src="https://agentmods.dev/badge/mcp/jaytyagiwithai-wq/tooldock_1.0/tooldock-ai/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/jaytyagiwithai-wq/tooldock_1.0/tooldock-ai"><img src="https://agentmods.dev/badge/mcp/jaytyagiwithai-wq/tooldock_1.0/tooldock-ai.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
tooldock-ai 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 11d 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
{ "tooldock-ai": { "command": "uvx", "args": [ "tooldock-ai" ] } }
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.
- 11d ago First seen · 8 lines scan A f84f1bf3570d
tooldock-ai is an MCP server published in the GitHub repository jaytyagiwithai-wq/tooldock_1.0 (1 stars, last pushed 1mo 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
codeflow-readonly
MCP server "codeflow-readonly" as configured in xiaojiou176-open/codeflow. Launched with bash ./bin/run-codeflow-readonly-mcp.sh.
tokenknows
TokenKnows MCP server — distill AI coding sessions (Claude Code / Codex / Cursor) into weekly reports, ADRs and a knowledge graph on your self-hosted workbench. Runs locally from the tokenknows-mcp Python package. Needs 5 environment variables to run.
youtube-ai
YTAI: Python YouTube SDK, CLI, and MCP server without user-supplied API keys. Runs locally from the youtube-ai Python package.
agent-center-app
A self-hostable notification layer for AI agents — they report what they did and what needs you; you read one feed and click out to where the work lives. Runs locally from the agent-center-app Python package.
demo-catalog
MCP server "demo-catalog" as configured in ownasquare/context-loom. Launched with demo-mcp-server.
mcp-a2a-bridge
Bidirectional bridge between MCP (Model Context Protocol) and A2A (Agent-to-Agent) protocols. Runs locally from the mcp-a2a-bridge Python package.