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/u9401066/rootcause-mcpWrote 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/u9401066/rootcause-mcp/rootcausemcp)<a href="https://agentmods.dev/mcp/u9401066/rootcause-mcp/rootcausemcp"><img src="https://agentmods.dev/badge/mcp/u9401066/rootcause-mcp/rootcausemcp/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/u9401066/rootcause-mcp/rootcausemcp"><img src="https://agentmods.dev/badge/mcp/u9401066/rootcause-mcp/rootcausemcp.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
rootcauseMcp 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
{
"rootcauseMcp": {
"type": "local",
"command": "uv",
"args": [
"run",
"--locked",
"rootcause-mcp"
],
"cwd": ".",
"env": {
"ROOTCAUSE_TOOL_PROFILE": "all",
"ROOTCAUSE_RESPONSE_MODE": "compact"
},
"tools": [
"*"
]
}
}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 · 19 lines scan A b1b2624649b1
rootcauseMcp is an MCP server published in the GitHub repository u9401066/rootcause-mcp (0 stars, last pushed 1mo ago), 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-08-31.
Other mcp servers, from other repositories
zulipchat
Model Context Protocol (MCP) server that connects AI assistants to Zulip Chat with a 20-tool core mode and 60-tool extended mode. Runs locally from the zulipchat-mcp Python package.
microsoft-planner-mcp
MCP server "microsoft-planner-mcp", hosted remotely at localhost, as configured in aixolotl/microsoft-planner-mcp.
openproject-mcp-server
MCP server for OpenProject: 89 tools for work packages, attachments, git activity, time tracking, meetings and reporting over the API v3. Runs locally from the openproject-mcp-server Python package. Needs 5 environment variables to run.
plane-workflow
MCP server "plane-workflow" as configured in amirhosseinkz/plane-workflow-mcp. Runs locally from the plane-workflow Python package.
linear-mcp
Multi-workspace Linear MCP server with PAT auth — drop-in replacement for the official OAuth-only Linear connector. Runs locally from the adelaidasofia-linear-mcp Python package. Needs 1 environment variable to run.
hcmcp
MCP server "hcmcp" as configured in trionnemesis/healthcare-opendata-mcp. Runs locally from the hcmcp Python package.