suspicious.env_credential_access
- Location
- src/index.ts:580
- Finding
- Environment variable access combined with network send.
AdvisoryAudited by Static analysis on May 10, 2026.
Detected: suspicious.env_credential_access
Artifact-based informational review of SKILL.md, metadata, install specs, static scan signals, and capability signals. ClawScan does not execute the skill or run runtime probes.
If an agent or user supplies an unexpected URL, the server may attempt to fetch it from the machine running the MCP server.
The tool caller controls the URL that the server fetches. This is expected for inspecting .spkg packages, but it should be treated as a network-fetch capability.
url: z.string().describe("Direct URL to a .spkg file") ... return await fetchSubstream(url, { signal: controller.signal });Use trusted direct .spkg URLs, preferably from spkg.io or the intended registry, and avoid exposing this tool to untrusted callers.
Anyone able to connect to the MCP endpoint could potentially invoke the search and package-inspection tools.
The skill can expose MCP tools over an HTTP/SSE endpoint. This is documented and purpose-aligned, but the artifacts do not describe authentication or access controls.
The SSE transport (`--http` / `--http-only`) starts a local HTTP server on port 3849 (configurable via `MCP_HTTP_PORT` env var).
Keep the endpoint bound to localhost or protect it with network controls if used in a remote deployment.
The code actually executed by npx comes from the npm package available at install time.
The documented setup runs an npm package through npx. This is normal for a Node MCP server, but it depends on the published npm package and its dependencies matching the reviewed source.
npx substreams-search-mcp
Verify the npm package publisher and consider pinning a specific version before use.