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/virtualsms-io/mcp-serverWrote 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/virtualsms-io/mcp-server/sms)<a href="https://agentmods.dev/mcp/virtualsms-io/mcp-server/sms"><img src="https://agentmods.dev/badge/mcp/virtualsms-io/mcp-server/sms/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/virtualsms-io/mcp-server/sms"><img src="https://agentmods.dev/badge/mcp/virtualsms-io/mcp-server/sms.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
sms 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
{
"sms": {
"command": "npx",
"args": [
"-y",
"virtualsms-mcp"
],
"env": {
"VIRTUALSMS_API_KEY": ""
}
}
}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 · 12 lines scan A 126babd72b1f
sms is an MCP server published in the GitHub repository virtualsms-io/mcp-server (8 stars, last pushed 1mo 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
connectmachine
Manage your ConnectMachine contacts, networks, events, and digital business cards. Remote server at mcp.connectmachine.ai.
sherweb-mcp
MCP server "sherweb-mcp" as configured in Servosity/msp-skills. Launched with https://github.com/Servosity/msp-skills/releases/download/sherweb-v0.1.4/sherweb. Needs 7 environment variables to run.
skykick-mcp
MCP server "skykick-mcp" as configured in Servosity/msp-skills. Launched with https://github.com/Servosity/msp-skills/releases/download/skykick-v0.1.4/skykick. Needs 6 environment variables to run.
appdirect-mcp
MCP server "appdirect-mcp" as configured in Servosity/msp-skills. Launched with https://github.com/Servosity/msp-skills/releases/download/appdirect-v0.1.5/appdi. Needs 6 environment variables to run.
connectwise-manage-mcp
MCP server "connectwise-manage-mcp" as configured in Servosity/msp-skills. Launched with https://github.com/Servosity/msp-skills/releases/download/connectwise-manage-v0.. Needs 7 environment variables to run.
crowdstrike-mcp
MCP server "crowdstrike-mcp" as configured in Servosity/msp-skills. Launched with https://github.com/Servosity/msp-skills/releases/download/crowdstrike-v0.1.5/cro. Needs 6 environment variables to run.