@httttt/mcp-npx-fetch-1
A CLI tool for fetching and processing content using the Model Context Protocol
This report shows the evidence for @httttt/mcp-npx-fetch-1@1.0.0. 1 of 2 known versions is blocked or flagged. The newest version, 0.0.1-security, is allowed. See all versions.
AI Security Review
scanned 2mo ago · by lpm-firewall-aiSource inspection confirms a package script retrieves and executes an unauditable remote payload. The normal MCP server code does not justify that behavior.
Decision evidence
public snapshot- Undocumented npm start downloads a remote file, marks it executable, and runs it.
- The remote executable is unrelated to the documented MCP fetch-server workflow.
- README documents CLI/npx use but not the start-script payload.
- The published bin only starts a stdio MCP server.
- Fetcher network calls are user-supplied MCP tool requests.
Source & flagged code
2 flagged · loading sourceUndocumented npm start downloads a remote file, marks it executable, and runs it.
package.jsonView on unpkg · L19The remote executable is unrelated to the documented MCP fetch-server workflow.
README.mdView on unpkg · L108Findings
Affected versions and remediation
This report applies to @httttt/mcp-npx-fetch-1@1.0.0.
The versions list below shows the verdict for each recorded version.
- Avoid installing @httttt/mcp-npx-fetch-1@1.0.0. Remove it from direct dependencies and check your lockfile for transitive copies.
- Choose an independently verified alternative or release. This report does not establish that other versions are safe.
- If this version ran, investigate the affected machine and build environment. Rotate credentials it could access and rebuild from a trusted environment.
Evidence last updated: .
Think this verdict is wrong? Dispute it on GitHub or read how reports are produced.