Hyperpanes MCP Server
hyperpanes-mcp
npm
v0.1.13
Published by eyalm321 — 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 hyperpanes (Electron terminal-workspace app) — compose, validate, and launch workspace layouts, and drive a running instance (read/spawn/layout panes, stream output, guarded input)
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.
Findings 12
high Tool "open_pane" exposes command/code executionMTC-CAP-001
Tool "open_pane" 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 open_pane
high Tool "spawn_workers" exposes command/code executionMTC-CAP-001
Tool "spawn_workers" appears to run shell commands or evaluate code (keyword "spawn" in tool name). 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 spawn_workers
high Shell/command execution in server code (dist/backlog/sources.js)MTC-SRC-002
In the server's implementation (`dist/backlog/sources.js:13`): 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: { execFile } from 'node:child_process'; import { promisify } from 'node:util'; const execFileP = promisify(execFile); co
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/backlog/sources.js
high Shell/command execution in server code (dist/launch.js)MTC-SRC-002
In the server's implementation (`dist/launch.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: rt { spawn } from 'node:child_process'; import { mkdtempSync, writeFileSync } from 'node:fs'; import { tmpdir } from 'no
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/launch.js
high Shell/command execution in server code (dist/worker-pool/git.js)MTC-SRC-002
In the server's implementation (`dist/worker-pool/git.js:7`): 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: { execFile } from 'node:child_process'; import { promisify } from 'node:util'; const execFileP = promisify(execFile); ex
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/worker-pool/git.js
high Shell/command execution in server code (dist/worker-pool/review.js)MTC-SRC-002
In the server's implementation (`dist/worker-pool/review.js:20`): 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 { Git } from './git.js'; /** Default review budget if the controller does
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/worker-pool/review.js
high Shell/command execution in server code (dist/worker-pool/worker.js)MTC-SRC-002
In the server's implementation (`dist/worker-pool/worker.js:23`): 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 { readFileSync, writeFileSync, existsSync, rmSync } from 'node:fs'; impor
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/worker-pool/worker.js
medium Untrusted input can drive an external actionMTC-FLOW-005
Untrusted-input tools ([read_pane, read_messages, send_message, get_task]) co-exist with external-action tools ([open_pane, spawn_workers, send_message]). A prompt injection could cause unwanted external actions, though no direct sensitive-data leak path was found.
Evidence: untrusted [read_pane, read_messages, send_message, get_task] → sinks [open_pane, spawn_workers, send_message]
Fix: Require confirmation for state-changing/egress actions triggered after processing untrusted content.
Location: flow read_pane → open_pane
medium Unconstrained command parameter "command" on "open_pane"MTC-CAP-006
Tool "open_pane" 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 open_pane · inputSchema.properties.command
medium Unconstrained command parameter "shell" on "open_pane"MTC-CAP-006
Tool "open_pane" takes a command-shaped parameter "shell" 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 open_pane · inputSchema.properties.shell
low Mutating tool "open_pane" declares no destructiveHintMTC-CAP-005
Tool "open_pane" 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 open_pane
low Mutating tool "spawn_workers" declares no destructiveHintMTC-CAP-005
Tool "spawn_workers" 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 spawn_workers
Tools 45
Each tool and what it can reach — statically extracted from the published source.
send_messageingests untrusted inputnetwork egressget_taskingests untrusted inputopen_paneruns code / shellread_messagesingests untrusted inputread_paneingests untrusted inputspawn_workersruns code / shellack_taskno sensitive capabilityadd_projectno sensitive capabilitybroadcast_subtreeno sensitive capabilitybuild_workspaceno sensitive capability
Show 35 more tools ↓
claim_taskno sensitive capabilitycontrol_statusno sensitive capabilityenqueue_taskno sensitive capabilityextend_taskno sensitive capabilitylaunch_workspaceno sensitive capabilitylist_layoutsno sensitive capabilitylist_panesno sensitive capabilitylist_projectsno sensitive capabilitylist_queuesno sensitive capabilitylist_tasksno sensitive capabilitylock_paneno sensitive capabilitymint_tokenno sensitive capabilitynack_taskno sensitive capabilityopen_tabno sensitive capabilityprompt_paneno sensitive capabilitypurge_queueno sensitive capabilityqueue_promptno sensitive capabilityrecolor_paneno sensitive capabilityrecolor_projectno sensitive capabilityremove_projectno sensitive capabilityrename_paneno sensitive capabilityrename_projectno sensitive capabilityrestart_appno sensitive capabilityrestart_paneno sensitive capabilitysend_inputno sensitive capabilitysend_keysno sensitive capabilitysend_to_parentno sensitive capabilityset_layoutno sensitive capabilityset_metano sensitive capabilityset_speechno sensitive capabilityset_talkno sensitive capabilitystop_speechno sensitive capabilityunlock_paneno sensitive capabilityvalidate_workspaceno sensitive capabilitywhoamino sensitive capability
Toxic flows 1
Cross-tool combinations that form a data-exfiltration primitive (untrusted input → sensitive source → external sink).
What this scan could not see
- Tools were statically extracted from the published source (45 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 3
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.13 latest |
A 93/100 | 12 | 1.13.0 | 2026-09-09 |
v0.1.12 |
A 93/100 | 12 | 1.12.1 | 2026-07-31 |
v0.1.10 |
A 93/100 | 13 | 1.9.0 | 2026-07-24 |
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 hyperpanes-mcp --onlineMore 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.