Godot MCP

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

MCP Servers JavaScript Grade D Listed MIT
48.9/100
Rank #456 of 1204
Compare Godot MCP

Thin or incomplete trust evidence. Review carefully before production use.

Open compare tool Suggest correction
Listing state
Listed
Evidence coverage
Grade B · 3/5 signals
Last push
2026-04-16 · 115d ago
Recent change
Rank

Is Godot MCP safe? Godot MCP scores 48.9/100 (Grade D), ranked #456 of 1204 tracked open-source AI agent projects, on evidence coverage B (3 of 5 independent signal types). The public evidence: no package-provenance attestation found; OSSF Scorecard rates its supply-chain practices 1.9/10; 45% of recent commits are signed; last pushed 2026-04-16. Every point is earned from checkable signals — never paid placement. How scoring works →

Ranked neighbours in MCP Servers

Quick Trust Read

What Would Improve It
Publish package provenance or release attestations for stronger supply-chain evidence.
Recent Changes
2026-08-08
Rank Moved
Rank dropped 115 spots (#335 → #450)
2026-07-29
Rank Moved
Rank dropped 10 spots (#308 → #318)
2026-07-24
Grade Changed
Trust grade C → D
Maintainer Checklist
Raise Scorecard signals Current OSSF Scorecard is 1.9/10. Tighten the weakest checks to improve public safety evidence.
Publish provenance Add package provenance or release attestations so users can verify where shipped artifacts came from.
Increase signed commits Raise the share of verified-signed commits to make maintainer identity and release history easier to trust.
Refresh maintenance signals The repo was last pushed 115 days ago. Fresh activity helps separate stable projects from stale ones.
43.9
Activity sub-score · out of 100
#151

How to read this: HVTrust (0–100) weighs supply-chain signals (provenance, OSSF Scorecard, signed commits, open license) alongside real-world adoption. Grade D reflects the trust score band: A ≥ 80, B ≥ 65, C ≥ 50, D < 50. Evidence coverage B is separate — it grades how many independent signal types back the score (3 of 5), so a high score on thin evidence stays visible. Full methodology →

Signals refreshed 2026-08-09 19:01 UTC · Repo last pushed 115 days ago

Activity & Reach

Stars
5.1k
Forks
453
Last Push
2026-04-16
115 days ago
Commits (4 wk)
0
Downloads (7d)
2,196
npm
HN mentions (30d)
Open Issues
35
Rank Change
▼6
was #450

Analysis

HVTrust Dimensions vs MCP Servers

48.9 / 100 · 100.0% confidence

Godot MCP MCP Servers average (718 agents)

Safety / Integrity50% OSSF Scorecard · 30% provenance · 20% signed commits
4.6 / 25
in line with avg 5.1
Identity / Provenance60% listing status · 40% build provenance
10.8 / 18
2.5 below avg 13.3
Transparency50% declared license · 50% OSSF Scorecard
10.1 / 17
1.3 above avg 8.8
Maintenance60% last-push freshness · 40% commit activity
4.3 / 20
8.2 below avg 12.5
AdoptionLog-scaled stars · package downloads
13.4 / 20
7.9 above avg 5.5

Activity Inputs

43.9 / 100
StarsRepository reach
22.3 / 30
FreshnessLast push recency
9.0 / 25
ActivityRecent commits
0.0 / 25
CommunityFork signal
12.4 / 20

Supply Chain Trust

Package Provenance
None
No package attestations found
OSSF Scorecard
1.9 / 10
OpenSSF Scorecard · scanned Aug 8, 2026
Signed Commits
45%
of last 100 commits verified
Binary-Artifacts 10
Branch-Protection 0
CI-Tests 0
CII-Best-Practices 0
Code-Review 4
Contributors 0
Dangerous-Workflow -1
Dependency-Update-Tool 0
Fuzzing 0
License 10
Maintained 0
Packaging -1
Pinned-Dependencies -1
SAST 0
Security-Policy 0
Signed-Releases -1
Token-Permissions -1
Vulnerabilities 0

Is Godot MCP safe?

Public trust evidence for Godot MCP is thin: several supply-chain signals are missing or weak. This does not mean the project is unsafe — it means an outside observer cannot easily verify the usual integrity checks. Treat with extra scrutiny.
Does Godot MCP publish package provenance?
No published build provenance is currently detected for Godot MCP. This is common for open-source projects but means consumers cannot independently verify that the package on the registry matches the GitHub source.
Does Godot MCP have an OpenSSF Scorecard?
Godot MCP has an OpenSSF Scorecard score of 1.9/10. The Scorecard checks for branch protection, signed releases, dependency updates, fuzzing, code review, and other supply-chain hygiene items. See the full check breakdown on this page.
Is Godot MCP actively maintained?
Slowing down. Last push was 115 days ago — keep an eye on whether activity resumes.
What license does Godot MCP use?
Godot MCP ships under MIT. A declared, OSI-approved license is one of the transparency signals HVTrust scores.
Are Godot MCP's commits signed?
45% of the last 100 commits to Godot MCP are verified-signed (GPG, SSH, S/MIME, or GitHub's signing flow). Signed commits help confirm that code was authored by who the commit claims.

Not a safety endorsement. HVTracker describes what public signals show, not whether a project is safe for your use case. Run your own security review before adopting in production.

AI agent surface

MCP, providers, tool surface
Scored in HVTrust

These runtime-trust fields — detected from public repo docs and manifests — contribute a bounded adjustment to this project's HVTrust score alongside supply-chain evidence. The exact values each field can add or subtract are documented in the methodology → Compare this surface across every listed agent in the capability matrix →

MCP Server Support
high confidence
Implemented
Godot MCP appears to expose MCP server capabilities.
Detailed evidence is not shown in the public view.
External Service Dependencies
None detected
No clear third-party provider dependency detected.
Credential signal: No explicit API-key/config marker detected.
Tool / Plugin Surface
medium confidence
1 tags
Broad capability areas detected.
  • filesystem
Detailed evidence is not shown in the public view.
Package Provenance Drift
high confidence
Match
Published package metadata matches the tracked repo
Detailed evidence is not shown in the public view.
  • MCP signal live
  • External deps live
  • Tool / plugin surface live
  • Package provenance drift live
How this surface has changed

Detected changes to Godot MCP's runtime surface and supply-chain posture, from daily public-signal snapshots. A change here means our detectors see something different — a genuinely changed capability, or better evidence of an existing one.

2026-07-15
Activity Went Stale
No commits for 90 days

Maintain Godot MCP?

For maintainers

HVTrust scores Godot MCP from public signals only — we never contact maintainers first. If a signal is wrong, stale, or missing (provenance you publish, a Scorecard you run, signed releases), tell us and we'll review it. Corrections are public and tracked on GitHub.

Reputation Timeline

Signal history
Rank 3Grade 2Listed 1HVTrust 1Stale 1Scorecard 1
2026-08-08
Rank Moved
Rank dropped 115 spots (#335 → #450)
2026-07-29
Rank Moved
Rank dropped 10 spots (#308 → #318)
2026-07-24
Grade Changed
Trust grade C → D
2026-07-15
Scorecard Added
OSSF Scorecard: 2.0/10
2026-07-15
Activity Went Stale
No commits for 90 days
2026-07-15
Grade Changed
Trust grade D → C
2026-07-15
Rank Moved
Rank rose 71 spots (#366 → #295)
2026-07-15
HVTrust Changed
HVTrust up 17.8pts (33.0 → 50.8)
2026-07-14
Newly Listed
First tracked at rank #366

Embed Badge Badge guide for maintainers →

For maintainers
HVTrust 48.9 Grade D
Markdown:
[![HVTrust](https://hvtracker.net/badge/godot-mcp.svg)](https://hvtracker.net/agents/godot-mcp)
HTML:
<a href="https://hvtracker.net/agents/godot-mcp"><img src="https://hvtracker.net/badge/godot-mcp.svg" alt="HVTrust"></a>

Other agents in MCP Servers

Data sources
GitHub REST API (repo, commits, stars, forks, license) · npm Registry (downloads, provenance) · OpenSSF Scorecard CLI
Each agent's signals refresh once daily across 6 staggered batches. Methodology v4.2 · Raw JSON