mcp-scraper@0.99.0
Authenticated public client for hosted MCP Scraper tools and REST APIs
AI Security Review
scanned 19d ago · by lpm-firewall-aiThe inspected source ties authenticated requests to a configurable API client and limits configuration changes to an explicit Claude Code apply command. Scanner signals do not establish automatic credential or command-output exfiltration, and the manifest has no lifecycle hooks.
Decision evidence
public snapshot- package.json lists commander as the sole runtime dependency and declares no lifecycle hook.
- The CLI takes an API key from an explicit option or environment variable and allows an API URL override, defaulting to mcpscraper.dev.
- The CLI sends that key to the selected API URL for the requested API call.
- Applying agent configuration requires the explicit --apply option, is limited to Claude Code, and checks for an API key.
- The CLI parses command-line input to run its commands; the inspected source does not establish an automatic credential export or command-output upload.
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.99.0.
See all versions of mcp-scraper for other recorded verdicts.
- Review the evidence and your use of mcp-scraper@0.99.0 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.