deed.page

page.deedv1.0.0Updated Sep 29, 2026

Publish static sites to permanent URLs in one call. No account, email code, or claim link.

VerifiedStreamable HTTPWeb executableCloud & InfrastructureDeveloper Tools

Overview

AI-generated overview

Lets an assistant publish static sites to permanent public URLs in a single call, with no account or email verification.

What it does
This remote MCP server exposes a publish_site tool that takes static site content and returns a permanent public URL. The first publish returns a bearer token that can be reused to manage or update the site. No account, email code, or claim link is required.
When to use it
Use it when you want an assistant to put a small static site, demo page, or generated HTML online quickly and get a stable link back, without setting up hosting or signing up for an account.
Requirements
A remote MCP client that supports streamable HTTP. No local runtime or package is needed. Publishing works without credentials; an optional Authorization bearer token, returned by the first publish, can be supplied as a header or as a token argument.
Before you install
Published content becomes publicly reachable at a permanent URL, so do not publish secrets or private data. The Authorization bearer token is a secret that grants control over the published site; keep it out of shared logs and conversations.

Installation

In SourceWeft

  1. Open deed.page in the dashboard and add it to a workspace.
  2. 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.

Other MCP clients

Add this to your client's mcpServers config.

{
  "mcpServers": {
    "deed-page": {
      "type": "http",
      "url": "https://deed.page/mcp"
    }
  }
}

Tools

0
Tool metadata has not been indexed yet.

Version history

1
  1. v1.0.0LatestSep 29, 2026