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/mikimatsub/swsd-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/mikimatsub/swsd-mcp/swsd)<a href="https://agentmods.dev/mcp/mikimatsub/swsd-mcp/swsd"><img src="https://agentmods.dev/badge/mcp/mikimatsub/swsd-mcp/swsd/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/mikimatsub/swsd-mcp/swsd"><img src="https://agentmods.dev/badge/mcp/mikimatsub/swsd-mcp/swsd.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
swsd 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
{
"swsd": {
"command": "npx",
"args": [
"-y",
"swsd-mcp"
],
"env": {
"SWSD_TOKEN": "",
"SWSD_BASE_URL": "https://api.samanage.com",
"SWSD_PROFILE": "agent",
"SWSD_WRITE_MODE": "live",
"SWSD_ATTACHMENT_ROOT": ""
}
}
}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 · 16 lines scan A b76160e36f1d
swsd is an MCP server published in the GitHub repository mikimatsub/swsd-mcp (3 stars, last pushed today), 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
invgate-service-desk-mcp
InvGate Service Desk MCP — 96 tools across 11 domains (incidents, users, knowledge base, assets, time tracking), read-only by default with a 3-tier write access model (none/support/full), and built-in OpenTelemetry observability. Runs locally from the invgate-service-desk-mcp Python package. Needs 3 environment…
teamdynamix-mcp-server
MCP server "teamdynamix-mcp-server" as configured in chatt-state/teamdynamix-mcp-server. Runs locally from the @chatt-state/teamdynamix-mcp-server npm package.
smartsuite
MCP server "smartsuite" as configured in SmartSuiteFoundry/smartsuite-mcp-server. Launched with smartsuite-mcp. Needs 4 environment variables to run.
astravue-mcp
Manage projects, tasks, time tracking, and team collaboration through natural language. Remote server at api.astravue.com.
servicenow-mcp-ai
ServiceNow MCP server — 67 tools over the full REST surface, every auth method, flows, diagrams. Runs locally from the servicenow-mcp-ai npm package. Needs 6 environment variables to run.
nowaikit
ServiceNow MCP server: 450+ tools for Claude, ChatGPT, Copilot & any AI. Read-only by default. Runs locally from the nowaikit npm package. Needs 14 environment variables to run.