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/ZylNice/RenderdocMCPInstalling this writes the configuration, not the program: `renderdoc-mcp` has to be on your PATH already, or the server will not start.
Wrote 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/zylnice/renderdocmcp/renderdoc)<a href="https://agentmods.dev/mcp/zylnice/renderdocmcp/renderdoc"><img src="https://agentmods.dev/badge/mcp/zylnice/renderdocmcp/renderdoc/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/zylnice/renderdocmcp/renderdoc"><img src="https://agentmods.dev/badge/mcp/zylnice/renderdocmcp/renderdoc.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
renderdoc 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.
This is a copy
100% identical to renderdoc — 0 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
{
"renderdoc": {
"command": "renderdoc-mcp"
}
}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 · 5 lines scan A 3eb6fb37475e
renderdoc is an MCP server published in the GitHub repository ZylNice/RenderdocMCP (0 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. It is 100% identical to renderdoc, differing in 0 lines, and is treated as a copy.
Other mcp servers, from other repositories
godotlens
Godot's own view of your GDScript project: navigation, diagnostics, engine API, scene checks. Runs locally from the godotlens-mcp npm package. Needs 10 environment variables to run.
dcc-mcp-renderdoc
RenderDoc capture and replay automation skills for DCC-MCP. Runs locally from the dcc-mcp-renderdoc Python package.
fivem-server-doctor-mcp
MCP server "fivem-server-doctor-mcp" as configured in mkcrw/fivem-server-doctor-mcp. Runs locally from the fivem-server-doctor-mcp npm package.
renderdoc-mcp
MCP server for RenderDoc graphics debugger - enables AI-assisted frame capture analysis. Runs locally from the renderdoc-mcp Python package.
c64-debug-mcp
Model Context Protocol server for C64 debugging via VICE emulator. Runs locally from the c64-debug-mcp npm package.
verse-diagnostics-mcp
MCP server for parsing UEFN Verse build diagnostics from UnrealEditorFortnite logs. Runs locally from the verse-diagnostics-mcp Python package.