Is Unreal Engine API Documentation safe to use?

Unreal Engine API Documentation has an HVTrust score of 61.6/100 (Grade C), ranked #589 of 1325 tracked AI agent projects. This score reflects verifiable supply-chain integrity, transparency, maintenance, and adoption signals.

What is the trust score for Unreal Engine API Documentation?

Unreal Engine API Documentation scores 61.6/100 on HVTracker's evidence-weighted HVTrust scale. It has 97 GitHub stars and is categorized under MCP Servers.

Unreal Engine API Documentation

Codeturion/unreal-api-mcp

Instant, accurate Unreal Engine API lookups instead of expensive source file reads, saving your agent tokens, context, and hallucinations.

MCP Servers Python Listed MIT

Is Unreal Engine API Documentation safe? Promising trust profile, but some evidence still deserves review.

OSSF Scorecard 3.3 / 10

Provenance Attested

Signed commits 6%

Last push 69d ago

Compare Unreal Engine API Documentation

How does it stack up against its MCP Servers neighbours?

Pick any agent to compare →

Suggest a correction

In detail: Unreal Engine API Documentation scores 61.6/100 (Grade C), ranked #589 of 1325 tracked open-source AI agent projects, on evidence coverage B (3 of 5 independent signal types). The public evidence: its packages ship with cryptographic provenance; OSSF Scorecard rates its supply-chain practices 3.3/10; 6% of recent commits are signed; last pushed 2026-07-19. Every point is earned from checkable signals — never paid placement. How scoring works →

How Unreal Engine API Documentation compares in MCP Servers

#331 Arxiv MCP Server 61.8 +0.2
#332 Persistent Project Context for xAI Grok 61.7 +0.1
#333 Unreal Engine API Documentation 61.6 this agent
#334 Web Researcher MCP 61.5 −0.1
#335 MCP Me 61.4 −0.2

Bars show each HVTrust score; the tick marks Unreal Engine API Documentation’s 61.6.

Where the 61.6 comes from

HVTrust dimensions vs the MCP Servers average

61.6 / 100 · 100.0% confidence

Unreal Engine API Documentation MCP Servers average (775 agents)

Safety / Integrity50% OSSF Scorecard · 30% provenance · 20% signed commits

11.9 / 25

1.6 above avg 10.3

Identity / Provenance60% listing status · 40% build provenance

18.0 / 18

4.6 above avg 13.4

Transparency50% declared license · 50% OSSF Scorecard

11.3 / 17

0.9 below avg 12.2

Maintenance60% last-push freshness · 40% commit activity

7.4 / 20

4.7 below avg 12.1

AdoptionLog-scaled stars · package downloads

7.0 / 20

in line with avg 7.2

Quick Trust Read

What Would Improve It

Increase the share of verified signed commits for clearer maintainer identity.

Recent Changes

2026-09-23

Mcp Status Changed

Detected MCP server support changed: none → implemented

2026-09-23

Provenance Added

Package provenance attestation detected

2026-09-23

Grade Changed

Trust grade D → C

Maintainer Checklist

Raise Scorecard signals Current OSSF Scorecard is 3.3/10. Tighten the weakest checks to improve public safety evidence.

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 69 days ago. Fresh activity helps separate stable projects from stale ones.

Compare with another agent Get email alerts for Unreal Engine API Documentation View MCP Servers Report missing data

32.7

Activity sub-score · out of 100

#333

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

2026-08-11 2026-09-26

Activity & Reach

Stars

Forks

Last Push

2026-07-19

69 days ago

Commits (4 wk)

Downloads (7d)

pypi

HN mentions (30d)

—

Open Issues

Rank Change

▼6

was #583

Analysis

Activity Inputs

32.7 / 100

StarsRepository reach

11.9 / 30

FreshnessLast push recency

15.4 / 25

ActivityRecent commits

0.0 / 25

CommunityFork signal

5.2 / 20

Supply Chain Trust

Package Provenance

Verified

pypi attestation

OSSF Scorecard

3.3 / 10

OpenSSF Scorecard · scanned Sep 22, 2026

Signed Commits

of last 100 commits verified

Binary-Artifacts 10

Branch-Protection 0

CI-Tests 3

CII-Best-Practices 0

Code-Review 0

Contributors 3

Dangerous-Workflow 10

Dependency-Update-Tool 0

Fuzzing 0

License 10

Maintained 1

Packaging 10

