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/DmitriyGolub/threejs-devtools-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/dmitriygolub/threejs-devtools-mcp/threejs-devtools)<a href="https://agentmods.dev/mcp/dmitriygolub/threejs-devtools-mcp/threejs-devtools"><img src="https://agentmods.dev/badge/mcp/dmitriygolub/threejs-devtools-mcp/threejs-devtools/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/dmitriygolub/threejs-devtools-mcp/threejs-devtools"><img src="https://agentmods.dev/badge/mcp/dmitriygolub/threejs-devtools-mcp/threejs-devtools.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- Socket warn
Grade A, and why
threejs-devtools 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
{
"threejs-devtools": {
"command": "npx",
"args": [
"-y",
"threejs-devtools-mcp"
],
"env": {
"DEV_PORT": "",
"BRIDGE_PORT": "",
"BROWSER": "",
"HEADLESS": "",
"CHROME_PATH": ""
}
}
}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 · 16 lines scan A c89dee8e7fa6
threejs-devtools is an MCP server published in the GitHub repository DmitriyGolub/threejs-devtools-mcp (121 stars, last pushed 4d 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-30.
Other mcp servers, from other repositories
uisight
Your AI sees the screen but can't measure it — measured web UI findings, shared live sessions. Runs locally from the uisight npm package. Needs 3 environment variables to run.
mcp
MCP server for WCAG accessibility and color-contrast audits plus QA issue tracking in Claude Code, Cursor, and Windsurf. Runs locally from the @overlayqa/mcp npm package.
savee
MCP server "savee", hosted remotely at mcp.savee.com, as configured in saveeit/savee-mcp-server.
uiverse-mcp
MCP server "uiverse-mcp" as configured in Fabi-SPL/uiverse-mcp. Runs locally from the uiverse-mcp npm package.
imugi-ai
Design to Code — AI-powered frontend builder with visual verification. Runs locally from the imugi-ai npm package.
conductor-figma
Design-intelligent MCP server for Figma. 201 design-intelligent tools for Figma. Every tool knows typography, spacing, color, accessibility. Not a shape proxy — a design engine. Runs locally from the conductor-figma npm package.