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/dockndevai/mcp-kafkaWrote 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/dockndevai/mcp-kafka/mcp-kafka)<a href="https://agentmods.dev/mcp/dockndevai/mcp-kafka/mcp-kafka"><img src="https://agentmods.dev/badge/mcp/dockndevai/mcp-kafka/mcp-kafka/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/dockndevai/mcp-kafka/mcp-kafka"><img src="https://agentmods.dev/badge/mcp/dockndevai/mcp-kafka/mcp-kafka.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
mcp-kafka 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 12d 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
{
"mcp-kafka": {
"command": "npx",
"args": [
"-y",
"@dockndevai/mcp-kafka"
],
"env": {
"KAFKA_BROKERS": "",
"KAFKA_MODE": ""
}
}
}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.
- 12d ago First seen · 13 lines scan A 9a140e42104e
mcp-kafka is an MCP server published in the GitHub repository dockndevai/mcp-kafka (1 stars, last pushed yesterday), 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
kafka-sentinel-mcp
Read-only Kafka observability MCP server: cluster health, consumer lag, and replay-readiness for AI agents that must never touch production. Runs locally from the kafka-sentinel-mcp Python package. Needs 6 environment variables to run.
kafka-sentinel
MCP server "kafka-sentinel" as configured in sanjay-amu/kafka-sentinel-mcp. Launched with kafka-sentinel-mcp. Needs 1 environment variable to run.
devcontext
MCP server "devcontext" as configured in sid-stack001/devcontext. Runs f:\project\devcontext\server.py with python.
kafka
MCP server "kafka" as configured in aswinayyolath/kafka-mcp-server. Runs /home/oem/Documents/kafka-mcp-server/kafka_mcp_server.py with python. Needs 2 environment variables to run.
mcptoon
MCP server "mcptoon" as configured in activeing123/mcptoon. Launched with mcptoon serve.
prometheus-mcp-server
MCP server "prometheus-mcp-server" as configured in pab1it0/prometheus-mcp-server. Runs in Docker (ghcr.io/pab1it0/prometheus-mcp-server:1.6.2). Needs 14 environment variables to run.