influship-api-mcp@0.20.1
The official MCP Server for the Influship API
AI Security Review
scanned 1mo ago · by lpm-firewall-aiThe package exposes an MCP API client with explicit remote or local code-execution modes, but has no install hook or hidden persistence behavior. The flagged primitives are package-aligned and tool-invoked rather than a concrete malicious chain.
Decision evidence
public snapshot- The execute tool sends submitted code and the Influship API key to a Stainless-hosted endpoint when invoked.
- The optional local mode evaluates caller-supplied code in a Deno worker.
- Startup fetches MCP instructions from a Stainless endpoint.
- The reviewed local documentation module contains embedded method data, not collection logic.
- The declared scripts are test, build, format, tsn, lint, and fix.
- The remote code-tool handler sends a POST request to its configured endpoint.
- The TypeScript source sends remote code-tool requests with POST.
- The worker evaluates the supplied code and invokes its exported run function with an SDK proxy.
- package.json has no preinstall, install, or postinstall hook.
- The executable entry point runs only when invoked as the command-line program.
- Remote calls and code evaluation are explicit MCP tool behavior, not import-time activity.
- No source showed persistence, broad file harvesting, destructive actions, or unrelated exfiltration.
Source & flagged code
12 flagged · loading sourceSource file is highly similar to a previously finalized malicious package; route for source-aware review.
instructions.jsView on unpkgPackage source references dynamic require/import behavior.
instructions.jsView on unpkg · L7Findings
Affected versions and remediation
This report applies to influship-api-mcp@0.20.1.
See all versions of influship-api-mcp for other recorded verdicts.
- Review the evidence and your use of influship-api-mcp@0.20.1 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.