updated 2026-10-13 04:10 UTC

Godot MCP

Repository

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

MCP Servers JavaScript Listed MIT

Is Godot MCP safe? Thin or incomplete trust evidence. Review carefully before production use.

OSSF Scorecard 1.9 / 10
Provenance None
Signed commits 45%
Last push 180d ago
Advisories None known
Compare Godot MCP

How does it stack up against its MCP Servers neighbours?

Pick any agent to compare →
Suggest a correction

In detail: Godot MCP scores 45.7/100 (Grade D), ranked #1094 of 1371 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; no published advisory affects its latest release (@coding-solo/godot-mcp); last pushed 2026-04-16. Every point is earned from checkable signals — never paid placement. How scoring works →

How Godot MCP could raise its score

Each line changes one public signal and recomputes with the live scoring function. The gains don't add up exactly, because the score is capped near the top.

Already done? Suggest a correctionAdd the trust badge

Chain of custody

Scanners check what the code says. This traces who ships Godot MCP and whether that has changed: from the source repository, through how changes are reviewed and released, to the package you install. These are the checks for OWASP ASI04 Agentic Supply Chain Vulnerabilities.

  1. Source Partly signed

    github.com/Coding-Solo/godot-mcp, MIT, last pushed 2026-04-16. 45% of the last 100 commits carry a verified signature; the rest can't be tied to a verified identity.

  2. Review and release Weak

    OpenSSF Scorecard rates the repository's practices 1.9/10 (scanned Oct 6, 2026). The checks that decide who can get a change released:

    • Code Review4
    • Branch Protection0
    • Signed Releasesn/a
    • Dangerous Workflown/a
    • Token Permissionsn/a
    • Pinned Dependenciesn/a
    All 18 Scorecard checks
    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

  3. Published packages Linked, not attested

    Without a build attestation, nothing proves the published files were built from this repository.

  4. What you install today No known advisories

    Latest release checked: @coding-solo/godot-mcp 0.1.1. No published advisory affects it (OSV, checked 2026-10-13).

Changes to this chain

No change to package provenance, package source links, Scorecard coverage or license in HVTracker's daily snapshots of Godot MCP.

Evidence behind this score

Coverage B: 3 of 5 independent evidence types found.

  • GitHub repository data
  • Package downloads
  • Supply-chain checks
  • Public actions (missing)
  • Community mentions (missing)

Verify this score yourself

Every build re-issues Godot MCP’s score as an Ed25519-signed credential, valid for 7 days. You can check it offline against HVTracker’s published key; if anyone changes a number after signing, verification fails.

Signed credential (JSON) How to verify

What this score doesn’t check

It covers who ships the code, not what the code does. It doesn’t read tool descriptions or prompts for injected instructions, watch runtime behaviour, or find bugs nobody has disclosed yet. For that, run a content scanner before you connect it, such as Cisco MCP Scanner or Snyk Agent Scan.

How Godot MCP compares in MCP Servers

  1. #633 KDAN PDF 45.8 +0.1
  2. #634 MCP Apple Music 45.8 +0.1
  3. #635 Godot MCP 45.7 this agent
  4. #636 Pty MCP 45.6 −0.1
  5. #637 Browserbase MCP Server 45.6 −0.1

Bars show each HVTrust score; the tick marks Godot MCP’s 45.7.

Where the 45.7 comes from

HVTrust dimensions vs the MCP Servers average

45.7 / 100 · 100.0% confidence

Godot MCP MCP Servers average (781 agents)

Safety / Integrity50% OSSF Scorecard · 30% provenance · 20% signed commits
4.6 / 25
5.8 below avg 10.4
Identity / Provenance60% listing status · 40% build provenance
10.8 / 18
2.7 below avg 13.5
Transparency50% declared license · 50% OSSF Scorecard
10.1 / 17
2.1 below avg 12.2
Maintenance60% last-push freshness · 40% commit activity
0 / 20
12.2 below avg 12.2
AdoptionLog-scaled stars · package downloads
14.5 / 20
7.1 above avg 7.4

