mcp-scraper@0.102.1
Authenticated public client for hosted MCP Scraper tools and REST APIs
AI Security Review
scanned 12d ago · by lpm-firewall-aiThe scanner's credential, network, and process-execution signals correspond to authenticated CLI features: workflow reporting transmits artifact metadata, and configuration changes require an explicit apply action. The inspected source does not establish hidden credential transfer or command-output exfiltration.
Decision evidence
public snapshot- The manifest exposes the flagged file as the mcp-scraper-cli executable.
- The inspected Commander dependency provides a standard ESM export wrapper; its listed scripts are development checks.
- Workflow artifact reporting sends the artifact path and metadata to the memory endpoint, not the artifact contents.
- The memory endpoint defaults to mcpscraper.dev; the API helper also defaults to that service and accepts an explicitly configured endpoint.
- Agent configuration changes require --apply, are limited to Claude Code, and require an API key.
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.1.
See all versions of mcp-scraper for other recorded verdicts.
- Review the evidence and your use of mcp-scraper@0.102.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.