@okostream/mcp@0.10.0
Control OKO Stream webinars from Claude, Codex, and other MCP clients.
AI Security Review
scanned 1mo ago · by lpm-firewall-aiThe network and environment signals support the package’s authenticated MCP functionality, and the flagged Firebase value is client configuration. Static inspection found no concrete malicious behavior warranting a warning or block.
Decision evidence
public snapshot- package.json has no registry-install lifecycle hooks or runtime self-dependency; its entrypoint runs an MCP server.
- dist/firebaseDefaults.js defines OKO Firebase project configuration, consumed by Firebase client initialization rather than privileged secret handling.
- Authentication sends the explicitly configured OKO_API_KEY to the default OKO exchange service or a caller-configured exchange URL.
- Image uploads require an authenticated scope and confirmation; local reads enforce configured directory boundaries.
- Remote image fetching rejects non-public addresses and pins the validated address.
Source & flagged code
4 flaggedPackage contains a high-severity secret pattern.
dist/firebaseDefaults.jsView on unpkg · L3dist/firebaseDefaults.js defines OKO Firebase project configuration, consumed by Firebase client initialization rather than privileged secret handling.
dist/firebaseDefaults.jsView on unpkg · L4Findings
Affected versions and remediation
This report applies to @okostream/mcp@0.10.0.
See all versions of @okostream/mcp for other recorded verdicts.
- Review the evidence and your use of @okostream/mcp@0.10.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.