Is PlanExe MCP server safe?
Not recommended.
Hidden from default browsing. Significant findings or unreachable.
What to know before installing
- highRemote endpoint did not respond — TypeError: fetch failed
How PlanExe compares
Against every graded MCP server, from our own scans and uptime checks. Updated after each scan run.
- Safety score
- 50/100
- higher than 9% of 48,114 servers
- Tools that change things
- 18%
- typical: 0%. Fewer write tools means less an agent can break
- Uptime
- 0%
- of our recent checks; the typical remote server answers 100%
What its tools let an agent do: 9 read · 1 change · 1 send or post
Public scan report
scanner v0.1.10 · 2026-10-14 · same rubric, same numbers if you re-run it
1 high
- –Code scanremote-only server, no package to scann/a
- Live reliabilityremote unreachable: TypeError: fetch failed0/20
- –Tool poisoningtools not inspected (endpoint requires auth); not countedn/a
- Auth qualityAPI key sent as a header8/15
- Maintenancelast push 3 days ago15/15
- Maintainer identityregistry namespace matches repository owner7/10
Findings (1)
- highRemote endpoint did not respond
reliability.unreachableTypeError: fetch failed
Overall 50/100. Components that don't apply are left out of the denominator. Any critical finding is an F.RubricAppeal a findingJSON