aft.page MCP server

• aft_deploysFree

  List the versions (v1, v2…) of a slug with their label, door, commit and whether each is live or a held preview. Needs edit_token from .aft/state.json (or the first deploy). Same history the project UI shows after claim.

• aft_healthFree

  Ping the aft.page deploy API.

• aft_promoteFree

  Make a held preview version live at the same URL. Pass version (e.g. 4) or deploy_id from aft_deploys. Needs edit_token.

• aft_rollbackFree

  Point the live slug at a prior version from aft_deploys, by version number or deploy_id. Same URL. Needs edit_token from .aft/state.json. Claim not required.

• deploywrite actionFree

  Publish to a live URL. Pass html (one page) OR files (a built site, or a small app's source). Plain HTML → html. Vite/React → npm run build, then files from dist/. Next static export → files from out/; a static site needs index.html. Flask/FastAPI/Django/Express → the source files with requirements.txt or package.json; aft builds and runs it. Never upload node_modules, .venv, or .next/. First hit: preferred_slug from aft.json (include aft.json in files). Later: same slug + edit_token from .aft/state.json — every update is a new version (v1, v2…) at the same URL. Pass hold:true to keep an update as a preview until aft_promote. label names the version. Limits: 500 files, 25MB each, 100MB total.

• deploy_repowrite actionFree

  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.

• –Code scanremote-only server, no package to scann/a
• Live reliabilityremote reachable in 1789ms20/20
• Tool poisoning6 tool descriptions checked15/15
• Auth qualityopen endpoint exposes 2 write-action tools with no auth3/15
• Maintenancelast push 1 days ago15/15
• Maintainer identityendpoint served from the registry-verified namespace domain8/10

Safety score

81/100

higher than 58% of 1,119 Developer tools servers

Tools

6

the typical Developer tools server has 7

Tools that change things

33%

typical: 5%. Fewer write tools means less an agent can break

Uptime

100%

of our recent checks; the typical remote Developer tools server answers 100%

Response time

547 ms

faster than 27% of 443 Developer tools servers

Grade history

• 2026-10-30restoreC → Bscore 81: Write-action tools reachable without authentication

aft.page: common questions

Is aft.page MCP server safe?

Mostly: it is graded B (81/100). Read the aft.page safety report

How do I install aft.page?

It runs remotely at mcp.aft.page. Add it to Claude Code, Cursor, VS Code or Claude Desktop with the snippets above, or call it through the mcp.market gateway without installing anything.

Does aft.page need an API key?

Not as far as the registry entry and our scan can tell: no credentials are declared or required.

Is aft.page maintained?

The last commit was 7 days ago (2026-10-29). The latest release is v1.1.0.

Is aft.page up?

100% of our last 28 checks got an answer. We check remote servers about four times a day.

What can I use instead of aft.page?

Servers from other publishers that do the same job: OctoCounts MCP Server, Dockhold MCP server and GitDiagram MCP server.

How does aft.page compare with other Developer tools MCP servers?

safety score 81/100 (higher than 58% of 1,119 Developer tools servers); tools 6 (the typical Developer tools server has 7); tools that change things 33% (typical: 5%. Fewer write tools means less an agent can break). Full comparison.