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/ChistokhinSV/gns3-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/chistokhinsv/gns3-mcp/gns3)<a href="https://agentmods.dev/mcp/chistokhinsv/gns3-mcp/gns3"><img src="https://agentmods.dev/badge/mcp/chistokhinsv/gns3-mcp/gns3/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/chistokhinsv/gns3-mcp/gns3"><img src="https://agentmods.dev/badge/mcp/chistokhinsv/gns3-mcp/gns3.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
gns3 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
{
"gns3": {
"command": "uvx",
"args": [
"[email protected]"
],
"env": {
"GNS3_HOST": "${user_config.gns3_host}",
"GNS3_PORT": "${user_config.gns3_port}",
"GNS3_USER": "${user_config.gns3_user}",
"GNS3_PASSWORD": "${user_config.gns3_password}"
}
}
}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 Changed e903463265aa
- 4d ago First seen · 14 lines scan A 3ee57aa44910
gns3 is an MCP server published in the GitHub repository ChistokhinSV/gns3-mcp (16 stars, last pushed 3d 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-11-03.
gns3 compared with mcp servers from other repositories
| Mod | Type | Stars | Last push | Licence | Scan | Tokens | Works with |
|---|---|---|---|---|---|---|---|
| gns3ChistokhinSV/gns3-mcp | MCP server | 16 | 3d ago | MIT | A | — | Claude Code |
| x-useihuzaifashoukat/x-use | MCP server | 181 | 4d ago | MIT | A | — | Claude Code, Codex, Cursor, Gemini CLI, OpenCode |
| adeudealfluence/adeu | MCP server | 170 | yesterday | MIT | A | — | Gemini CLI |
| pare-testDave-London/Pare | MCP server | 140 | 4d ago | MIT | A | — | Claude Code, Codex, Cursor, Gemini CLI, OpenCode |
| hypermnesia-mcpcdeust/Cortex | MCP server | 76 | yesterday | MIT | A | — | Claude Code |
| seotrendsmcp-ai/Trends-MCP | MCP server | 46 | 4d ago | MIT | A | — | Claude Code, Codex, Cursor, Gemini CLI, OpenCode |
| google-search-console-mcpsurendranb/google-search-console-mcp | MCP server | 40 | 9d ago | MIT | A | — | Claude Code, Cursor |