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/zebbern/zebbern-kali-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/zebbern/zebbern-kali-mcp/kali-tools)<a href="https://agentmods.dev/mcp/zebbern/zebbern-kali-mcp/kali-tools"><img src="https://agentmods.dev/badge/mcp/zebbern/zebbern-kali-mcp/kali-tools/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/zebbern/zebbern-kali-mcp/kali-tools"><img src="https://agentmods.dev/badge/mcp/zebbern/zebbern-kali-mcp/kali-tools.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- Socket warn
Grade A, and why
kali-tools 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 3d 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
{
"kali-tools": {
"command": "uvx",
"args": [
"zebbern-kali-mcp"
],
"env": {
"KALI_API_URL": "http://127.0.0.1:5000"
}
}
}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.
- 3d ago First seen · 11 lines scan A 717d4da99f62
kali-tools is an MCP server published in the GitHub repository zebbern/zebbern-kali-mcp (46 stars, last pushed 4d 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-09-06.
Other mcp servers, from other repositories
kali
MCP server "kali" as configured in Unaacceptable297/kali-mcp. Runs dist/index.js with node.
pipefy
MCP server that exposes Pipefy's GraphQL API. Runs locally from the pipefy-mcp-server Python package.
mcp
Web search, AI agent, and content extraction via You.com APIs. Runs locally from the @youdotcom-oss/mcp npm package. Needs 3 environment variables to run.
openmm-mcp
MCP server for OpenMM — exposes market data, account, trading, and strategy tools to AI agents. Runs locally from the @qbtlabs/openmm-mcp npm package.
mcp
Argentine business automation: Mercado Pago, AFIP/ARCA, WhatsApp, banking, shipping (7 packages). Runs locally from the @ar-agents/mcp npm package. Needs 6 environment variables to run.
gridproof
Gridproof your UI — automated spacing & grid QA in the agent loop (MCP server). Runs locally from the gridproof npm package.