Electron (iamvinitk) MCP Server
@iamvinitk/electron-mcp
npm
v0.1.0
Published by @iamvinitk — no publish provenance and no public repository, so the publisher could not be verified and the source cannot be independently located.
MCP server for interacting with and debugging an Electron application via Chrome DevTools Protocol + Node Inspector.
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 − 8 = 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 |
|---|---|
| −6 | capability blast radius (high) — 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 1
high Shell/command execution in server code (build/electron.js)MTC-SRC-002
In the server's implementation (`build/electron.js:22`): 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 net from "node:net"; import path from "node:path"; import fs from "node:f
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 build/electron.js
Tools 20
Each tool and what it can reach — statically extracted from the published source.
attach_appno sensitive capabilityclear_logsno sensitive capabilityenable_ipc_loggingno sensitive capabilityevaluateno sensitive capabilityget_app_pathsno sensitive capabilityget_console_messagesno sensitive capabilityget_ipc_logno sensitive capabilityget_main_logsno sensitive capabilityget_network_requestsno sensitive capabilityinvoke_electron_apino sensitive capability
Show 10 more tools ↓
launch_appno sensitive capabilitylaunch_via_npmno sensitive capabilitylist_appsno sensitive capabilitylist_electron_api_methodsno sensitive capabilitylist_windowsno sensitive capabilitynavigateno sensitive capabilityping_inspectorno sensitive capabilityread_user_data_fileno sensitive capabilityscreenshotno sensitive capabilitystop_appno sensitive capability
What this scan could not see
- Tools were statically extracted from the published source (20 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.0 latest |
A 92/100 | 1 | 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.
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 @iamvinitk/electron-mcp --onlineOther implementations of Electron 7
Independent packages implementing the same tool, scanned with the same engine. Compare all 8 side by side →
Embedded MCP server for Electron apps.
MCP server for testing Electron applications using Playwright
MCP server for Electron application automation and management. See MCP_USAGE_GUIDE.md for proper argument structure examples.
MCP server for Electron application automation and management. See MCP_USAGE_GUIDE.md for proper argument structure examples.
MCP server for Electron app automation via CDP. Agent-browser style compact refs. Use with any Electron app running --remote-debugging-port=9222.
Electron.js MCP server — IPC scaffolding, security auditing, build tooling, and development intelligence for AI assistants
More 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.