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/jmagar/swag-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/jmagar/swag-mcp/swag-mcp-swag-mcp)<a href="https://agentmods.dev/mcp/jmagar/swag-mcp/swag-mcp-swag-mcp"><img src="https://agentmods.dev/badge/mcp/jmagar/swag-mcp/swag-mcp-swag-mcp/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/jmagar/swag-mcp/swag-mcp-swag-mcp"><img src="https://agentmods.dev/badge/mcp/jmagar/swag-mcp/swag-mcp-swag-mcp.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
swag-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 12d 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
{
"swag-mcp": {
"type": "http",
"url": "${user_config.swag_mcp_url}",
"headers": {
"Authorization": "Bearer ${user_config.swag_mcp_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.
- 12d ago First seen · 9 lines scan A 2e2bb0e450e3
swag-mcp is an MCP server published in the GitHub repository jmagar/swag-mcp (5 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
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.
groupme-mcp-server
A FastMCP server that exposes the GroupMe API v3 to MCP clients. Runs locally from the groupme-mcp-server Python package.
claude-context
Model Context Protocol integration for Claude Context. Runs locally from the @zilliz/claude-context-mcp npm package. Needs 7 environment variables to run.
sop-mcp
An MCP server for guiding users through Standard Operating Procedures. Runs locally from the sop-mcp Python package.