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/woohq/godette-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/woohq/godette-mcp/godette)<a href="https://agentmods.dev/mcp/woohq/godette-mcp/godette"><img src="https://agentmods.dev/badge/mcp/woohq/godette-mcp/godette/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/woohq/godette-mcp/godette"><img src="https://agentmods.dev/badge/mcp/woohq/godette-mcp/godette.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
godette 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 10d 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
{ "godette": { "command": "npx", "args": [ "-y", "godette" ] } }
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.
- 10d ago First seen · 9 lines scan A 2e39ce76d130
godette is an MCP server published in the GitHub repository woohq/godette-mcp (0 stars, last pushed 5mo 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-31.
Other mcp servers, from other repositories
godot-mcp
Agent-driven Godot playtesting: editor control, input injection, game-time stepping, live state. Runs locally from the @satelliteoflove/godot-mcp npm package. Needs 2 environment variables to run.
godot-mcp
MCP server for full Godot 4.x engine control with 165 tools for AI-driven game development. Runs locally from the @tugcantopaloglu/godot-mcp npm package.
godot-docs-mcp
MCP server "godot-docs-mcp" as configured in mcintalmo/godot-docs-mcp. Runs locally from the godot-docs-mcp Python package.
godot
The most complete Godot 4 MCP: secure sandbox, 40+ tools (projects–runtime), major MCP clients. Runs locally from the godot-mcp-server Python package.
unity-editor
MCP for Unity Server: A Unity package for Unity Editor integration via the Model Context Protocol (MCP). Runs locally from the mcpforunityserver Python package.
fal-media
Model Context Protocol (MCP) server for fal.ai - interact with AI models through Claude and other MCP clients. Now with Platform API v1 support! Runs locally from the fal-ai-mcp-server npm package. Needs 1 environment variable to run.