mcpbeat Sign in

aft.page MCP Server

by vaibhavmule Your server? Claim it
answering

aft.page is answering right now. Last checked moments ago. It exposes 5 tools. Last commit 28 Aug 2026.

Deploy HTML or dist/ to a live HTTPS URL. No account. Drop, MCP, or CLI.

Uptime history 46 hours of history
46 hours agonow
100.0%
Uptime 24h
92 of 92 checks
5
Tools
read from the server
312 ms
Response time
average over 24h
0
Stars
last commit 28 Aug 2026

What the code does

We read the source, 11 h ago · tools taken from the live server · rules 3dff92dd89df

Capabilities

What this server is able to do. For an MCP server this is often the job itself — a terminal server runs commands because that is what it is for. Listed so you know what you are plugging in, not as an accusation.

Runs an external command apps/cli/check.mjs:65, apps/cli/src/ui.js:98, qa/check.mjs:21 и ещё 4
const help = spawnSync(process.execPath, [join(root, "bin/aft.js"), "--help"], {
Sends data to a third-party sink apps/api/src/container-origin.ts:16
    return new URL(url).hostname.toLowerCase().endsWith(".trycloudflare.com");
Image runs as root apps/run-container/Dockerfile:2
# ponytail: stock image has python3 but no pip. Image install is the ceiling; runner still falls back to ensurepip/apt.
USER root
Reads files and sends them to the network apps/run-container/src/index.ts:542
        for dirpath, _, names in os.walk(p):
          feed.innerHTML = days

Is this your server and something here is wrong? Tell us — corrections are free and do not require a plan.

This code can reach further than it looks

We found places where it runs commands, builds paths or queries from values it is given. None of that is a flaw by itself — it becomes one when the code changes, and code changes quietly between releases. We re-read it on every one.

Three servers free · no card

Connect this server

Endpoint below is the one we actually reach during checks — not the one copied from a README. Last verified 0 min ago.

run in your terminal
claude mcp add aft-page --transport http https://mcp.aft.page/mcp
~/Library/Application Support/Claude/claude_desktop_config.json
{
  "mcpServers": {
    "aft-page": {
      "url": "https://mcp.aft.page/mcp"
    }
  }
}
~/.codex/config.toml
[mcp_servers.aft-page]
url = "https://mcp.aft.page/mcp"
.cursor/mcp.json
{
  "mcpServers": {
    "aft-page": {
      "url": "https://mcp.aft.page/mcp"
    }
  }
}
.vscode/mcp.json
{
  "mcpServers": {
    "aft-page": {
      "url": "https://mcp.aft.page/mcp"
    }
  }
}

Available tools 5

Read directly from the server with tools/list, grouped by what they act on. If a tool disappears, we record the date.

aft
aft_deploys
List rollback-able deploys for a slug. Needs edit_token from .aft/state.json (or the first deploy). Same history the project UI shows after claim.
aft_health
Ping the aft.page deploy API.
aft_rollback
Point the live slug at a prior deployId from aft_deploys. Same URL. Needs edit_token from .aft/state.json. Claim not required.
deploy
deploy
Publish to a live URL. Pass html (one page) OR files (built site). Plain HTML → html. Vite/React → npm run build, then files from dist/. Next static export → files from out/. Always include index.html. Never upload src/, node_modules, or .next/. First hit: preferred_slug from aft.json (include aft.json in files). Later: same slug + edit_token from .aft/state.json. Limits: 500 files, 25MB each, 100MB total.
deploy_repo
Same engine as aft.page/run: public GitHub URL → detect → build → live URL. Static is instant; Vite and Next.js build in the background (polls until live or failed). Private repos are refused. For a local project dir, use hosted CLI aft deploy instead.

Endpoints

URLTransportStateLatencyChecked
https://mcp.aft.page/mcp streamable-http answering 436 ms 0 min ago

Alternatives to aft.page

same job, measured the same way
aft.page
by aft

Deploy HTML or dist/ to a live HTTPS URL. No account. Drop, MCP, or CLI.

5 tools answering
ship.page
by ship

Deploy HTML from any agent: POST markup, get a live URL. Static hosting API with MCP tools.

9 tools answering
Breezedeploy
by przemekzur

Deploy a local folder, git repo, or Docker image to a live HTTPS URL from your AI chat.

39 installs/wk local only
Openpouch
by openpouch

Agent-native hosting: deploy any folder to a live URL in one command. No approve tool.

68 installs/wk local only
Netcafe Build
by ainetcafe

Deploy a live web app from one sentence. build_app + poll to a public HTTPS URL you own.

7 tools answering
PageDrop MCP
by dpozimski

Deploy and manage instant HTML sites with paste, upload, and ZIP deploy

33 installs/wk local only
Softkiln Deploy
by softkiln

Host apps built with AI: deploy to a live HTTPS URL, custom domains, secrets and backups.

answering
PastML
by h4ck4life

Deploy HTML and Markdown as live URLs. Create, search, update, and manage pastes from any AI agent.

answering

aft.page — questions

Answers built from our own checks of this server.

What can aft.page do?
It exposes 5 tools, read directly from the server on our last check. Among them: aft_deploys, aft_health, aft_rollback, deploy, deploy_repo. The full list with descriptions is on this page — we take it from the server itself via tools/list, not from a README. How MCP servers expose tools in the first place →
What is aft.page mostly used for?
Its tools cluster around aft and deploy. That is what this server is built to work with — the grouping comes from the actual tool names, not from a category we assigned.
Is aft.page working right now?
We send a real MCP handshake every 15 minutes. Over the last 24 hours 92 of 92 checks got a reply (100.0%), average response time 312 ms. The bar chart above shows every period we have measured.
How do I connect aft.page?
Copy the ready config from this page — we generate it for Claude Code, Claude Desktop, Codex, Cursor and VS Code, each with the file path that client actually reads. It is a remote server, so there is nothing to install — the client connects to the address.
Does aft.page need an API key?
No. aft.page completed a full MCP handshake with us as an anonymous client and listed its tools without asking for anything. All 5 of them are readable on this page. This is what we observed, not what the docs claim.
How fast is aft.page?
It answers our handshake in 312 ms on average, which is faster than 56% of all working MCP servers we measure. The comparison comes from our own checks across the whole registry, every 15 minutes.
Is aft.page open source?
Yes — written in TypeScript and 0 stars on GitHub. The source link is on this page, so you can read exactly what it does with your data before you connect it.