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.
npx agentmods add mcp/sota-deploy/mcp-server/sotagit clone --depth 1 https://github.com/sota-deploy/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/sota-deploy/mcp-server/sota)<a href="https://agentmods.dev/mcp/sota-deploy/mcp-server/sota"><img src="https://agentmods.dev/badge/mcp/sota-deploy/mcp-server/sota.svg" alt="Measured on agentmods" height="20"></a>Grade A, and why
sota 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 3d 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.
This is a copy
89% identical to mcp — 2 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
What it actually says
{
"sota": {
"command": "npx",
"args": [
"-y",
"@sota-io/mcp"
],
"env": {}
}
}What else server.json configures
This page is one entry in a file that holds 2. Installing the file brings all of them; each is measured and scanned on its own page.
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.
- 3d ago First seen · 10 lines scan A cff82cb87574
sota is an MCP server published in the GitHub repository sota-deploy/mcp-server (0 stars, last pushed 3mo 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. It is 89% identical to mcp, differing in 2 lines, and is treated as a copy.
Other mcp servers, from other repositories
ssh-licco
SSH Model Context Protocol Server - Enable SSH functionality for AI models. Runs locally from the ssh-licco Python package. Needs 4 environment variables to run.
cloudflare-docs
MCP server "cloudflare-docs", hosted remotely at docs.mcp.cloudflare.com, as configured in ourobx/agent-ebpf.
tailscale-compute
Run builds, tests, and benchmarks on your own Tailscale compute node. Runs locally from the @dylantirandaz/tailscale-compute-mcp npm package. Needs 6 environment variables to run.
vmware-privateai
VMware Private AI Foundation with NVIDIA ops — GPU inventory, vGPU/DirectPath profiles, utilization, model-serving (MCP + CLI). Runs locally from the vmware-privateai Python package.
project-bourne
Run reproducible scientific workloads on GPUs, local compute, Slurm, and PBS with provenance. Runs locally from the @project-bourne/mcp npm package.
playwright
MCP server "playwright" as configured in jtylek/EpesiCRM. Runs C:\Users\jasiek\AppData\Roaming\npm\node_modules\@playwright\mcp\cli.js with node.