Tugcantopaloglu Godot MCP

MCP server for full Godot 4.x engine control: 157 tools for AI-driven game development (GDScript and C#/.NET). Tested wi

MCP Servers JavaScript Grade D Listed MIT
33.0/100
Rank #726 of 1283
Compare Tugcantopaloglu Godot MCP

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

Open compare tool Suggest correction
Listing state
Listed
Evidence coverage
Grade C · 2/5 signals
Last push
2026-07-13 · 30d ago
Recent change
Rank +2

Is Tugcantopaloglu Godot MCP safe? Tugcantopaloglu Godot MCP scores 33.0/100 (Grade D), ranked #726 of 1283 tracked open-source AI agent projects, on evidence coverage C (2 of 5 independent signal types). The public evidence: no package-provenance attestation found; no OSSF Scorecard result yet; 21% of recent commits are signed; last pushed 2026-07-13. 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
Add or improve OSSF Scorecard coverage so safety checks are easier to verify.
Recent Changes
2026-08-10
Rank Moved
Rank dropped 40 spots (#687 → #727)
2026-08-09
Activity Score Changed
Activity score down 8pts (59 → 51)
2026-08-08
Newly Listed
First tracked at rank #669
Maintainer Checklist
Add Scorecard coverage Expose the repository to OpenSSF Scorecard checks so supply-chain posture is easier to verify.
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.
51.0
Activity sub-score · out of 100
#325

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 C is separate — it grades how many independent signal types back the score (2 of 5), so a high score on thin evidence stays visible. Full methodology →

Signals refreshed 2026-08-12 05:02 UTC · Repo last pushed 30 days ago

Rank Trend

2026-08-11 2026-08-12

Activity & Reach

Stars
403
Forks
63
Last Push
2026-07-13
30 days ago
Commits (4 wk)
2
Downloads (7d)
65
npm
HN mentions (30d)
Open Issues
4
Rank Change
▲1
was #727

Analysis

HVTrust Dimensions vs MCP Servers

33.0 / 100 · 67.0% confidence

Tugcantopaloglu Godot MCP MCP Servers average (761 agents)

Safety / Integrity50% OSSF Scorecard · 30% provenance · 20% signed commits
1.1 / 25
3.9 below avg 5.0
Identity / Provenance60% listing status · 40% build provenance
10.8 / 18
2.5 below avg 13.3
Transparency50% declared license · 50% OSSF Scorecard
8.5 / 17
in line with avg 8.8
Maintenance60% last-push freshness · 40% commit activity
11.9 / 20
0.5 below avg 12.4
AdoptionLog-scaled stars · package downloads
8.7 / 20
2.9 above avg 5.8

Activity Inputs

51.0 / 100
StarsRepository reach
15.6 / 30
FreshnessLast push recency
20.8 / 25
ActivityRecent commits
6.0 / 25
CommunityFork signal
8.4 / 20

Supply Chain Trust

Package Provenance
None
No package attestations found
OSSF Scorecard
Not available
Signed Commits
21%
of last 100 commits verified

Is Tugcantopaloglu Godot MCP safe?

Public trust evidence for Tugcantopaloglu 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 Tugcantopaloglu Godot MCP publish package provenance?
No published build provenance is currently detected for Tugcantopaloglu 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 Tugcantopaloglu Godot MCP have an OpenSSF Scorecard?
No OpenSSF Scorecard data is currently published for Tugcantopaloglu Godot MCP. Maintainers can enable the Scorecard GitHub Action to get a public score; without it, automated supply-chain hygiene is harder for outsiders to verify.
Is Tugcantopaloglu Godot MCP actively maintained?
Maintained. Last push was 30 days ago.
What license does Tugcantopaloglu Godot MCP use?
Tugcantopaloglu Godot MCP ships under MIT. A declared, OSI-approved license is one of the transparency signals HVTrust scores.
Are Tugcantopaloglu Godot MCP's commits signed?
21% of the last 100 commits to Tugcantopaloglu 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
Tugcantopaloglu 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
high 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 Tugcantopaloglu Godot MCP?

For maintainers

HVTrust scores Tugcantopaloglu 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
Listed 1Score 1Rank 1
2026-08-10
Rank Moved
Rank dropped 40 spots (#687 → #727)
2026-08-09
Activity Score Changed
Activity score down 8pts (59 → 51)
2026-08-08
Newly Listed
First tracked at rank #669

Embed Badge Badge guide for maintainers →

For maintainers
HVTrust 33.0 Grade D
Markdown:
[![HVTrust](https://hvtracker.net/badge/tugcantopaloglu-godot-mcp.svg)](https://hvtracker.net/agents/tugcantopaloglu-godot-mcp)
HTML:
<a href="https://hvtracker.net/agents/tugcantopaloglu-godot-mcp"><img src="https://hvtracker.net/badge/tugcantopaloglu-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)
Each agent's signals refresh once daily across 6 staggered batches. Methodology v4.3 · Raw JSON