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/yearningss/gamemaker-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/yearningss/gamemaker-mcp/gamemaker)<a href="https://agentmods.dev/mcp/yearningss/gamemaker-mcp/gamemaker"><img src="https://agentmods.dev/badge/mcp/yearningss/gamemaker-mcp/gamemaker/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/yearningss/gamemaker-mcp/gamemaker"><img src="https://agentmods.dev/badge/mcp/yearningss/gamemaker-mcp/gamemaker.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
gamemaker 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 2d 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
{
"gamemaker": {
"type": "stdio",
"command": "C:\\Program Files\\nodejs\\node.exe",
"args": [
"C:\\Users\\Micr\\GameMakerMCP\\dist\\src\\index.js"
],
"env": {
"GAMEMAKER_MCP_MODE": "workspace-write",
"GAMEMAKER_MCP_ALLOW_BUILD": "1"
}
}
}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.
- 2d ago First seen · 13 lines scan A f0393eb91fb9
gamemaker is an MCP server published in the GitHub repository yearningss/gamemaker-mcp (15 stars, last pushed 3d 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-09-10.
Other mcp servers, from other repositories
context7
Gives the agent up-to-date documentation and code examples for libraries and frameworks, fetched on demand so answers are not stuck at the model's training cutoff. Runs locally from the @upstash/context7-mcp npm package.
agents-docs
Ultra-fast, zero-bloat local markdown documentation RAG for AI coding agents via MCP. Runs locally from the agents-docs Python package.
mcp
Build, version, review, and export websites, web apps, and games from a conversation. Remote server at 2ools.app.
funplay-unreal-mcp
stdio bridge for the local Unreal Editor MCP server from FunplayAI/funplay-unreal-mcp. Runs locally from the funplay-unreal-mcp npm package. Needs 4 environment variables to run.
docs-langchain
MCP server "docs-langchain", hosted remotely at docs.langchain.com, as configured in langchain-ai/langchain.
component-explorer
MCP server "component-explorer" as configured in microsoft/vscode. Launched with npm exec --no -- component-explorer mcp -p ./test/componentFixtures/component-ex.