Zenable cleans up sloppy AI code and prevents vulnerabilities with deterministic guardrails
Inferred from the transports this listing declares (streamable-http). A client not listed here hasn’t been ruled out — it just isn’t something Forge can confirm.
Verification confirms publisher identity (repo ownership), not code safety. The security scan covers known CVEs and suspicious install scripts.
The endpoint answers, but requires the vendor's own credentials before it will list its tools. Forge holds no credentials for third-party servers, so the surface is not observable from here. This is a normal state for a commercial hosted server, not a finding against it.
https://mcp.zenable.app/auth requiredZenable cleans up sloppy AI code and prevents vulnerabilities with deterministic guardrails
This entry publishes no npm package, so Forge has no dependency tree for it. That is a gap in coverage — not a statement that it has no dependencies.