Nonead Universal Robots MCP Server
nonead-universal-robots-mcp
PyPI
v0.1.1
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.
Nonead Universal Robots MCP
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 − 6.3 = 94. What the published surface and source actually contain:
| Points | What was found | Category |
|---|---|---|
| −6.3 | Unsafe deserialization MTC-SRC-007 | permissions |
2. Client adoption risk — 94 − 2 = 92. 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 |
|---|---|
| −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 1
medium Unsafe deserialization (URBasic/advanced_data_recorder.py)MTC-SRC-007
In the server's implementation (`URBasic/advanced_data_recorder.py:730`): Deserializing untrusted data with these APIs can execute arbitrary code (a well-known RCE gadget class). This is read from the code itself — not from the tool description — so a poisoned server cannot hide it behind honest-looking metadata.
Evidence: file_records = pickle.loads(zlib.decompress(compressed_data)) else: with op
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 URBasic/advanced_data_recorder.py
Tools 39
Each tool and what it can reach — statically extracted from the published source.
analyze_robot_datano sensitive capabilitycompare_robots_performanceno sensitive capabilityconnect_urno sensitive capabilitycreate_collaborative_taskno sensitive capabilitydisconnect_urno sensitive capabilitydraw_circleno sensitive capabilitydraw_rectangleno sensitive capabilitydraw_squareno sensitive capabilityexecute_collaborative_taskno sensitive capabilitygenerate_bezier_pathno sensitive capability
Show 29 more tools ↓
generate_robot_reportno sensitive capabilityget_actual_joint_currentno sensitive capabilityget_actual_joint_poseno sensitive capabilityget_actual_joint_voltageno sensitive capabilityget_actual_robot_currentno sensitive capabilityget_actual_robot_voltageno sensitive capabilityget_actual_tcp_poseno sensitive capabilityget_joint_temperaturesno sensitive capabilityget_output_bit_registerno sensitive capabilityget_output_double_registerno sensitive capabilityget_output_int_registerno sensitive capabilityget_program_stateno sensitive capabilityget_programsno sensitive capabilityget_robot_modeno sensitive capabilityget_robot_modelno sensitive capabilityget_safety_modeno sensitive capabilityget_serial_numberno sensitive capabilityget_timeno sensitive capabilityget_ur_software_versionno sensitive capabilitymovejno sensitive capabilitymovelno sensitive capabilitymovel_xno sensitive capabilitymovel_yno sensitive capabilitymovel_zno sensitive capabilityoptimize_trajectoryno sensitive capabilitysend_program_scriptno sensitive capabilitysetup_multi_robot_coordinationno sensitive capabilitystart_data_recordingno sensitive capabilitystop_data_recordingno sensitive capability
What this scan could not see
- Tools were statically extracted from the published source (39 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.1.1 latest |
A 92/100 | 1 | 1.13.0 | 2026-08-25 |
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 nonead-universal-robots-mcp --online --registry pypiMore in Developer Tools
Hotel booking MCP server — 300K+ properties, real confirmation numbers, loyalty programs. Builders monetize every booking via Stripe Connect. The first MCP server that completes real hotel reservations inside AI conversations.
Manage AdGuard Home through AI assistants
Read-only Azure DevOps for MCP clients using only your existing browser session — no PAT, no Azure CLI. Browse work items, pull requests, comments, attachments and Artifacts feeds across every project, repo and feed you can access.
MCP server for Adobe Experience Manager Assets integration development
Servidor MCP para el tiempo oficial de España (API pública OpenData de AEMET). Predicción, observación y avisos como herramientas MCP tipadas.
A standalone MCP stdio bridge for Affinity by Canva's local MCP SSE server.