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.
npx agentmods add mcp/netdefense-io/ndcli/netdefense-mcpgit clone --depth 1 https://github.com/netdefense-io/NDCLIWrote 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/netdefense-io/ndcli/netdefense-mcp)<a href="https://agentmods.dev/mcp/netdefense-io/ndcli/netdefense-mcp"><img src="https://agentmods.dev/badge/mcp/netdefense-io/ndcli/netdefense-mcp.svg" alt="Measured on agentmods" height="20"></a>Grade A, and why
netdefense-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 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
{
"netdefense-mcp": {
"command": "https://github.com/netdefense-io/ndcli-releases/releases/download/v1.27.0/netdefense-mcp_1.27.0.mcpb",
"args": [],
"env": {
"NDCLI_TOKEN": ""
}
}
}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 · 9 lines scan A 3dc11be2891e
netdefense-mcp is an MCP server published in the GitHub repository netdefense-io/NDCLI (0 stars, last pushed 12d ago), licensed Apache-2.0. 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
sophos-firewall-mcp-server
MCP server "sophos-firewall-mcp-server" as configured in jelmervdm/sophos-firewall-mcp. Runs locally from the sophos-firewall-mcp-server Python package.
ai-agent-firewall
Every agent action watched, every money-moving one gated, every verdict independently verifiable. Runs locally from the @fidacy/mcp npm package. Needs 3 environment variables to run.
fidacy
You're the one in charge of your AI agent. But it doesn't know your limits. Authorize, deny, release and record on every consequential action, as an MCP server. Non-custodial. Runs locally from the @fidacy/mcp npm package.
fleet-mcp
Model Context Protocol tool for Fleet DM integration. Runs locally from the fleet-mcp Python package. Needs 5 environment variables to run.
strata
MCP server for progressive tool usage at any scale (see https://klavis.ai). Remote server at strata.klavis.ai.
pare-test
Pare Test ג€” Auto-detects test framework (pytest, jest, vitest, mocha), returns typed JSON. Runs locally from the @paretools/test npm package.