Blueprint Extractor MCP Server

blueprint-extractor-mcp npm v8.2.7

Published by sungrow — no publish provenance, so origin is unverified, but the source is public: the repository link below is self-declared yet readable, so you can inspect the code before adopting it.

MCP server for the Unreal Engine BlueprintExtractor plugin over Remote Control

Trust grade
A
93/100
Last scanned get badge →
Trust
A · 93/100
Adoption risk for you: the threat score, then adjusted down for blast radius, publisher verification and how much the scan could see. Deterministic; every point is auditable.
Capability
High
Blast radius if it went rogue — what the server’s tools could reach. Independent of trust.
Coverage
Source
How much the scan could actually inspect. Shallow coverage is stated, never hidden.
Share this Trust Score
𝕏 Share LinkedIn Reddit
A Why this grade threat 100 − adoption risk = 93/100

The grade answers one question — how safe is this server for you to adopt — so it is computed in two auditable stages. Nothing below is an opinion or an LLM's guess; every line is a real term the deterministic engine applied, and the same input always yields the same number.

1. Threat score — 100 − 0 = 100. What the published surface and source actually contain:

The deterministic scan raised no scored threat in the surface it inspected — the threat score stayed at 100. Capability observations and advisory notes are recorded but never lower it.

2. Client adoption risk — 100 − 7 = 93. Three small, subtract-only factors that reflect your risk in adopting it — a clean scan proves less on a powerful, unverified or barely-inspectable package, so the grade says so plainly:

PointsAdoption-risk factor
−6 capability blast radius (high) — client exposure if the model is manipulated
−1 publisher verification (public source) — no provenance, but the source is public and inspectable

Capability observations and info notes are shown under Findings but never scored. Open any row's finding below for the file, line and evidence behind a deduction.

Findings 3

high Shell/command execution in server code (dist/automation-controller.js)MTC-SRC-002

In the server's implementation (`dist/automation-controller.js:2`): Spawning a shell/process is command-execution capability; with unsanitized tool input it is command injection / RCE. This is read from the code itself — not from the tool description — so a poisoned server cannot hide it behind honest-looking metadata.

