@okostream/mcp@0.16.0
Control OKO Stream webinars from Claude, Codex, and other MCP clients.
AI Security Review
scanned 1mo ago · by lpm-firewall-aiStatic inspection found no lifecycle hook or concrete malicious behavior. Network authentication is tied to an explicit OKO API key and the server uses stdio.
Decision evidence
public snapshot- The manifest exposes dist/server.js as its executable entrypoint and has no install lifecycle hook.
- The server requires an explicitly configured OKO_API_KEY before sending an authentication request.
- The default authentication endpoint is an OKO Firebase Cloud Function.
- Local image reads are disabled unless explicit trusted roots are configured.
- The entrypoint registers MCP tools over stdio.
Source & flagged code
6 flaggedBrowser source reuses an authenticated session to collect identity data and mutate account settings while reporting externally.
dist/server.jsView on unpkg · L1232A bounded semantic-analysis stage reached its safety limit; remaining detectors completed, but this package requires AI review.
dist/server.jsView on unpkgPackage contains source files above the normal full-analysis size ceiling.
Findings
Affected versions and remediation
This report applies to @okostream/mcp@0.16.0.
See all versions of @okostream/mcp for other recorded verdicts.
- Review the evidence and your use of @okostream/mcp@0.16.0 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.