Is Office Oxide MCP server safe?
Not recommended.
Hidden from default browsing. Significant findings or unreachable.
What to know before installing
- highShell command built from a string (injection risk)
How Office Oxide compares
Against every graded MCP server, from our own scans and uptime checks. Updated after each scan run.
- Safety score
- 49/100
- higher than 9% of 48,255 servers
Public scan report
scanner v0.1.9 · 2026-09-26 · same rubric, same numbers if you re-run it
1 high2 medium
- Code scan4 source files scanned3/25
- –Live reliabilityno gateway calls yet and no remote to proben/a
- –Tool poisoningtools not inspected (local package is not executed); not countedn/a
- Auth qualitylocal package, no credentials required12/15
- Maintenancelast push 103 days ago8/15
- Maintainer identityregistry namespace matches repository owner; GitHub account older than a year9/10
Findings (3)
- mediumnpm install lifecycle script present
install.script - highShell command built from a string (injection risk)
exec.shell-concatinstall.js: …if (platform() !== 'win32') { execSync(`chmod +x "${dest}"`); } resolve(); … - mediumnpm install lifecycle script present
install.scriptpackage.json: …-mcp": "run.js" }, "scripts": { "postinstall": "node install.js" }, "repository": …
Overall 49/100. Components that don't apply are left out of the denominator. Any critical finding is an F.RubricAppeal a findingJSON