MCP serverpage.aft/mcp
Deploy HTML or dist/ to a live HTTPS URL.
Read more
Deploy HTML or dist/ to a live HTTPS URL. No account. Drop, MCP, or CLI.Overview
Score?
UNRATED 0.672
of what a free look can see, on 30 looks
Looks
35
last 15 hr ago
Tools
5
More info
URL
mcp.aft.page/mcp
streamable-http
Says it is
aft-page 0.6.0
protocol 2025-06-18
In the record since
32 days ago
Among servers18,413 with a card
0median 0.606 · this server 0.672 · highest on record 0.8561
Toolsfrom sha256:512c7e04cf…eb7b59
| Tool | Schema |
|---|---|
| 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. |
input · no output |
| aft_health Ping the aft.page deploy API. |
input · no output |
| 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. |
input · no output |
| 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/. Alway |
input · no output |
| 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 |
input · no output |
Verify it yourself
npx teppi-check https://mcp.aft.page/mcpcurl -s https://api.teppi.xyz/v1/trust/mcp/mcs_01M1FZ2QG9D9SMFJ3TCG8TJYBW