roku-mcp
npm
v1.7.0
Published by jack1590 — 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 Roku device automation — deploy, ECP control, screenshots, debug console, and BrightScript profiler analysis
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:
| Points | Adoption-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.
Tools that read sensitive data ([query_perfetto]) and tools that can send data out ([roku_console_send]) are exposed together. An agent can move private data to the sink.
Evidence: sources [query_perfetto] → sinks [roku_console_send]
Fix: Keep secret-reading and egress capabilities on separate, separately-approved servers.
Location: flow query_perfetto → roku_console_send
Tool "roku_console_send" appears to run shell commands or evaluate code (parameter "command"). Arbitrary execution driven by model input is one of the most dangerous MCP capabilities; combined with any untrusted input it becomes RCE.
Fix: Sandbox execution, allowlist commands/arguments, and never pass model output to a shell unescaped.
Location: tool roku_console_send
In the server's implementation (`dist/stream/live.js:197`): A hardcoded outbound call to a fixed external host inside server code is a classic exfiltration/telemetry channel — especially paired with reads of local data. This is read from the code itself — not from the tool description — so a poisoned server cannot hide it behind honest-looking metadata.
Evidence: ).toString(); await axios.post(`http://${params.host}:8060/launch/dev?${qs}`); // 3. Give the channel time to bo
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/stream/live.js
Tool "roku_console_send" takes a command-shaped parameter "command" with no enum/pattern constraint. Free-form, model- or attacker-controlled arguments reaching a shell is the command-injection precondition.
Fix: Constrain the parameter (enum/pattern), or build the command from a fixed template with escaped args.
Location: tool roku_console_send · inputSchema.properties.command
Tool "roku_console_send" can mutate/egress but declares no destructiveHint. Clients that don't default to spec-safe behavior may not prompt before running it.
Fix: Declare accurate annotations, and gate destructive tools on user confirmation regardless.
Location: tool roku_console_send
Tool "query_perfetto" takes a path parameter "filePath" with no constraint. Without a canonicalize-and-contain check (not visible statically), this permits ../ traversal outside the intended root.
Fix: Resolve and verify the path stays within an allowed root; reject traversal sequences.
Location: tool query_perfetto · inputSchema.properties.filePath
Each tool and what it can reach — statically extracted from the published source.
query_perfettoreads sensitive dataroku_console_sendruns code / shellanalyze_bsprofno sensitive capabilityanalyze_perfettono sensitive capabilitybsprof_infono sensitive capabilitycompare_bsprofno sensitive capabilitycompare_perfettono sensitive capabilityroku_console_connectno sensitive capabilityroku_console_disconnectno sensitive capabilityroku_console_readno sensitive capabilityroku_create_nodeno sensitive capabilityroku_delete_dev_channelno sensitive capabilityroku_deployno sensitive capabilityroku_diagnose_streamno sensitive capabilityroku_discoverno sensitive capabilityroku_edit_nodeno sensitive capabilityroku_find_nodeno sensitive capabilityroku_focus_nodeno sensitive capabilityroku_get_focused_nodeno sensitive capabilityroku_get_valueno sensitive capabilityroku_keypressno sensitive capabilityroku_keypress_sequenceno sensitive capabilityroku_launchno sensitive capabilityroku_move_nodeno sensitive capabilityroku_observe_fieldno sensitive capabilityroku_perfetto_enableno sensitive capabilityroku_perfetto_startno sensitive capabilityroku_perfetto_stopno sensitive capabilityroku_query_active_appno sensitive capabilityroku_query_app_uino sensitive capabilityroku_query_device_infono sensitive capabilityroku_query_media_playerno sensitive capabilityroku_query_sg_nodesno sensitive capabilityroku_remove_nodeno sensitive capabilityroku_screenshotno sensitive capabilityroku_set_node_visibleno sensitive capabilityroku_sleepno sensitive capabilityroku_type_textno sensitive capabilityCross-tool combinations that form a data-exfiltration primitive (untrusted input → sensitive source → external sink).
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 |
|---|---|---|---|---|
v1.7.0 latest |
A 93/100 | 6 | 1.13.0 | 2026-09-07 |
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.
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 roku-mcp --online
Independent packages implementing the same tool, scanned with the same engine. Compare all 2 side by side →
Authenticated MCP transport with HTTP Signatures for AAuth agents
Local-first MCP server for parallel AI coding agents to claim file ownership before edits, preventing stomping on each other in the same worktree.
Agent-agnostic intercommunication system — sessions, messaging, channels, shared state, and real-time events
MCP server for AI agent task communication and delegation with diagnostic lifecycle visibility
Programmatic add/link/unlink for MCP servers across 23 AI coding agents (Claude Code, Claude Desktop, Cursor, VS Code, Codex, Gemini CLI, Zed, Cline, OpenCode, Goose, Kiro, Windsurf, and more). Functional API with dry-run support.
MCP server layer exposing agent-mesh orchestrator as an MCP agent