Unreal Engine API Documentation
PYPI · UNREAL-API-MCP
Accurate UE5 C++ API docs for AI agents. Prevents hallucinated signatures and includes.
Available components
Last scanned (4 hours ago)
Scores higher than 91% of PyPI servers
Category Code Search and Documentation
How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score → Why this is hard to score →
Supply Chain Security100
- No malware found by supply-chain analysis.Pass
- No known CVEs affecting this package version or its production dependencies.Pass
- Runs hatchling.build at install time, a recognised build step with no custom scripting around it. View diagnostics → Pass
- 0 of 28 dependencies flagged as unhealthy. View diagnostics → Pass
Provenance & Transparency97
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Cryptographically verified build provenance (signed, bound to Codeturion/unreal-api-mcp). View diagnostics → Pass
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 24 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability68
- AI-judged instruction clarity (good).Pass
- Tool/resource definitions use about 370 tokens (~74/item across 5 items; 5 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management73
- Stability observed for 22 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage71
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 0% of tool parameters carry a description.Fail
- Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 5 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 6 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 5 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 70 to 73. That category is still filling its 30-day observation window: 21 days of observed history at the previous scan, 22 at this one. The score rises as the window fills, whether or not the server changes.
- 3 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 63 to 67. That category is still filling its 30-day observation window: 19 days of observed history at the previous scan, 20 at this one. The score rises as the window fills, whether or not the server changes.
- 1 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 57 to 60. That category is still filling its 30-day observation window: 17 days of observed history at the previous scan, 18 at this one. The score rises as the window fills, whether or not the server changes.
- 31 Oct 26 0
- Security disclosure: unverified → fail ▼ functional
- 30 Oct 26 +1
- Security disclosure: fail → unverified ▼ functional
- 28 Oct 26 +16
- Malware scan: unverified → pass ▲ security
- 27 Oct 26 −15
- Malware scan: pass → unverified ▼ security
- 26 Oct 26 +15
- Malware scan: unverified → pass ▲ security
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 5 Nov 2026 · Analysed pypi/unreal-api-mcp@0.3.1
Provenance Verified
A signed build attestation was found and verified, binding this exact artifact to the source repository it claims to come from.
| Result | Verified |
|---|---|
| Ecosystem | pypi |
| Reason | Verified |
| Discovered via | Registry attestation endpoint |
| Source repo | Codeturion/unreal-api-mcp |
| Certificate issuer | https://token.actions.githubusercontent.com |
| Certificate SAN | https://github.com/Codeturion/unreal-api-mcp/.github/workflows/publish.yml@refs/tags/v0.3.1 |
| Rekor log index | 3217082924 |
| Predicate type | PyPI publish attestation https://docs.pypi.org/attestations/publish/v1 |
| Subject digest | sha256:4621a8eaf5aa8bdf95a3dfdeb3db8eee19053b058b6947fb4f2cf41b6516bd46 |
Background: How many MCP packages publish verified provenance →
Install scripts 1 script
| Hook | Tier | Command |
|---|---|---|
| build_backend | allowlisted | hatchling.build |
Background: Why install scripts are a supply-chain risk →
Dependencies 28 packages
| Packages resolved | 28 |
|---|---|
| Tree resolution | Complete |
Background: SBOMs and build attestations, explained →
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
get_class_reference ~54
Get all public members of an Unreal Engine class. Args: class_name: The class name (e.g. "AActor", "ACharacter", "UGameplayStatics").
| Name | Type | Req | Description |
|---|---|---|---|
| class_name | string | yes | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
get_deprecation_warnings ~45
Check if an Unreal Engine API is deprecated. Args: name: API name to check (function, class, property, etc.).
| Name | Type | Req | Description |
|---|---|---|---|
| name | string | yes | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
get_function_signature ~61
Get the exact signature of an Unreal Engine function by fully-qualified name. Args: fqn: Fully-qualified name like "AActor::GetActorLocation" or "UGameplayStatics::SpawnActor".
| Name | Type | Req | Description |
|---|---|---|---|
| fqn | string | yes | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
get_include_path ~59
Get the #include path for an Unreal Engine class, struct, or type. Args: name: Class or type name (e.g. "AActor", "FHitResult", "ECollisionChannel").
| Name | Type | Req | Description |
|---|---|---|---|
| name | string | yes | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
search_unreal_api ~109
Search the Unreal Engine API by keyword. Args: query: Search terms (class name, function name, or keyword). n_results: Number of results to return (1-20, default 10). member_type: Filter by type: "class", "struct", "enum", "function", "property", or "delegate". Leave empty for all.
| Name | Type | Req | Description |
|---|---|---|---|
| member_type | string | – | – |
| n_results | integer | – | – |
| query | string | yes | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
How do I install the Unreal Engine API Documentation MCP server?
Unreal Engine API Documentation runs locally as a PyPI package, launched with uvx unreal-api-mcp. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
pypi · unreal-api-mcp
claude mcp add codeturion-unreal-api-mcp -- uvx unreal-api-mcp
What is the Unreal Engine API Documentation MCP server?
Unreal Engine API Documentation is an MCP server listed in the public MCP registry as io.github.Codeturion/unreal-api-mcp. Accurate UE5 C++ API docs for AI agents. Prevents hallucinated signatures and includes. This page covers its PyPI package (unreal-api-mcp).
Is the Unreal Engine API Documentation MCP server safe to use?
Unreal Engine API Documentation scores 88 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 5 November 2026. Its build provenance is signed and verified. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the Unreal Engine API Documentation MCP server expose?
Unreal Engine API Documentation exposes 5 tools: search_unreal_api, get_function_signature, get_include_path, get_class_reference, get_deprecation_warnings. Their descriptions and schemas cost roughly 328 tokens of context every time the server is loaded.
Is the Unreal Engine API Documentation MCP server still maintained?
Unreal Engine API Documentation is still listed as active in the MCP registry. We last reached this channel on 5 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.
What licence is the Unreal Engine API Documentation MCP server under?
Unreal Engine API Documentation declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.