mcp-scraper@0.102.5
Authenticated public client for hosted MCP Scraper tools and REST APIs
AI Security Review
scanned 2d ago · by lpm-firewall-aiThe CLI silently sends local artifact paths to the package’s service whenever a workflow records output. This is undisclosed runtime telemetry carrying local path details, so it warrants a warning.
Decision evidence
public snapshot- The CLI posts to `https://mcpscraper.dev/memory/mcp-call` using `MCP_SCRAPER_API_KEY`, with a `libraryIngestTool` payload.
- Whenever the CLI records a workflow artifact, it invokes that sink with the artifact’s local path as content, plus its title and workflow identifiers.
- The network request uses the package’s own service and its own API key; no unrelated host or other service credential appears in this flow.
- Workflow commands are user-run, and the sink sends artifact path metadata rather than the artifact’s file contents.
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.5.
See all versions of mcp-scraper for other recorded verdicts.
- Review the evidence and your use of mcp-scraper@0.102.5 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.