npm analyzed 0.1.1

coding-solo/godot-mcp

v0.1.1
npm

MCP server for interfacing with Godot game engine. Provides tools for launching the editor, running projects, and capturing debug output.

maintainer
coding-solo
license
MIT
first seen
2026-05-22
last seen
2026-06-23
releases · 30d
0
short id
risk 40/100 · heuristic grade
C elevated
  • vulnerabilitiesattested+9
  • capability exposureinferred+16
  • inherited (deps)attested+15

attestedinferred

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 10m ago · see ecosystem CVEs →

capability exposure grade factor +16
Inferred surface — each links to servers holding it:
vulnerabilities 1 CVEs · grade factor +9
HIGH
godot-mcp has Command Injection via unsanitized projectPath EPSS 0% CVE-2026-25546 CVSS 7.8 affects [{"type":"SEMVER","events":[{"introduced":"0"},{"fixed":"0.1.1"}]}]fixed in 0.1.1GHSANVDGHSAGHSA

inherited (deps) · grade factor +15

inherited via dependencies 3
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 safety all quiet

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

embed badge readme-ready
live risk-grade badge preview [![MCP Observatory risk grade](https://mcpobservatory.com/servers/mcpso:Coding-Solo/godot-mcp/badge.svg)](https://mcpobservatory.com/servers/mcpso:Coding-Solo/godot-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 coding-solo.