Is @yawlabs/electron-mcp safe?
Electron MCP server: IPC scaffolding, security audits, CSP and fuses config, build-error diagnosis, and version-migration checklists
If an AI agent using this server were tricked, the damage it could do through this server is limited.
Why: reads files but does not change them.
What it can do
- Starts other programs
- Reads files
How to use it safely
- ✓ It starts another program (often a browser for sign-in, or a bundled binary). Install it only from the official package.
- ✓ Only give it the folders it needs; files it reads can end up in the AI’s context.
- ✓ Pin the version (below) so an update can't change what it does without you noticing.
Code patterns worth reviewing
Automated pattern matches in the published package. Some are expected for this kind of server, and some may be false positives — they are pointers for review, not confirmed vulnerabilities.
Command injection risk
The agent appears to pass input into a shell or command execution path.
bin/electron-mcp.mjs:14
Install it pinned
{
"mcpServers": {
"electron": {
"command": "npx",
"args": ["-y", "@yawlabs/electron-mcp@1.7.1"]
}
}
}Check your whole MCP setup
Agent Verify checks the servers in your Claude, Cursor and VS Code config — including whole-drive access and keys stored in plain text.
Maintain @yawlabs/electron-mcp?
Show users you've thought about access: add the badge below. If something here is wrong or you've released a fix, ask for a re-scan — we update pages on request.
[](https://aimodularity.com/agentverify/mcp/yawlabs-electron-mcp/)
Agent Verify reads the package published on npm as text — it is never installed or run. Ratings describe capability, not intent, and are an automated, evidence-based check, not a guarantee. Scanner 2.0.0.