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/Simone-Tarantino/godot-superpowersWrote 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/simone-tarantino/godot-superpowers/meshy)<a href="https://agentmods.dev/mcp/simone-tarantino/godot-superpowers/meshy"><img src="https://agentmods.dev/badge/mcp/simone-tarantino/godot-superpowers/meshy/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/simone-tarantino/godot-superpowers/meshy"><img src="https://agentmods.dev/badge/mcp/simone-tarantino/godot-superpowers/meshy.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
meshy 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 8d 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 meshy — 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
{
"meshy": {
"command": "npx",
"args": [
"-y",
"@meshy-ai/meshy-mcp-server"
],
"env": {
"MESHY_API_KEY": "${MESHY_API_KEY}"
}
}
}What else .mcp.json configures
This page is one entry in a file that holds 5. Installing the file brings all of them; each is measured and scanned on its own page.
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.
- 8d ago First seen · 12 lines scan A 4789594ae3d1
meshy is an MCP server published in the GitHub repository Simone-Tarantino/godot-superpowers (2 stars, last pushed 4mo 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 meshy, differing in 0 lines, and is treated as a copy.
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.
blender
Blender integration through the Model Context Protocol. Runs locally from the blender-mcp Python package.
beckett
MCP server "beckett", hosted remotely at 127.0.0.1, as configured in beckettlab/beckett-godot-mcp.
godot-mcp-bridge
MCP server for Godot game engine integration — control the Godot editor with AI. Runs locally from the godot-mcp-bridge npm package.
wavedash
Wavedash docs and workflow guidance for building and publishing browser games. Remote server at mcp.wavedash.com.