Quick Trust Read

What Would Improve It
Publish package provenance or release attestations for stronger supply-chain evidence.
Recent Changes
2026-10-09
Rank Moved
Rank dropped 14 spots (#1071 → #1085)
2026-09-23
Rank Moved
Rank dropped 617 spots (#411 → #1028)
2026-09-22
Rank Moved
Rank dropped 67 spots (#344 → #411)
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 180 days ago. Fresh activity helps separate stable projects from stale ones.
Compare with another agent Get email alerts for Godot MCP View MCP Servers Report missing data
35.3
Activity sub-score · out of 100
#635
In MCP Servers

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-10-13 04:10 UTC · Repo last pushed 180 days ago

Rank Trend

2026-09-29 2026-10-13

Activity & Reach

Stars
6.0k
Forks
479
Last Push
2026-04-16
180 days ago
Commits (4 wk)
0
Downloads (7d)
11,260
npm
HN mentions (30d)
—
Open Issues
38
Rank Change
▲1
was #1095

Analysis

Activity Inputs

35.3 / 100
StarsRepository reach
22.7 / 30
FreshnessLast push recency
0.0 / 25
ActivityRecent commits
0.0 / 25
CommunityFork signal
12.5 / 20

Common questions about Godot MCP

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 180 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

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.

Submit a correction → Add the trust badge

Reputation Timeline

Signal history
Rank 31Grade 1
2026-10-09
Rank Moved
Rank dropped 14 spots (#1071 → #1085)
2026-09-23
Rank Moved
Rank dropped 617 spots (#411 → #1028)
2026-09-22
Rank Moved
Rank dropped 67 spots (#344 → #411)
2026-09-21
Rank Moved
Rank rose 679 spots (#1023 → #344)
2026-09-20
Rank Moved
Rank dropped 12 spots (#1011 → #1023)
2026-09-12
Rank Moved
Rank dropped 12 spots (#996 → #1008)
2026-09-11
Rank Moved
Rank dropped 13 spots (#983 → #996)
2026-09-09
Rank Moved
Rank dropped 15 spots (#970 → #985)
2026-09-08
Rank Moved
Rank dropped 12 spots (#958 → #970)
2026-09-07
Rank Moved
Rank dropped 38 spots (#920 → #958)
2026-09-06
Rank Moved
Rank dropped 11 spots (#909 → #920)
2026-09-05
Rank Moved
Rank dropped 55 spots (#854 → #909)
2026-09-04
Rank Moved
Rank dropped 35 spots (#819 → #854)
2026-09-03
Rank Moved
Rank dropped 46 spots (#773 → #819)
2026-09-02
Rank Moved
Rank dropped 38 spots (#735 → #773)
2026-09-01
Rank Moved
Rank dropped 32 spots (#703 → #735)
2026-08-31
Rank Moved
Rank dropped 32 spots (#671 → #703)
2026-08-30
Rank Moved
Rank dropped 24 spots (#647 → #671)
2026-08-29
Rank Moved
Rank dropped 45 spots (#602 → #647)
2026-08-28
Rank Moved
Rank dropped 13 spots (#589 → #602)
2026-08-27
Rank Moved
Rank dropped 16 spots (#573 → #589)
2026-08-26
Rank Moved
Rank dropped 86 spots (#487 → #573)
2026-08-24
Rank Moved
Rank dropped 16 spots (#472 → #488)
2026-08-22
Rank Moved
Rank rose 16 spots (#491 → #475)
2026-08-19
Rank Moved
Rank dropped 11 spots (#477 → #488)
2026-08-17
Rank Moved
Rank rose 10 spots (#484 → #474)
2026-08-13
Rank Moved
Rank dropped 11 spots (#460 → #471)
2026-08-12
Rank Moved
Rank rose 11 spots (#471 → #460)
2026-08-10
Rank Moved
Rank dropped 13 spots (#456 → #469)
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
GitHub → npm: @coding-solo/godot-mcp

Embed Badge Badge guide for maintainers →

For maintainers
HVTrust 45.7 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.4 · Raw JSON