Tomyud1 Godot MCP

MCP Server and Godot Plugin for AI-assisted game development

MCP Servers GDScript Listed MIT

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

OSSF Scorecard 2.7 / 10
Provenance None
Signed commits 19%
Last push 53d ago
Advisories None known
Compare Tomyud1 Godot MCP
Suggest a correction

In detail: Tomyud1 Godot MCP scores 50.3/100 (Grade C), ranked #1004 of 1378 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 2.7/10; 19% of recent commits are signed; no published advisory affects its latest release (godot-mcp-server); last pushed 2026-08-24. Every point is earned from checkable signals — never paid placement. How scoring works →

How Tomyud1 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.

Chain of custody

Scanners check what the code says. This traces who ships Tomyud1 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/tomyud1/godot-mcp, MIT, last pushed 2026-08-24. 19% 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 2.7/10 (scanned Oct 16, 2026). The checks that decide who can get a change released:

    • Code Review0
    • 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 0
    Contributors 0
    Dangerous-Workflow -1
    Dependency-Update-Tool 0
    Fuzzing 0
    License 10
    Maintained 2
    Packaging -1
    Pinned-Dependencies -1
    SAST 0
    Security-Policy 0
    Signed-Releases -1
    Token-Permissions -1
    Vulnerabilities 10
  3. Published packages Linked, not attested

    • npm godot-mcp-server Source link points back to this repo No build attestation

    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: godot-mcp-server 0.6.0. No published advisory affects it (OSV, checked 2026-10-16).

Changes to this chain

  • 2026-09-15 OSSF Scorecard: 2.5/10

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 Tomyud1 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.

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 Tomyud1 Godot MCP compares in MCP Servers

  1. #562 MCP Documentation Server 50.3 ±0
  2. #563 JADX MCP Server 50.3 ±0
  3. #564 Tomyud1 Godot MCP 50.3 this agent
  4. #565 OSS Snowflake MCP Server 50.2 −0.1
  5. #566 Weather MCP Server 50.2 −0.1

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

Where the 50.3 comes from

HVTrust dimensions vs the MCP Servers average

50.3 / 100 · 100.0% confidence

Tomyud1 Godot MCP MCP Servers average (781 agents)

