hdply

com.hdplyPublished by hdply.comOfficial publisherv1.0.0Updated Oct 24, 2026

Publish a single HTML file as a live HTTPS site in seconds. Versioned deploys, no delete tool.

VerifiedStreamable HTTPWeb executableCloud & Infrastructure

Overview

AI-generated overview

Publishes a single HTML file as a live HTTPS site, with versioned deploys and no delete tool.

What you can do
This remote MCP server lets an assistant publish one HTML file as a live HTTPS site in seconds. Deployments are versioned, so each publish creates a new version rather than overwriting history. The registry description lists no delete tool, so published sites cannot be removed through the server.
When to use it
Use it when you want an assistant to put a quick single-file HTML page online at a public HTTPS address, for example a prototype, demo, or landing page. It is less suited to multi-file sites or to workflows that need to take a published page down again.
Requirements
A remote streamable HTTP endpoint at Authentication is required: a bearer token sent in the Authorization header, described as an hdply API key obtained from the provider's settings page. Network access is needed.
Before you install
The Authorization header carries a secret API key; keep it out of logs and shared configuration. Publishing makes content publicly reachable over HTTPS, and the description notes there is no delete tool, so a published site may not be removable through this server. Review what you publish before sending it.

Installation

In SourceWeft

  1. Open hdply in the dashboard and add it to a workspace.
  2. Connect Authorization token credentials. They are stored privately and never shown on public pages.
  3. Enable the server for the chats that should use its tools.

Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.

Use with an agent

Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.

Read https://sourceweft.com/mcp/com.hdply%2Fhdply/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config.

{
  "mcpServers": {
    "hdply": {
      "type": "http",
      "url": "https://api.app.hdply.com/mcp",
      "headers": {
        "Authorization": "Bearer <YOUR_TOKEN>"
      }
    }
  }
}

Tools

0
This server asks for a credential such as an API key, so SourceWeft could not read its tools without one and has not indexed them.

Version history

1
  1. v1.0.0LatestSep 16, 2026

Score

67% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 daysRequired25 pts
  • Auth declaredRequired10 pts
  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts

    Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.

  • LicenseNot applicable

    A hosted service is used under its provider's terms, so no license is expected here. This check is left out of the percentage.