Evidence: rt { spawn } from 'node:child_process'; import { mkdir, readdir, readFile, writeFile } from 'node:fs/promises'; import {

Fix: Review this call path: confirm it never receives unsanitized tool input, constrain it, or remove it. Treat a server whose code reaches these sinks as high-capability regardless of what its tools claim.

Location: server dist/automation-controller.js

high Shell/command execution in server code (dist/execution/adapters/commandlet-adapter.js)MTC-SRC-002

In the server's implementation (`dist/execution/adapters/commandlet-adapter.js:5`): Spawning a shell/process is command-execution capability; with unsanitized tool input it is command injection / RCE. This is read from the code itself — not from the tool description — so a poisoned server cannot hide it behind honest-looking metadata.

Evidence: import { spawn } from 'child_process'; import { COMMANDLET_CAPABILITIES } from '../execution-adapter.js'; import { reso

Fix: Review this call path: confirm it never receives unsanitized tool input, constrain it, or remove it. Treat a server whose code reaches these sinks as high-capability regardless of what its tools claim.

Location: server dist/execution/adapters/commandlet-adapter.js

high Shell/command execution in server code (dist/project-controller.js)MTC-SRC-002

In the server's implementation (`dist/project-controller.js:1`): Spawning a shell/process is command-execution capability; with unsanitized tool input it is command injection / RCE. This is read from the code itself — not from the tool description — so a poisoned server cannot hide it behind honest-looking metadata.

Evidence: ync, spawn } from 'node:child_process'; import { access, readdir, unlink } from 'node:fs/promises'; import { constants a

Fix: Review this call path: confirm it never receives unsanitized tool input, constrain it, or remove it. Treat a server whose code reaches these sinks as high-capability regardless of what its tools claim.

Location: server dist/project-controller.js

Tools 115

Each tool and what it can reach — statically extracted from the published source.

  • read_message_logingests untrusted input
  • activate_tool_profileno sensitive capability
  • activate_workflow_scopeno sensitive capability
  • apply_commonui_button_styleno sensitive capability
  • apply_widget_diffno sensitive capability
  • apply_widget_patchno sensitive capability
  • apply_window_ui_changesno sensitive capability
  • audit_project_assetsno sensitive capability
  • batch_widget_operationsno sensitive capability
  • capture_editor_screenshotno sensitive capability
Show 105 more tools ↓
  • capture_runtime_screenshotno sensitive capability
  • capture_widget_motion_checkpointsno sensitive capability
  • capture_widget_previewno sensitive capability
  • check_asset_existsno sensitive capability
  • cleanup_capturesno sensitive capability
  • clear_editor_selectionno sensitive capability
  • compare_capture_to_referenceno sensitive capability
  • compare_motion_capture_bundleno sensitive capability
  • compile_material_assetno sensitive capability
  • compile_project_codeno sensitive capability
  • compile_widgetno sensitive capability
  • create_anim_montageno sensitive capability
  • create_anim_sequenceno sensitive capability
  • create_behavior_treeno sensitive capability
  • create_blackboardno sensitive capability
  • create_blend_spaceno sensitive capability
  • create_blueprintno sensitive capability
  • create_commonui_button_styleno sensitive capability
  • create_curveno sensitive capability
  • create_curve_tableno sensitive capability
  • create_data_assetno sensitive capability
  • create_data_tableno sensitive capability
  • create_input_actionno sensitive capability
  • create_input_mapping_contextno sensitive capability
  • create_materialno sensitive capability
  • create_material_instanceno sensitive capability
  • create_material_setupno sensitive capability
  • create_menu_screenno sensitive capability
  • create_state_treeno sensitive capability
  • create_user_defined_enumno sensitive capability
  • create_user_defined_structno sensitive capability
  • create_widget_animationno sensitive capability
  • create_widget_blueprintno sensitive capability
  • execute_widget_recipeno sensitive capability
  • extract_assetno sensitive capability
  • extract_blueprintno sensitive capability
  • extract_cascadeno sensitive capability
  • extract_commonui_button_styleno sensitive capability
  • extract_materialno sensitive capability
  • extract_widget_animationno sensitive capability
  • extract_widget_blueprintno sensitive capability
  • find_and_extractno sensitive capability
  • get_active_editorno sensitive capability
  • get_automation_test_runno sensitive capability
  • get_editor_contextno sensitive capability
  • get_import_jobno sensitive capability
  • get_project_automation_contextno sensitive capability
  • get_project_index_statusno sensitive capability
  • get_tool_helpno sensitive capability
  • import_assetsno sensitive capability
  • insert_widget_childno sensitive capability
  • launch_editorno sensitive capability
  • list_assetsno sensitive capability
  • list_automation_test_runsno sensitive capability
  • list_capturesno sensitive capability
  • list_import_jobsno sensitive capability
  • list_message_log_listingsno sensitive capability
  • list_running_editorsno sensitive capability
  • material_graph_operationno sensitive capability
  • modify_anim_montageno sensitive capability
  • modify_anim_sequenceno sensitive capability
  • modify_behavior_treeno sensitive capability
  • modify_blackboardno sensitive capability
  • modify_blend_spaceno sensitive capability
  • modify_blueprint_graphsno sensitive capability
  • modify_blueprint_membersno sensitive capability
  • modify_commonui_button_styleno sensitive capability
  • modify_curveno sensitive capability
  • modify_curve_tableno sensitive capability
  • modify_data_assetno sensitive capability
  • modify_data_tableno sensitive capability
  • modify_input_actionno sensitive capability
  • modify_input_mapping_contextno sensitive capability
  • modify_materialno sensitive capability
  • modify_material_instanceno sensitive capability
  • modify_state_treeno sensitive capability
  • modify_user_defined_enumno sensitive capability
  • modify_user_defined_structno sensitive capability
  • modify_widget_animationno sensitive capability
  • move_widgetno sensitive capability
  • patch_widgetno sensitive capability
  • patch_widget_class_defaultsno sensitive capability
  • read_output_logno sensitive capability
  • read_statetree_debuggerno sensitive capability
  • refresh_project_indexno sensitive capability
  • relaunch_pieno sensitive capability
  • remove_widgetno sensitive capability
  • replace_widget_classno sensitive capability
  • replace_widget_treeno sensitive capability
  • restart_editorno sensitive capability
  • review_blueprintno sensitive capability
  • run_automation_testsno sensitive capability
  • save_assetsno sensitive capability
  • scaffold_blueprintno sensitive capability
  • search_assetsno sensitive capability
  • search_project_contextno sensitive capability
  • select_editorno sensitive capability
  • start_pieno sensitive capability
  • start_statetree_debuggerno sensitive capability
  • stop_pieno sensitive capability
  • stop_statetree_debuggerno sensitive capability
  • sync_project_codeno sensitive capability
  • trigger_live_codingno sensitive capability
  • wait_for_editorno sensitive capability
  • wrap_widgetno sensitive capability

What this scan could not see

Versions 1

Scan history per published version. The engine is deterministic — the same version always yields the same score, so a changed score means the package itself changed.

VersionScoreFindingsEngineScanned
v8.2.7 latest A 93/100 3 1.13.0 2026-09-07

Embed this score

Show this server's live Trust Score in your README, docs or website. The badge is served straight from the registry and updates automatically after every rescan — no API key needed. It links back to this page, so anyone who sees the grade can also read the findings behind it instead of taking a number on faith.

MCP Trust Score: A · 93/100
Markdown (GitHub README)
[![MCP Trust Score](https://mcptrustchecker.com/registry/blueprint-extractor-mcp/badge.svg)](https://mcptrustchecker.com/registry/blueprint-extractor-mcp)
HTML
<a href="https://mcptrustchecker.com/registry/blueprint-extractor-mcp"><img src="https://mcptrustchecker.com/registry/blueprint-extractor-mcp/badge.svg" alt="MCP Trust Score" height="20"></a>
Prefer shields.io styling? Point it at https://mcptrustchecker.com/registry/blueprint-extractor-mcp/badge.json via https://img.shields.io/endpoint?url=…

Verify this score yourself

The score above is reproducible: the same package version always yields the same result. Run it locally or over the free API — no account, no LLM, fully deterministic.

npx mcptrustchecker scan blueprint-extractor-mcp --online

Use the free API → How scoring works

More in Gaming & Entertainment