🌐 Deploy HTML content to EdgeOne Pages
PassAudited by ClawScan on May 1, 2026.
Overview
This skill appears to do what it says—publish supplied HTML to a public EdgeOne Pages URL—but users should verify the npm helper and avoid deploying private content.
This skill is reasonable for publishing HTML to EdgeOne Pages. Before installing, verify the mcporter npm package, and only use the skill with content you intentionally want to publish publicly because the artifacts do not describe retention or deletion controls.
Findings (2)
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.
Installing or running the helper uses code from the npm ecosystem, so the user is trusting that package to handle the deployment command safely.
The skill depends on an external npm package, and the artifacts do not show a pinned version or additional provenance. This is aligned with the skill's CLI-based deployment purpose but is worth user verification.
node | package: mcporter | creates binaries: mcporter
Verify the mcporter package source and version before installing or running it, especially in sensitive environments.
Content supplied to the skill may be transmitted to a remote service and made publicly accessible.
The command sends provided content, including a selected local file in the example, to a remote MCP deployment endpoint that returns a public URL. This matches the stated purpose but creates a clear external data-sharing boundary.
npx -y mcporter call mcp-on-edge.edgeone.app/mcp-server.deploy-html value="$(cat index.html)"
Only deploy files or HTML that you are comfortable making public, and check the provider's retention and deletion options if that matters.