MCP Observatory
npm analyzed 1.0.79

ue-mcp

v1.0.79
npm

Unreal Engine MCP server - 21 tools, 569+ actions for AI-driven editor control

maintainer
db-lyon
license
BUSL-1.1
first seen
2026-06-01
last seen
2026-06-14
releases · 30d
145
short id
risk41/100 · heuristic grade
C elevated
  • capability exposureinferred+35
  • inherited (deps)attested+15
  • trust mitigatorsmixed−9

attestedinferredmixed

The A–E grade is our heuristic synthesis — a "review this" prompt, not a verdict. Each factor is tagged by what backs it: attested (a verifiable record), reported (a third party's claim), or inferred (our own heuristic, e.g. permissions). See methodology.

graded 7m ago · see ecosystem CVEs →

capability exposuregrade factor +35
Inferred surface — each links to servers holding it:
vulnerabilities0 CVEs

no known CVEs for this server.

inherited (deps) · grade factor +15

inherited via dependencies3
HIGH
@modelcontextprotocol/sdk has cross-client data leak via shared server/transport instance reuse via @modelcontextprotocol/sdk · 1 hop CVE-2026-25536 fixed in 1.26.0
HIGH
Anthropic's MCP TypeScript SDK has a ReDoS vulnerability via @modelcontextprotocol/sdk · 1 hop CVE-2026-0621 fixed in 1.25.2
HIGH
Model Context Protocol (MCP) TypeScript SDK does not enable DNS rebinding protection by default via @modelcontextprotocol/sdk · 1 hop CVE-2025-66414 fixed in 1.24.0
tool safetyall quiet

No tool-safety findings — heuristic detectors run on the compute-risk cadence; a finding appears when a tool trips a rule.

skills & danger signalsnpm-tarball
prompt-surface shipped agent-instruction files + hidden-content / dangerous-code findings — quoted from the analyzed source

analyzed v1.0.79 · analyzer v17 · 1d ago

skills & prompt files 4

embed badgereadme-ready
live risk-grade badge preview [![MCP Observatory risk grade](https://mcpobservatory.com/servers/github:db-lyon/ue-mcp/badge.svg)](https://mcpobservatory.com/servers/github:db-lyon/ue-mcp/security)

Heuristic, inferred signals — false positives (legitimately powerful tools, forks, language ports) are expected. Treat each as "review this", not a verdict. See the ecosystem-wide picture on the security hub, or the fleet security of db-lyon.