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/plugins/olaw2jr/gns3-mcp/plugin)<a href="https://agentmods.dev/plugins/olaw2jr/gns3-mcp/plugin"><img src="https://agentmods.dev/badge/plugins/olaw2jr/gns3-mcp/plugin/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/plugins/olaw2jr/gns3-mcp/plugin"><img src="https://agentmods.dev/badge/plugins/olaw2jr/gns3-mcp/plugin.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 1mo 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
{
"name": "gns3",
"version": "0.1.0",
"description": "Drive a GNS3 v3 network-emulation controller from Claude: build topologies, manage device lifecycle, snapshot, capture packets, manage templates/computes/RBAC, and automate device CLIs over node consoles.",
"author": { "name": "Oscar" },
"keywords": ["gns3", "networking", "mcp", "automation", "labs"],
"mcpServers": "./.mcp.json",
"commands": "./commands"
}
What it installs
The manifest is a name and a version. 1 command, 1 MCP server travel with it, and installing the plugin installs all of them — 16 tokens a session between them. Each is measured on its own page, and each can be installed alone.
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.
- 1mo ago First seen · 10 lines scan A c2f1d36218f2
gns3 is a plugin published in the GitHub repository Olaw2jr/gns3-mcp (1 stars, last pushed 1mo ago), licensed MIT. Its token cost is not measured: this kind of file is read by the harness, not the model. 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 plugins, from other repositories
unraid-mcp
Query, monitor, and manage Unraid servers via GraphQL API through MCP tools. Supports system info, Docker, VMs, array/parity, notifications, plugins, rclone, and live telemetry.
archhub-marketplace
Plugin marketplace listing 1 plugin: archhub.
servicenow
ServiceNow MCP server for Claude Code, GitHub Copilot, Codex and any MCP client: Table API, CMDB, schema, aggregates and update sets, plus four Agent Skills. Read-only mode, OAuth client credentials for headless use, audit log.
servicenow-change-impact
Example skills for mcp-server-servicenow: change impact and SLA definition review (read-only, itil).
servicenow-incident-triage
Example skill for mcp-server-servicenow: incident triage and trend reports (ITSM, itil).
my-servicenow-skills
My skills for mcp-server-servicenow.