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/Olaw2jr/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/olaw2jr/gns3-mcp/gns3)<a href="https://agentmods.dev/mcp/olaw2jr/gns3-mcp/gns3"><img src="https://agentmods.dev/badge/mcp/olaw2jr/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/olaw2jr/gns3-mcp/gns3"><img src="https://agentmods.dev/badge/mcp/olaw2jr/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 9d 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": "gns3-mcp",
"args": [],
"env": {
"GNS3_BASE_URL": "${GNS3_BASE_URL}",
"GNS3_USERNAME": "${GNS3_USERNAME}",
"GNS3_PASSWORD": "${GNS3_PASSWORD}",
"GNS3_TOKEN": "${GNS3_TOKEN}",
"GNS3_READ_ONLY": "${GNS3_READ_ONLY}",
"GNS3_DEFAULT_PROJECT": "${GNS3_DEFAULT_PROJECT}"
}
}
}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.
- 9d ago First seen · 14 lines scan A 16850038fbe3
gns3 is an MCP server published in the GitHub repository Olaw2jr/gns3-mcp (0 stars, last pushed 5d 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-08-31.
Other mcp servers, from other repositories
local-reddit-research-mcp
MCP server "local-reddit-research-mcp", hosted remotely at localhost, as configured in dialog-tools/reddit-research-mcp.
reddit-research-mcp
MCP server "reddit-research-mcp" as configured in dialog-tools/reddit-research-mcp.
unraid
Rust MCP server and CLI for Unraid GraphQL operations across NAS, Docker, VM, and storage workflows. Runs locally from the @dinglebear/unraid npm package. Needs 6 environment variables to run.
unraid-mcp
MCP Server for Unraid API - provides tools to interact with an Unraid server's GraphQL API. Runs locally from the unraid-mcp Python package. Needs 3 environment variables to run.
unraid-mcp
MCP Server for Unraid API - provides tools to interact with an Unraid server's GraphQL API. Runs locally from the unraid-mcp Python package. Needs 2 environment variables to run.
unifi
MCP server "unifi" as configured in pete-builds/mcp-unifi. Runs in Docker (ghcr.io/pete-builds/mcp-unifi:0.5.1). Needs 9 environment variables to run.