Is Flyto Indexer 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 Flyto Indexer compares
Against every graded MCP server, from our own scans and uptime checks. Updated after each scan run.
- Safety score
- 71/100
- higher than 36% of 48,255 servers
Public scan report
scanner v0.1.10 · 2026-09-28 · same rubric, same numbers if you re-run it
2 medium
- Code scan43 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 1 days ago15/15
- Maintainer identitynamespace and repository owner differ4/10
Findings (2)
- mediumsubprocess with shell=True
exec.shell-trueflyto_indexer-1.0.2/src/analyzer/security.py: …^)]*shell\s*=\s*True', "subprocess with shell=True", "Command injection risk"), (…
- mediumeval / new Function used
exec.evalflyto_indexer-1.0.2/src/analyzer/security.py: …?<![.\w])eval\s*\(\s*["\']?[a-zA-Z_]', "eval()", "Arbitrary code execution risk"), …
Overall 71/100. Components that don't apply are left out of the denominator. Any critical finding is an F.RubricAppeal a findingJSON