Safety / Integrity50% OSSF Scorecard · 30% provenance · 20% signed commits
4.3 / 25
6.2 below avg 10.5
Identity / Provenance60% listing status · 40% build provenance
10.8 / 18
2.7 below avg 13.5
Transparency50% declared license · 50% OSSF Scorecard
10.8 / 17
1.5 below avg 12.3
Maintenance60% last-push freshness · 40% commit activity
8.5 / 20
3.8 below avg 12.3
AdoptionLog-scaled stars · package downloads
9.9 / 20
2.5 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-15
Rank Moved
Rank dropped 10 spots (#988 → #998)
2026-10-14
Rank Moved
Rank dropped 12 spots (#976 → #988)
2026-10-09
Rank Moved
Rank dropped 19 spots (#940 → #959)
Maintainer Checklist
Raise Scorecard signals Current OSSF Scorecard is 2.7/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 53 days ago. Fresh activity helps separate stable projects from stale ones.
41.3
Activity sub-score · out of 100
#564

How to read this: HVTrust (0–100) weighs supply-chain signals (provenance, OSSF Scorecard, signed commits, open license) alongside real-world adoption. Grade C 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-16 20:06 UTC · Repo last pushed 53 days ago

Rank Trend

2026-09-29 2026-10-16

Activity & Reach

Stars
435
Forks
50
Last Push
2026-08-24
53 days ago
Commits (4 wk)
0
Downloads (7d)
467
npm
HN mentions (30d)
—
Open Issues
13
Rank Change
▼6
was #998

Analysis

Activity Inputs

41.3 / 100
StarsRepository reach
15.8 / 30
FreshnessLast push recency
17.6 / 25
ActivityRecent commits
0.0 / 25
CommunityFork signal
7.9 / 20

Common questions about Tomyud1 Godot MCP

Public trust evidence for Tomyud1 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 Tomyud1 Godot MCP publish package provenance?
No published build provenance is currently detected for Tomyud1 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 Tomyud1 Godot MCP have an OpenSSF Scorecard?
Tomyud1 Godot MCP has an OpenSSF Scorecard score of 2.7/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 Tomyud1 Godot MCP actively maintained?
Slowing down. Last push was 53 days ago — keep an eye on whether activity resumes.
What license does Tomyud1 Godot MCP use?
Tomyud1 Godot MCP ships under MIT. A declared, OSI-approved license is one of the transparency signals HVTrust scores.
Are Tomyud1 Godot MCP's commits signed?
18% of the last 100 commits to Tomyud1 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
Tomyud1 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
None detected
No clear plugin system or broad tool surface detected.
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 Tomyud1 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-09-23
Mcp Status Changed
Detected MCP server support changed: none → implemented
2026-08-24
Activity Resumed
Activity resumed

Maintain Tomyud1 Godot MCP?

For maintainers

HVTrust scores Tomyud1 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 24HVTrust 4Listed 2Grade 2Score 1Fresh 1Scorecard 1Delisted 1MCP 1
2026-10-15
Rank Moved
Rank dropped 10 spots (#988 → #998)
2026-10-14
Rank Moved
Rank dropped 12 spots (#976 → #988)
2026-10-09
Rank Moved
Rank dropped 19 spots (#940 → #959)
2026-09-30
Rank Moved
Rank dropped 15 spots (#909 → #924)
2026-09-23
Mcp Status Changed
Detected MCP server support changed: none → implemented
2026-09-23
Grade Changed
Trust grade D → C
2026-09-23
Rank Moved
Rank rose 189 spots (#1078 → #889)
2026-09-23
HVTrust Changed
HVTrust up 28.9pts (22.7 → 51.6)
2026-09-22
Newly Listed
First tracked at rank #1078
2026-09-21
Removed From Active Tracking
Removed from active tracking
2026-09-20
Rank Moved
Rank dropped 11 spots (#838 → #849)
2026-09-15
Scorecard Added
OSSF Scorecard: 2.5/10
2026-09-15
Grade Changed
Trust grade D → C
2026-09-15
Rank Moved
Rank rose 417 spots (#1259 → #842)
2026-09-15
HVTrust Changed
HVTrust up 19.1pts (33.8 → 52.9)
2026-09-09
Rank Moved
Rank dropped 12 spots (#1237 → #1249)
2026-09-07
Rank Moved
Rank dropped 25 spots (#1203 → #1228)
2026-09-06
Rank Moved
Rank dropped 21 spots (#1182 → #1203)
2026-09-05
Rank Moved
Rank dropped 34 spots (#1148 → #1182)
2026-09-04
Rank Moved
Rank dropped 12 spots (#1136 → #1148)
2026-09-03
Rank Moved
Rank rose 120 spots (#1256 → #1136)
2026-09-03
HVTrust Changed
HVTrust up 13.2pts (21.7 → 34.9)
2026-09-02
Rank Moved
Rank dropped 26 spots (#1230 → #1256)
2026-09-01
Rank Moved
Rank dropped 26 spots (#1204 → #1230)
2026-08-31
Rank Moved
Rank dropped 28 spots (#1176 → #1204)
2026-08-30
Rank Moved
Rank dropped 31 spots (#1145 → #1176)
2026-08-29
Rank Moved
Rank dropped 31 spots (#1114 → #1145)
2026-08-28
Rank Moved
Rank dropped 25 spots (#1089 → #1114)
2026-08-27
Rank Moved
Rank dropped 23 spots (#1066 → #1089)
2026-08-26
Rank Moved
Rank dropped 74 spots (#992 → #1066)
2026-08-24
Activity Resumed
Activity resumed
2026-08-24
Rank Moved
Rank rose 175 spots (#1166 → #991)
2026-08-24
HVTrust Changed
HVTrust up 3.8pts (18.1 → 21.9)
2026-08-24
Activity Score Changed
Activity score up 21pts (31 → 52)
2026-08-16
Rank Moved
Rank dropped 28 spots (#1140 → #1168)
2026-08-10
Rank Moved
Rank dropped 67 spots (#1071 → #1138)
2026-08-08
Newly Listed
First tracked at rank #1072

Embed Badge Badge guide for maintainers →

For maintainers
HVTrust 50.3 Grade C
Markdown:
[![HVTrust](https://hvtracker.net/badge/tomyud1-godot-mcp.svg)](https://hvtracker.net/agents/tomyud1-godot-mcp)
HTML:
<a href="https://hvtracker.net/agents/tomyud1-godot-mcp"><img src="https://hvtracker.net/badge/tomyud1-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