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/vulnmaster/CASE-UCO-SDKWrote 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/vulnmaster/case-uco-sdk/case-uco)<a href="https://agentmods.dev/mcp/vulnmaster/case-uco-sdk/case-uco"><img src="https://agentmods.dev/badge/mcp/vulnmaster/case-uco-sdk/case-uco/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/vulnmaster/case-uco-sdk/case-uco"><img src="https://agentmods.dev/badge/mcp/vulnmaster/case-uco-sdk/case-uco.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
case-uco 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 today.
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
{
"case-uco": {
"url": "http://127.0.0.1:8765/sse"
}
}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.
- today First seen · 5 lines scan A 9fec145a3a15
case-uco is an MCP server published in the GitHub repository vulnmaster/CASE-UCO-SDK (9 stars, last pushed today), licensed Apache-2.0. 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-09-09.
Other mcp servers, from other repositories
findevil-mcp
MCP server "findevil-mcp" as configured in TimothyVang/verdict-dfir. Launched with bash scripts/run-mcp-rust.sh.
findevil-agent-mcp
MCP server "findevil-agent-mcp" as configured in TimothyVang/verdict-dfir. Launched with bash scripts/run-mcp-python.sh.
n8n-mcp
MCP server "n8n-mcp" as configured in TimothyVang/verdict-dfir. Launched with bash scripts/run-mcp-n8n.sh.
playwright
MCP server "playwright" as configured in TimothyVang/verdict-dfir. Launched with bash scripts/run-mcp-playwright.sh.
puppeteer
MCP server "puppeteer" as configured in TimothyVang/verdict-dfir. Launched with bash scripts/run-mcp-puppeteer.sh.
qmd
MCP server "qmd" as configured in TimothyVang/verdict-dfir. Launched with bash scripts/run-mcp-qmd.sh.