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.
npx agentmods add mcp/laxy9887/game-dev.-spritesheet-forge/spritesheet-forgegit clone --depth 1 https://github.com/LAXY9887/Game-Dev.-Spritesheet-ForgeWrote 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/laxy9887/game-dev.-spritesheet-forge/spritesheet-forge)<a href="https://agentmods.dev/mcp/laxy9887/game-dev.-spritesheet-forge/spritesheet-forge"><img src="https://agentmods.dev/badge/mcp/laxy9887/game-dev.-spritesheet-forge/spritesheet-forge.svg" alt="Measured on agentmods" height="20"></a>Grade A, and why
spritesheet-forge 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 3d 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
{
"spritesheet-forge": {
"url": "https://mcp.clawstudiouo.com/mcp",
"type": "streamable-http"
}
}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.
- 3d ago First seen · 6 lines scan A c0eb2b38781a
spritesheet-forge is an MCP server published in the GitHub repository LAXY9887/Game-Dev.-Spritesheet-Forge (0 stars, last pushed 2mo 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
aseprite-live-mcp
Unity-first MCP server for the live Aseprite editor (and headless batch). Runs locally from the aseprite-live-mcp Python package. Needs 4 environment variables to run.
picoberry-mcp
An AI 3D workspace for games, VR, and beyond. Generate, remesh, texture, and animate 3D assets. Runs locally from the @picoberry/mcp-server 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.
blender
Blender integration through the Model Context Protocol. Runs locally from the blender-mcp Python package.
generate
Generate game sprites and assets from text prompts for game development. Remote server at api.spritecook.ai.
unity-hub-mcp
MCP server "unity-hub-mcp" as configured in MauricePutinas/Unity-MCP-Claude-Code. Runs locally from the unity-hub-mcp Python package.