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/simonwittber/agentbridge/unity-examplegit clone --depth 1 https://github.com/simonwittber/AgentBridgeGrade A, and why
unity-example 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 today.
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
{
"unity-example": {
"type": "stdio",
"command": "AgentBridge/Harness~/dffrnt-agent/dffrnt-agent.exe",
"args": [
"--project",
"AgentBridge/Example~",
"serve"
]
}
}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.
- today First seen · 11 lines scan A 56d6eab54e4a
unity-example is an MCP server published in the GitHub repository simonwittber/AgentBridge (0 stars, last pushed 6d 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-01.
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.
summer-engine
Local Summer CLI and MCP server for Summer Engine. Install and run the engine, connect Claude Code, Cursor, Codex, Gemini, and other agents, and build real games with bundled skills, hooks, and plugins. Runs locally from the summer-engine npm package.
vera-ue
MCP server "vera-ue" as configured in ezesubu/VERA. Launched with C:/Users/ezesu/AppData/Local/Programs/Python/Python314/python.exe -m vera.tools.. Needs 1 environment variable to run.
ue-llm-toolkit
MCP server "ue-llm-toolkit" as configured in ColtonWilley/ue-llm-toolkit. Runs Resources/mcp-bridge/index.js with node. Needs 1 environment variable to run.
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.