@caelo-cms/mcp-server@0.10.30
MCP servers for Caelo CMS: `caelo_chat` (talk to Caelo's own AI) and the admin-scoped Power-MCP (the full chat-runner tool catalogue, driven by your own agent). Lets Claude Code (or any MCP-aware client) drive a Caelo install from outside the browser.
AI Security Review
scanned 8d ago · by lpm-firewall-aiSource inspection found no install-time attack or covert credential transfer. The flagged signing flow is operator-configured for Google IAP, and agent context files are written only by the explicit export command.
Decision evidence
public snapshot- package.json exposes the dist entrypoints and declares only a prepublishOnly compiler build; it has no install lifecycle hook.
- IAP signing is inactive unless the operator configures CAELO_IAP_SERVICE_ACCOUNT and CAELO_ADMIN_URL.
- When enabled, the code uses Google IAM signJwt to create a token whose audience is derived from the configured admin URL.
- MCP requests send the token and optional IAP header to opts.adminUrl; no package-selected third-party recipient appears in this flow.
- The agent context export runs only for the explicit export command and writes files under the chosen or current directory; skill slugs are checked before writing.
Source & flagged code
3 flagged · loading sourceSource sends credentials or rich application records to a package-controlled external receiver enabled by default.
dist/ingress-auth.jsView on unpkg · L28Findings
Affected versions and remediation
This report applies to @caelo-cms/mcp-server@0.10.30.
See all versions of @caelo-cms/mcp-server for other recorded verdicts.
- Review the evidence and your use of @caelo-cms/mcp-server@0.10.30 before allowing it. Restrict the permissions described in this report.
- Choose an independently verified alternative or release. This report does not establish that other versions are safe.
Evidence last updated: .
Think this verdict is wrong? Dispute it on GitHub or read how reports are produced.