mcp-scraper@0.102.2
Authenticated public client for hosted MCP Scraper tools and REST APIs
AI Security Review
scanned 2d ago · by lpm-firewall-aiThe scanner’s credential and network hits resolve to the package’s own API key and service, while the command execution shown is used by an explicit setup command. Workflow artifact ingestion sends metadata and a local artifact path rather than the artifact contents.
Decision evidence
public snapshot- The manifest describes an authenticated client for hosted MCP Scraper tools and exposes the flagged file as a user-run CLI command, with no lifecycle scripts.
- The CLI’s memory sink sends a supplied MCP Scraper API key and library-ingest arguments to the configured MCP Scraper service.
- Workflow artifact recording sends artifact metadata and a local path to that sink; it does not send artifact contents.
- The CLI requires the MCP Scraper API key and defaults requests to mcpscraper.dev.
- The flagged CLI runs when invoked by the user; it is not a package import entry point or install hook.
- The reviewed credential flow uses the package’s own API key and service endpoint; no unrelated credential source or collector was found.
Source & flagged code
7 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.2.
See all versions of mcp-scraper for other recorded verdicts.
- Review the evidence and your use of mcp-scraper@0.102.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.