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/tumourlove/DEPRECATED-unreal-editor-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/tumourlove/deprecated-unreal-editor-mcp/unreal-editor-mcp)<a href="https://agentmods.dev/mcp/tumourlove/deprecated-unreal-editor-mcp/unreal-editor-mcp"><img src="https://agentmods.dev/badge/mcp/tumourlove/deprecated-unreal-editor-mcp/unreal-editor-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/tumourlove/deprecated-unreal-editor-mcp/unreal-editor-mcp"><img src="https://agentmods.dev/badge/mcp/tumourlove/deprecated-unreal-editor-mcp/unreal-editor-mcp.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
unreal-editor-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 12d 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
{ "unreal-editor-mcp": { "command": "uvx", "args": [ "unreal-editor-mcp" ] } }
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.
- 12d ago First seen · 8 lines scan A 8b87936b5682
unreal-editor-mcp is an MCP server published in the GitHub repository tumourlove/DEPRECATED-unreal-editor-mcp (0 stars, last pushed 6mo 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
unreal-mcp-ue4
UE4.27 MCP server for controlling Unreal Editor sessions over Python Remote Execution. Runs locally from the unreal-mcp-ue4 npm package.
txadmin-mcp
MCP server for FiveM/RedM server administration through txAdmin. Runs locally from the txadmin-mcp npm package.
unreal-project-mcp
MCP server "unreal-project-mcp" as configured in tumourlove/DEPRECATED-unreal-project-mcp. Runs locally from the unreal-project-mcp Python package.
unreal-source-mcp
MCP server "unreal-source-mcp" as configured in tumourlove/DEPRECATED-unreal-source-mcp. Runs locally from the unreal-source-mcp Python package.
unreal-animation-mcp
MCP server "unreal-animation-mcp" as configured in tumourlove/DEPRECATED-unreal-animation-mcp. Runs locally from the unreal-animation-mcp Python package.
ninjaone-mcp
MCP server "ninjaone-mcp" as configured in WYRE-AI/ninjaone-mcp. Runs in Docker (ghcr.io/wyre-ai/ninjaone-mcp:v2.3.0). Needs 6 environment variables to run.