@okostream/mcp@0.12.15
Control OKO Stream webinars from Claude, Codex, and other MCP clients.
AI Security Review
scanned 2mo ago · by lpm-firewall-aiNo concrete malicious install hook, exfiltration path beyond the stated OKO authentication exchange, or stealth persistence was found. The package nevertheless has significant credential-bearing MCP and destructive remote-control capability, so it should be warned rather than automatically marked clean.
Decision evidence
public snapshot- The executable MCP server loads a home-directory dotenv file at startup.
- When configured, it sends the named OKO API key to the OKO key-exchange endpoint.
- It exposes authenticated destructive webinar deletion tools, though they require explicit confirmation and scoped authorization.
- The manifest has no registry install lifecycle hook; prepublishOnly is publisher-side.
- The observed endpoint is an OKO service endpoint and the request is limited to the configured OKO API key and version.
- Deletion paths require an events:delete scope and confirmation fields.
- No package-authored child-process execution, arbitrary code loading, persistence, or broad local-file harvesting was found.
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.12.15.
See all versions of @okostream/mcp for other recorded verdicts.
- Review the evidence and your use of @okostream/mcp@0.12.15 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.