← Registry

Cloud Services

deed.page

Hosts and manages static websites by publishing, updating, retrieving, listing, and deleting live site slugs.

1 endpoint7 known toolsFirst detected October 1, 2026Last detected October 8, 2026

ENDPOINT 1

https://deed.page/mcp

No auth detected

MCP server metadata

Name
deed.page
Version
1.1.0
Capabilities
tools
Server instructions

deed.page publishes static files to a permanent public HTTPS URL. No account, email code, or claim link. Flow: call publish_site with a files map and a slug. The first call without a token returns "token" once: keep it and pass it (Authorization: Bearer header or the "token" argument) to update_site, delete_site, list_sites. There is no way to recover a lost token. Slugs must already match ^[a-z0-9](?:[a-z0-9-]{0,61}[a-z0-9])?$ (lowercase, 1-63, no leading or trailing hyphen). They are not rewritten. Reserved names (www, api, hello, my-page, and other docs examples) return an error. File paths are stored exactly as given. merge=true overwrites only the paths you send and leaves every other path alone. Sites never expire unless ttl_seconds is set. Up to ~4 MB per call; for bigger sites call update_site again with merge=true to add files. Custom domains are not supported. Previous file sets are not stored; publish the earlier files again to undo a change.

Known tools 7

publish_site

Use this when the user wants something put online, shared as a link, or hosted.

Inferred read-only
update_site

Use this to replace (or with merge=true, add to) the files of a slug you already own.

Inferred read-only
get_site

Use this to check whether a slug is live and read its URL, version, size, and timestamps.

Inferred read-only
list_sites

Use this to list every live site owned by your token, with URLs and versions.

Inferred read-only
delete_site

Use this only when the user explicitly asks to take a site down.

Inferred read-only
whoami

Use this to read your plan, limits, and how many sites your token owns.

Inferred read-only
get_upgrade_link

Use this only when the user asks for higher limits.

Inferred read-only

CONNECT WITH APPROVAL

Client installation

Review this server and its permissions before adding it. Secret placeholders must be set locally.

Codex

~/.codex/config.toml

[mcp_servers.deed-page]
url = "https://deed.page/mcp"
enabled = true
Claude Code

.mcp.json

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

Settings → Connectors → Add custom connector

Name: deed-page
Remote MCP URL: https://deed.page/mcp

Add this remote URL as a custom connector in Claude Desktop. Availability depends on the user plan and workspace policy.

Cursor

.cursor/mcp.json

{
  "mcpServers": {
    "deed-page": {
      "url": "https://deed.page/mcp"
    }
  }
}
Visual Studio Code

.vscode/mcp.json

Add to Visual Studio Code
{
  "servers": {
    "deed-page": {
      "type": "http",
      "url": "https://deed.page/mcp"
    }
  }
}
Generic MCP

Client-specific MCP configuration

{
  "name": "deed-page",
  "transport": "streamable-http",
  "url": "https://deed.page/mcp"
}
MCP Inspector

Run the official MCP Inspector locally and enter the indexed Streamable HTTP endpoint.

TRUST AND VERIFICATION EVIDENCE

Trust Data Available

BuiltWith Trust API v2 evidence for deed.page was fetched 2026-10-03T06:51:31.789Z.

Trust status Trusted

deed.page is assessed as Trusted: Domain has an established technology history spanning over a year.

Indexed

Evidence is source-attributed and does not guarantee that a third-party server is safe. Risk labels are conservative metadata heuristics.