Is CLIO Seismic 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.
Public scan report
scanner v0.1.9 · 2026-09-27 · same rubric, same numbers if you re-run it
2 medium
- Code scan299 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 11 days ago15/15
- Maintainer identityregistry namespace matches repository owner; GitHub account older than a year9/10
Findings (2)
- mediumeval / new Function used
exec.evalclio_kit-2.2.3/clio-kit-mcp-servers/hdf5/src/hdf5_mcp/server.py: …c: try: slice_obj = eval(f"np.s_[{slice_spec}]") except E… - mediumsubprocess with shell=True
exec.shell-trueclio_kit-2.2.3/clio-kit-mcp-servers/node-hardware/src/node_hardware_mcp/capabilities/remote_node_info.py: …y: result = subprocess.run(cmd, shell=True, capture_output=True, text=True, timeou…
Overall 78/100. Components that don't apply are left out of the denominator. Any critical finding is an F.RubricAppeal a findingJSON