aft.page is an MCP server with 5 tools an agent can call, among them aft_deploys, aft_health, aft_rollback. It answers at https://mcp.aft.page/mcp over streamable HTTP, and it listed its tools to an anonymous client, so no sign-in was needed for that. Our probes reached it 6 of 6 times since 12 September 2026; the last check, on 24 October 2026, succeeded.
Deploy a folder, build output, or public GitHub repo to a live URL. Update, roll back.
Description as the publisher wrote it.
| Tool | What it does |
|---|---|
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. Inputs: slug, edit_token |
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. Inputs: slug, edit_token, deploy_id |
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 .n Inputs: html, files, preferred_slug, edit_token, expires |
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 dep Inputs: url |
Every block below points at https://mcp.aft.page/mcp. Pick your client and copy.
claude mcp add --transport http aft-page https://mcp.aft.page/mcp
{
"mcpServers": {
"aft-page": {
"command": "npx",
"args": ["-y", "mcp-remote", "https://mcp.aft.page/mcp"]
}
}
}{
"mcpServers": {
"aft-page": {
"url": "https://mcp.aft.page/mcp"
}
}
}{
"servers": {
"aft-page": {
"type": "http",
"url": "https://mcp.aft.page/mcp"
}
}
}{
"context_servers": {
"aft-page": {
"url": "https://mcp.aft.page/mcp"
}
}
}{
"mcpServers": {
"aft-page": {
"serverUrl": "https://mcp.aft.page/mcp"
}
}
}{
"mcpServers": {
"aft-page": {
"url": "https://mcp.aft.page/mcp"
}
}
}name: aft.page
version: 0.0.1
schema: v1
mcpServers:
- name: aft.page
type: streamable-http
url: https://mcp.aft.page/mcp{
"mcpServers": {
"aft-page": {
"httpUrl": "https://mcp.aft.page/mcp"
}
}
}{
"mcpServers": {
"aft-page": {
"type": "http",
"url": "https://mcp.aft.page/mcp"
}
}
}{
"mcpServers": {
"aft-page": {
"url": "https://mcp.aft.page/mcp"
}
}
}goose://extension?url=https%3A%2F%2Fmcp.aft.page%2Fmcp&type=streamable_http&id=aft-page&name=aft.page
It answered our last check on 24 October 2026 in 724 ms. Over 6 checks since 12 September 2026 it answered 6. Status here comes from Neuronto's own probes, not from the publisher.
Yes. It is published by aft.page and served from mcp.aft.page, the vendor's own domain: https://mcp.aft.page/mcp.
5, as returned by the server's own tools/list on 23 September 2026: aft_deploys, aft_health, aft_rollback, deploy, deploy_repo.
It answered our last check on 24 October 2026 in 724 ms. Over 6 checks since 12 September 2026 it answered 6.
Put the server under mcpServers in ~/.cursor/mcp.json with the URL https://mcp.aft.page/mcp. The exact JSON is above, with the same setup for Claude Code, Claude Desktop, VS Code, Windsurf, Zed, Gemini CLI and the rest.
It listed its tools to an anonymous client, so reading the tool list needs no key. Individual tools can still ask for credentials in their own inputs.
Publisher: page.aft. Endpoint host: mcp.aft.page. ARD identifier: urn:air:page.aft:mcp:mcp.
First indexed 10 September 2026. The tools are exactly what the server returned; nothing on this page
is inferred from its name. Ranking in Neuronto search is never for sale.