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/qase-tms/qase-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/qase-tms/qase-mcp-server/mcp-server)<a href="https://agentmods.dev/mcp/qase-tms/qase-mcp-server/mcp-server"><img src="https://agentmods.dev/badge/mcp/qase-tms/qase-mcp-server/mcp-server/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/qase-tms/qase-mcp-server/mcp-server"><img src="https://agentmods.dev/badge/mcp/qase-tms/qase-mcp-server/mcp-server.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
mcp-server 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
{
"mcp-server": {
"command": "npx",
"args": [
"-y",
"@qase/mcp-server"
],
"env": {
"QASE_API_TOKEN": "",
"QASE_API_DOMAIN": "api.qase.io",
"QASE_API_PROTOCOL": "https"
}
}
}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 · 14 lines scan A 46cecd6a2acf
mcp-server is an MCP server published in the GitHub repository qase-tms/qase-mcp-server (32 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-30.
Other mcp servers, from other repositories
pare-test
Pare Test ג€” Auto-detects test framework (pytest, jest, vitest, mocha), returns typed JSON. Runs locally from the @paretools/test npm package.
rtblint
Validate OpenRTB bid requests and responses against IAB specs. ARTF, Rust core. Remote server at rtblint.org.
mirrors
AI agent testing: replay real sessions against a rebuilt staging environment to catch regressions. Remote server at api.runmirrors.com.
hookray-mcp
Webhook testing for AI agents. Runs locally from the hookray-mcp npm package.
cold-run
Run every skill in your agent setup twice — once with it, once against an agent that cannot see it — and find out which ones change nothing. Runs locally from the cold-run npm package.
chaosmesh-mcp
MCP server "chaosmesh-mcp" as configured in Ausium/chaosmesh-mcp. Runs locally from the chaosmesh-mcp Python package.