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/kamil5b/db2toonWrote 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/kamil5b/db2toon/db2toon-mcp)<a href="https://agentmods.dev/mcp/kamil5b/db2toon/db2toon-mcp"><img src="https://agentmods.dev/badge/mcp/kamil5b/db2toon/db2toon-mcp/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/kamil5b/db2toon/db2toon-mcp"><img src="https://agentmods.dev/badge/mcp/kamil5b/db2toon/db2toon-mcp.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
db2toon-mcp 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 9d 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
{
"db2toon-mcp": {
"command": "docker",
"args": [
"run",
"-i",
"--rm",
"ghcr.io/kamil5b/db2toon:v1.4.4"
],
"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.
- 9d ago First seen · 12 lines scan A 928cf8b84e13
db2toon-mcp is an MCP server published in the GitHub repository kamil5b/db2toon (5 stars, last pushed 28d 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
mcp-toolbox
MCP server "mcp-toolbox" as configured in googleapis/mcp-toolbox. Runs in Docker (us-central1-docker.pkg.dev/database-toolbox/toolbox/toolbox:1.9.0).
web-researcher
MCP server "web-researcher" as configured in zoharbabin/web-researcher-mcp. Launched with web-researcher-mcp. Needs 56 environment variables to run.
web-researcher-mcp
MCP server "web-researcher-mcp" as configured in zoharbabin/web-researcher-mcp. Runs in Docker (ghcr.io/zoharbabin/web-researcher-mcp:1.9.0). Needs 8 environment variables to run.
schemabrain
The trust and intelligence layer between AI agents and your database. Runs locally from the schemabrain Python package. Needs 1 environment variable to run.
oraclemcp
MCP server "oraclemcp" as configured in MuhDur/oraclemcp. Runs in Docker (ghcr.io/muhdur/oraclemcp:0.9.0).
mcp-clickhouse
ClickHouse query & management for AI agents — SQL-classified read/write/destructive gating. Runs locally from the @dockndevai/mcp-clickhouse npm package. Needs 4 environment variables to run.