@okostream/mcp@0.18.2
Control OKO Stream webinars from Claude, Codex, and other MCP clients.
AI Security Review
scanned 1mo ago · by lpm-firewall-aiInspected source supports a package-aligned MCP service with explicit API authentication and guarded file access. No concrete malicious chain or unresolved warning-level behavior was established.
Decision evidence
public snapshot- package.json exposes dist/server.js as the CLI and has no registry install hooks or runtime self-dependency.
- The entrypoint registers webinar tools and connects an MCP stdio transport.
- Authentication sends the explicitly configured OKO_API_KEY to the OKO exchange service by default; operators can configure the endpoint.
- Local image reads require configured trusted roots and reject paths outside them after resolving filesystem paths.
- Workspace invite claims require authentication with a write scope and explicit confirmation.
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.18.2.
See all versions of @okostream/mcp for other recorded verdicts.
- Review the evidence and your use of @okostream/mcp@0.18.2 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.