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/node9-ai/node9-proxyWrote 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/node9-ai/node9-proxy/node9)<a href="https://agentmods.dev/mcp/node9-ai/node9-proxy/node9"><img src="https://agentmods.dev/badge/mcp/node9-ai/node9-proxy/node9/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/node9-ai/node9-proxy/node9"><img src="https://agentmods.dev/badge/mcp/node9-ai/node9-proxy/node9.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- Socket pass
Grade A, and why
node9 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 2d 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
{
"node9": {
"command": "npx",
"args": [
"-y",
"node9-ai"
],
"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.
- 2d ago First seen · 10 lines scan A 891f3ccc6d9b
node9 is an MCP server published in the GitHub repository node9-ai/node9-proxy (221 stars, last pushed 2d 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-10-26.
Other mcp servers, from other repositories
mcpsafetywarden
MCP proxy server with behavioral profiling, security scanning, risk gating, and safe execution. Runs locally from the mcpsafetywarden Python package.
agentshield-mcp
Detect prompt injection, jailbreak, and social-engineering attacks in LLM agents. Runs locally from the @eigenart/agentshield-mcp npm package. Needs 1 environment variable to run.
filesystem
Gives the agent read and write access to a set of allowed directories on the local filesystem. Runs locally from the @modelcontextprotocol/server-filesystem npm package.
plantuml
MCP server for generating PlantUML diagrams. Runs locally from the plantuml-mcp-server npm package. Needs 1 environment variable to run.
ethicore-guardian
MCP server "ethicore-guardian" as configured in OraclesTech/guardian-sdk. Runs locally from the ${CLAUDE_PLUGIN_ROOT} Python package. Needs 1 environment variable to run.
zugashield
Comprehensive 7-layer security system for AI agents — prompt injection, tool exploitation, memory poisoning, data exfiltration, and more. Runs locally from the zugashield Python package.