Pinned-Dependencies 0

SAST 0

Security-Policy 0

Signed-Releases 0

Token-Permissions 0

Vulnerabilities 10

Common questions about Unreal Engine API Documentation

Unreal Engine API Documentation has a mixed signal profile. Some trust indicators are present, others are missing. Whether it is safe for your use case depends on which gaps matter to you — review the breakdown below before adopting in production.

Does Unreal Engine API Documentation publish package provenance?

Yes. Unreal Engine API Documentation's package releases carry build provenance attestations, which cryptographically link the published package back to its source repository and CI workflow.

Does Unreal Engine API Documentation have an OpenSSF Scorecard?

Unreal Engine API Documentation has an OpenSSF Scorecard score of 3.3/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 Unreal Engine API Documentation actively maintained?

Slowing down. Last push was 69 days ago — keep an eye on whether activity resumes.

What license does Unreal Engine API Documentation use?

Unreal Engine API Documentation ships under MIT. A declared, OSI-approved license is one of the transparency signals HVTrust scores.

Are Unreal Engine API Documentation's commits signed?

5% of the last 100 commits to Unreal Engine API Documentation 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

medium confidence

Implemented

Unreal Engine API Documentation 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 Unreal Engine API Documentation'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-09-23

Provenance Added

Package provenance attestation detected

Maintain Unreal Engine API Documentation?

For maintainers

HVTrust scores Unreal Engine API Documentation 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

2026-09-23

Mcp Status Changed

Detected MCP server support changed: none → implemented

2026-09-23

Provenance Added

Package provenance attestation detected

2026-09-23

Grade Changed

Trust grade D → C

2026-09-23

Rank Moved

Rank rose 596 spots (#1175 → #579)

2026-09-23

HVTrust Changed

HVTrust up 41.7pts (20.1 → 61.8)

2026-09-22

Newly Listed

First tracked at rank #1175

2026-09-21

Removed From Active Tracking

Removed from active tracking

2026-09-20

Rank Moved

Rank dropped 14 spots (#538 → #552)

2026-09-11

Rank Moved

Rank dropped 17 spots (#492 → #509)

2026-09-08

Rank Moved

Rank dropped 13 spots (#477 → #490)

2026-09-07

Rank Moved

Rank dropped 31 spots (#446 → #477)

2026-09-06

Rank Moved

Rank dropped 23 spots (#423 → #446)

2026-09-05

Rank Moved

Rank dropped 67 spots (#356 → #423)

2026-09-03

Rank Moved

Rank dropped 23 spots (#327 → #350)

2026-09-01

Scorecard Added

OSSF Scorecard: 3.3/10

2026-09-01

Rank Moved

Rank rose 148 spots (#467 → #319)

2026-09-01

HVTrust Changed

HVTrust up 6.9pts (57.3 → 64.2)

2026-08-31

Rank Moved

Rank dropped 32 spots (#435 → #467)

2026-08-29

Rank Moved

Rank dropped 14 spots (#430 → #444)

2026-08-26

Rank Moved

Rank dropped 40 spots (#376 → #416)

2026-08-24

Rank Moved

Rank dropped 19 spots (#352 → #371)

2026-08-22

Rank Moved

Rank rose 16 spots (#370 → #354)

2026-08-19

Rank Moved

Rank dropped 13 spots (#357 → #370)

2026-08-18

Rank Moved

Rank dropped 37 spots (#320 → #357)

2026-08-18

Activity Score Changed

Activity score down 6pts (44 → 38)

2026-08-17

Rank Moved

Rank rose 15 spots (#335 → #320)

2026-08-13

Rank Moved

Rank dropped 18 spots (#306 → #324)

2026-08-12

Rank Moved

Rank rose 14 spots (#320 → #306)

2026-08-10

Rank Moved

Rank dropped 18 spots (#303 → #321)

2026-08-08

Newly Listed

First tracked at rank #299

GitHub → PyPI: unreal-api-mcp

Embed Badge Badge guide for maintainers →

For maintainers

Markdown:
            [![HVTrust](https://hvtracker.net/badge/unreal-engine-api-documentation.svg)](https://hvtracker.net/agents/unreal-engine-api-documentation)
            
HTML:
            <a href="https://hvtracker.net/agents/unreal-engine-api-documentation"><img src="https://hvtracker.net/badge/unreal-engine-api-documentation.svg" alt="HVTrust"></a>

Other agents in MCP Servers

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