mcp-scraper@0.102.3
Authenticated public client for hosted MCP Scraper tools and REST APIs
AI Security Review
scanned 2d ago · by lpm-firewall-aiThe flagged API key is sent to the package’s own service, but artifact recording also sends the local artifact path without disclosure in the workflow command description. This is suspicious runtime telemetry rather than clear credential theft.
Decision evidence
public snapshot- The CLI sends a POST to `/memory/mcp-call` using `MCP_SCRAPER_API_KEY` and the configured base URL, which defaults to `https://mcpscraper.dev`.
- The request payload includes an artifact title, a content field containing the local artifact path, and a workflow source identifier.
- Artifact creation invokes this upload automatically through the workflow artifact `remember` method.
- The credential sent is the package’s own API key and the destination defaults to the package’s service.
- The upload contains artifact metadata and a local path, not the artifact file contents.
- The upload is reached when a user runs a workflow; no install or import-time upload was identified.
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.3.
See all versions of mcp-scraper for other recorded verdicts.
- Review the evidence and your use of mcp-scraper@0.102.3 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.