Is Slidingbox Hydrate/Dehydrate MCP server safe?
Yes, with the usual care.
Passed every safety check we run. Maintained, authenticated, reachable, clean scan.
No critical or high findings in the latest scan.
Public scan report
scanner v0.1.5 · 2026-09-19 · same rubric, same numbers if you re-run it
no findings
- Code scan3 source files scanned25/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 qualitystatic API keys via environment variables6/15
- Maintenancelast push 1 days ago15/15
- Maintainer identityregistry namespace matches repository owner; website matches verified namespace9/10
Overall 85/100. Components that don't apply are left out of the denominator. Any critical finding is an F.RubricAppeal a findingJSON
Other servers that do what Slidingbox Hydrate/Dehydrate does
- Phoenix Zero — L2 Health OraclePre-flight L2 health check using kernel-level eBPF telemetry. PASS/DEGRADED/FAIL verdict.not reviewedGrowingA
NetOps Field NotesConfig drift, CIS/PCI checks, 802.1X diagnosis, certs inside configs, topology, change pre-flight.not reviewedNewA
DoDomainConnect custom domains via AI agents: DNS pre-flight checks, hand-off connect sessions and checks.not reviewedNewB