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/GimbalGoats/GG_MayaMCPWrote 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/gimbalgoats/gg_mayamcp/maya-mcp)<a href="https://agentmods.dev/mcp/gimbalgoats/gg_mayamcp/maya-mcp"><img src="https://agentmods.dev/badge/mcp/gimbalgoats/gg_mayamcp/maya-mcp/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/gimbalgoats/gg_mayamcp/maya-mcp"><img src="https://agentmods.dev/badge/mcp/gimbalgoats/gg_mayamcp/maya-mcp.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
maya-mcp 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 11d 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
{
"maya-mcp": {
"command": "uvx",
"args": [
"maya-mcp"
],
"env": {}
}
}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.
- 11d ago First seen · 9 lines scan A 28f262cb52b8
maya-mcp is an MCP server published in the GitHub repository GimbalGoats/GG_MayaMCP (19 stars, last pushed 27d 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
3D-AI-Agent-Avatar
3D AI Agent Avatar — render any GLB, give it a Solana wallet, a voice, and pump.fun powers. Runs locally from the @three-ws/avatar-agent npm package. Needs 11 environment variables to run.
audio-mcp
Text-to-speech, speech-to-text, audio-to-face lipsync, and motion-capture clips for 3D agents. Runs locally from the @three-ws/audio-mcp npm package. Needs 3 environment variables to run.
3d-agent-mcp
MCP tools from three.ws: free + paid text-to-3D, rigging, agent reputation, market intel. Runs locally from the @three-ws/mcp-server npm package. Needs 3 environment variables to run.
scene-mcp
Compose a placed 3D diorama from one sentence, export a forged world, browse saved scenes. Runs locally from the @three-ws/scene-mcp npm package. Needs 2 environment variables to run.
meshy
MCP server for Meshy AI 3D generation platform. Runs locally from the @meshy-ai/meshy-mcp-server npm package. Needs 1 environment variable to run.
3d-agent
MCP server "3d-agent", hosted remotely at three.ws, as configured in nirholas/three.ws.