mcp-scraper@0.100.2
Authenticated public client for hosted MCP Scraper tools and REST APIs
AI Security Review
scanned 14d ago · by lpm-firewall-aiSource inspection found no lifecycle hook or confirmed attack behavior. The flagged credential and network operations are API-client behavior directed to the configured service endpoint, with a package-aligned default.
Decision evidence
public snapshot- package.json defines the client entrypoints and commander dependency; it has no lifecycle scripts.
- The CLI sends its API key with API requests to the configured API URL, which defaults to mcpscraper.dev.
- The library client validates its configured HTTP(S) endpoint and sends the API key with MCP requests there.
- The CLI’s memory-ingest helper sends artifact metadata to the configured MCP Scraper base URL.
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.100.2.
See all versions of mcp-scraper for other recorded verdicts.
- Review the evidence and your use of mcp-scraper@0.100.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.