Is I14y MCP server safe?
Yes, with the usual care.
Safe to use. Minor gaps such as a missing repository or slower maintenance.
No critical or high findings in the latest scan.
How I14y compares
Against every graded MCP server, from our own scans and uptime checks. Updated after each scan run.
- Safety score
- 77/100
- higher than 50% of 48,255 servers
- Tools that change things
- 8%
- typical: 0%. Fewer write tools means less an agent can break
What its tools let an agent do: 12 read · 1 change
Release history: 2 versions in the registry since 2026-08-03, latest 2026-09-19, typically one every 47 days.
Public scan report
scanner v0.1.10 · 2026-10-14 · same rubric, same numbers if you re-run it
2 medium
- Code scan33 source files scanned15/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 18 days ago15/15
- Maintainer identityregistry namespace matches repository owner; GitHub account older than a year8/10
Findings (2)
- mediumsubprocess with shell=True
exec.shell-truei14y_mcp-0.4.0/audits/2026-07-23T151450-Z-i14y-mcp/raw/sec.json: …: [ "grep over src/ for os.system|shell=True|eval(|exec(|os.popen|subprocess|child_p…
- mediumeval / new Function used
exec.evali14y_mcp-0.4.0/audits/2026-07-23T151450-Z-i14y-mcp/raw/sec.json: …grep over src/ for os.system|shell=True|eval(|exec(|os.popen|subprocess|child_process…
Overall 77/100. Components that don't apply are left out of the denominator. Any critical finding is an F.RubricAppeal a findingJSON