mcp-scraper@0.102.6
Authenticated public client for hosted MCP Scraper tools and REST APIs
AI Security Review
scanned 4d ago · by lpm-firewall-aiThe CLI sends local artifact paths and workflow metadata to the vendor’s service whenever it records workflow artifacts. This is identifying runtime telemetry without a clear disclosure or opt-out, so warn rather than block; the inspected payload does not include artifact contents or unrelated credentials.
Decision evidence
public snapshot- When the sink runs, the CLI POSTs JSON to `/memory/mcp-call` with the API key in the `x-api-key` header.
- Artifact handling sends a workflow title, the artifact’s local path, and workflow/run identifiers to that sink.
- The sink is called while an explicit CLI workflow action runs; no install hook is configured.
- The default destination is the package’s own service, and the API key is the package’s own key.
- The payload includes the artifact path and metadata, not the artifact’s file contents.
- The package has no lifecycle scripts; the flagged behavior is runtime CLI functionality.
Source & flagged code
9 flaggedPackage source references child process execution.
dist/bin/mcp-scraper-cli.jsView on unpkg · L1A single source file combines environment access, network access, and code or shell execution; review context before blocking.
dist/bin/mcp-scraper-cli.jsView on unpkg · L1Findings
Affected versions and remediation
This report applies to mcp-scraper@0.102.6.
See all versions of mcp-scraper for other recorded verdicts.
- Review the evidence and your use of mcp-scraper@0.102.6 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.