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/reowens/qsys-toolsWrote 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/reowens/qsys-tools/qsys-mcp-qsys-mcp)<a href="https://agentmods.dev/mcp/reowens/qsys-tools/qsys-mcp-qsys-mcp"><img src="https://agentmods.dev/badge/mcp/reowens/qsys-tools/qsys-mcp-qsys-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/reowens/qsys-tools/qsys-mcp-qsys-mcp"><img src="https://agentmods.dev/badge/mcp/reowens/qsys-tools/qsys-mcp-qsys-mcp.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
qsys-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 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
{
"qsys-mcp": {
"command": "npx",
"args": [
"-y",
"qsys-mcp"
],
"env": {}
}
}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 · 10 lines scan A f0311fb354a6
qsys-mcp is an MCP server published in the GitHub repository reowens/qsys-tools (3 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
elements
NVIDIA Elements UI design system and agent tools for AI/ML, robotics, and autonomous vehicles. Runs locally from the @nvidia-elements/cli npm package.
smartest-tv
Talk to your TV. Play Netflix, Disney+, and 20+ streaming platforms by name on any smart TV. Runs locally from the stv Python package. Needs 3 environment variables to run.
cli
PushToDisplay MCP server — send real-time updates to display boards on iOS and Android devices. Runs locally from the pushtodisplay npm package.
inferbench
Vendor-neutral local-LLM-inference benchmark and hardware-config advisor for omlx and llama.cpp -- measures real tokens/second on your own hardware, live. Runs locally from the inferbench-cli Python package.
tplinkcli
MCP server "tplinkcli" as configured in axo4xo/tplinkcli. Runs locally from the tplinkcli Python package.
unifi
MCP server and CLI for UniFi Network controllers: clients, devices, WLANs, firewall, and health over stdio or streamable HTTP, with auth. Runs locally from the @dinglebear/runifi npm package. Needs 12 environment variables to run.