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/toolprint/mcping-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/toolprint/mcping-mcp/docker)<a href="https://agentmods.dev/mcp/toolprint/mcping-mcp/docker"><img src="https://agentmods.dev/badge/mcp/toolprint/mcping-mcp/docker/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/toolprint/mcping-mcp/docker"><img src="https://agentmods.dev/badge/mcp/toolprint/mcping-mcp/docker.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
docker 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.
This is a copy
100% identical to docker — 0 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
What it actually says
{
"docker": {
"type": "stdio",
"command": "uvx",
"args": [
"mcp-server-docker"
],
"env": {}
}
}What else .mcp.json configures
This page is one entry in a file that holds 4. Installing the file brings all of them; each is measured and scanned on its own page.
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 · 10 lines scan A 477d4f6d4a8d
docker is an MCP server published in the GitHub repository toolprint/mcping-mcp (1 stars, last pushed 1y 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. It is 100% identical to docker, differing in 0 lines, and is treated as a copy.
Other mcp servers, from other repositories
sandbase-harness
MCP server "sandbase-harness" as configured in sandbaseai/sandbase-harness. Runs in Docker (ghcr.io/sandbaseai/sandbase-harness-mcp:0.3.8). Needs 2 environment variables to run.
mcp-proxmox
MCP server for managing Proxmox VE clusters through AI assistants. Runs locally from the mcp-proxmox Python package.
orbit-sentinel-mcp
MCP server "orbit-sentinel-mcp" as configured in Viventine-Space/orbit-sentinel-mcp. Runs in Docker (ghcr.io/viventine-space/orbit-sentinel-mcp:0.6.6).
dockerfile-generator-ai-mcp
MCP server for dockerfile generator ai. Features generate dockerfile, generate compose, optimize image. From MEOK AI Labs. Runs locally from the dockerfile-generator-ai-mcp Python package.
devops-ai-mcp
Devops Ai automation via MCP. Includes docker compose generator, cicd pipeline builder, log analyzer. By MEOK AI Labs. Runs locally from the devops-ai-mcp Python package.
docker-helper-ai-mcp
Docker Helper Ai MCP server. Tools: generate dockerfile, parse compose, optimize image. Built by MEOK AI Labs. Runs locally from the docker-helper-ai-mcp Python package.