Cura MCP Server
cura-mcp
PyPI
v0.5.0
Published by an unidentified publisher — no publish provenance and no public repository, so the publisher could not be verified and the source cannot be independently located.
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 − 5 = 95. 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:
| Points | Adoption-risk factor |
|---|---|
| −3 | capability blast radius (moderate) — client exposure if the model is manipulated |
| −2 | publisher verification (unlinked) — no provenance/repo link, but the shipped source was fully read |
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 0
Tools 49
Each tool and what it can reach — statically extracted from the published source.
open_projectnetwork egresssave_projectnetwork egressarrange_allno sensitive capabilitycenter_modelno sensitive capabilityclear_plateno sensitive capabilityduplicate_modelno sensitive capabilityexport_gcodeno sensitive capabilityexport_modelno sensitive capabilityget_all_user_settingsno sensitive capabilityget_estimatesno sensitive capability
Show 39 more tools ↓
get_machine_infono sensitive capabilityget_model_settingsno sensitive capabilityget_qualityno sensitive capabilityget_settingno sensitive capabilityget_snapshotno sensitive capabilityget_statusno sensitive capabilitygroup_modelsno sensitive capabilitylay_flatno sensitive capabilitylist_machinesno sensitive capabilitylist_materialsno sensitive capabilitylist_modelsno sensitive capabilitylist_quality_profilesno sensitive capabilitylist_variantsno sensitive capabilityload_modelno sensitive capabilitymerge_modelsno sensitive capabilitymirror_modelno sensitive capabilitymove_modelno sensitive capabilityremove_modelno sensitive capabilityreset_all_settingsno sensitive capabilityreset_model_settingno sensitive capabilityreset_orientationno sensitive capabilityreset_settingno sensitive capabilityrotateno sensitive capabilityscale_modelno sensitive capabilityscale_to_fitno sensitive capabilityselect_modelno sensitive capabilityset_adhesionno sensitive capabilityset_infill_densityno sensitive capabilityset_layer_heightno sensitive capabilityset_mesh_typeno sensitive capabilityset_model_settingno sensitive capabilityset_qualityno sensitive capabilityset_settingno sensitive capabilityset_supportsno sensitive capabilitysliceno sensitive capabilityswitch_machineno sensitive capabilityswitch_materialno sensitive capabilityswitch_variantno sensitive capabilityungroup_modelno sensitive capability
What this scan could not see
- Tools were statically extracted from the published source (49 recovered), not enumerated from a running server. Tool-poisoning, Unicode-smuggling, capability and toxic-flow analysis ran on this inferred surface, but a mis-parsed registration could be missed or mis-attributed, so tool-derived findings are capped below “confirmed”. To grade the real runtime surface, scan the running server: --command "npx -y <package>".
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.
| Version | Score | Findings | Engine | Scanned |
|---|---|---|---|---|
v0.5.0 latest |
A 95/100 | 0 | 1.9.0 | 2026-07-23 |
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.
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 cura-mcp --online --registry pypiMore in Developer Tools
Security scan results for the 1stay MCP server.
Security scan results for the Adguard Home MCP server.
Security scan results for the Ado Browser MCP server.
Security scan results for the Adobe Experience Dev MCP server.
Security scan results for the Aemet MCP server.
Security scan results for the Affinity Mcp Bridge MCP server.