Tugcantopaloglu Godot MCP
MCP server for full Godot 4.x engine control: 157 tools for AI-driven game development (GDScript and C#/.NET). Tested with Godot 4.7.
Is Tugcantopaloglu Godot MCP safe? Thin or incomplete trust evidence. Review carefully before production use.
Compare Tugcantopaloglu Godot MCP
How does it stack up against its MCP Servers neighbours?
Pick any agent to compare →In detail: Tugcantopaloglu Godot MCP scores 54.6/100 (Grade C), ranked #854 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 3.0/10; 19% of recent commits are signed; no published advisory affects its latest release (@tugcantopaloglu/godot-mcp); last pushed 2026-10-09. Every point is earned from checkable signals — never paid placement. How scoring works →
How Tugcantopaloglu 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.
- Publish build provenance for its packagesnpm publish --provenance from CI +14.7 → 69.3 B · #222 of 781
- Raise the OSSF Scorecard from 3.0 to 9.0lowest checks: Branch-Protection 0, CII-Best-Practices 0, Code-Review 0 +12.5 → 67.1 B · #262 of 781
- Sign every commit19% signed today +4.1 → 58.7 C · #386 of 781
Chain of custody
Scanners check what the code says. This traces who ships Tugcantopaloglu 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.
-
Source Partly signed
github.com/tugcantopaloglu/godot-mcp, MIT, last pushed 2026-10-09. 19% of the last 100 commits carry a verified signature; the rest can't be tied to a verified identity.
-
Review and release Weak
OpenSSF Scorecard rates the repository's practices 3.0/10 (scanned Oct 8, 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 10Branch-Protection 0CI-Tests 6CII-Best-Practices 0Code-Review 0Contributors 3Dangerous-Workflow -1Dependency-Update-Tool 0Fuzzing 0License 10Maintained 10Packaging -1Pinned-Dependencies -1SAST 3Security-Policy 0Signed-Releases -1Token-Permissions -1Vulnerabilities 0 -
Published packages Linked, not attested
- npm @tugcantopaloglu/godot-mcp Source link points back to this repo No build attestation
Without a build attestation, nothing proves the published files were built from this repository.
-
What you install today No known advisories
Latest release checked: @tugcantopaloglu/godot-mcp 1.0.0. No published advisory affects it (OSV, checked 2026-10-16).
Changes to this chain
- 2026-08-26 OSSF Scorecard: 3.0/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 Tugcantopaloglu 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 Tugcantopaloglu Godot MCP compares in MCP Servers
- #463 Three.js DevTools MCP 54.7 +0.1
- #464 FreeCAD MCP 54.6 ±0
- #465 Tugcantopaloglu Godot MCP 54.6 this agent
- #466 IT Glue 54.5 −0.1
- #467 DexPaprika 54.5 −0.1
Bars show each HVTrust score; the tick marks Tugcantopaloglu Godot MCP’s 54.6.
Where the 54.6 comes from
HVTrust dimensions vs the MCP Servers average
54.6 / 100 · 100.0% confidenceTugcantopaloglu Godot MCP MCP Servers average (781 agents)
Quick Trust Read
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 →
Rank Trend
Activity & Reach
Analysis
Activity Inputs
57.5 / 100Common questions about Tugcantopaloglu Godot MCP
Does Tugcantopaloglu Godot MCP publish package provenance?
Does Tugcantopaloglu Godot MCP have an OpenSSF Scorecard?
Is Tugcantopaloglu Godot MCP actively maintained?
What license does Tugcantopaloglu Godot MCP use?
Are Tugcantopaloglu Godot MCP's commits signed?
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
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 →
- filesystem
- MCP signal live
- External deps live
- Tool / plugin surface live
- Package provenance drift live
Detected changes to Tugcantopaloglu 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.
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
Embed Badge Badge guide for maintainers →
For maintainers
[](https://hvtracker.net/agents/tugcantopaloglu-godot-mcp)
<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
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