aft.page
REMOTE · MCP.AFT.PAGE · SCANNED SEP 20
Deploy HTML or dist/ to a live HTTPS URL. No account. Drop, MCP, or CLI.
Available components
How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →
Endpoint Security63
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation not fully verified: no authorisation is required to call this server, and 5 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe. See how to fix → View diagnostics → Unverified
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability75
- AI-judged instruction clarity (good).Pass
- Tool/resource definitions use about 516 tokens (~103/item across 5 items; 5 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management70
- Stability observed for 21 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage97
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 91% of tool parameters carry a description.Partial
Tool Safety75
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- 0 of 2 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation; "deploy" implies "deploy" and declares no destructiveHint at all, which the MCP spec reads as destructive by default. See how to fix → Fail
- An AI judge read all 5 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a current MCP spec version (2026-07-28).Pass
How do I install the aft.page MCP server?
aft.page is a hosted endpoint at https://mcp.aft.page/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
remote · mcp.aft.page
claude mcp add --transport http page-aft-mcp 'https://mcp.aft.page/mcp'
{
"mcpServers": {
"page-aft-mcp": {
"url": "https://mcp.aft.page/mcp"
}
}
} {
"servers": {
"page-aft-mcp": {
"type": "http",
"url": "https://mcp.aft.page/mcp"
}
}
} [mcp_servers.page-aft-mcp] url = "https://mcp.aft.page/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"page-aft-mcp": {
"type": "remote",
"url": "https://mcp.aft.page/mcp",
"enabled": true
}
}
} openclaw mcp add page-aft-mcp --url 'https://mcp.aft.page/mcp' --transport streamable-http
mcp_servers:
page-aft-mcp:
url: "https://mcp.aft.page/mcp" {
"McpServers": {
"page-aft-mcp": {
"Transport": "http",
"Url": "https://mcp.aft.page/mcp"
}
}
} assistant mcp add page-aft-mcp -t streamable-http -u 'https://mcp.aft.page/mcp'
{
"mcpServers": {
"page-aft-mcp": {
"type": "http",
"url": "https://mcp.aft.page/mcp"
}
}
} The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 20 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 67 to 70. That category is still filling its 30-day observation window: 20 days of observed history at the previous scan, 21 at this one. The score rises as the window fills, whether or not the server changes.
- 18 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 60 to 63. That category is still filling its 30-day observation window: 18 days of observed history at the previous scan, 19 at this one. The score rises as the window fills, whether or not the server changes.
- 16 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 53 to 57. That category is still filling its 30-day observation window: 16 days of observed history at the previous scan, 17 at this one. The score rises as the window fills, whether or not the server changes.
- 13 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 43 to 47. That category is still filling its 30-day observation window: 13 days of observed history at the previous scan, 14 at this one. The score rises as the window fills, whether or not the server changes.
- 11 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 37 to 40. That category is still filling its 30-day observation window: 11 days of observed history at the previous scan, 12 at this one. The score rises as the window fills, whether or not the server changes.
- 9 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 30 to 33. That category is still filling its 30-day observation window: 9 days of observed history at the previous scan, 10 at this one. The score rises as the window fills, whether or not the server changes.
- 7 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 23 to 27. That category is still filling its 30-day observation window: 7 days of observed history at the previous scan, 8 at this one. The score rises as the window fills, whether or not the server changes.
- 5 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 17 to 20. That category is still filling its 30-day observation window: 5 days of observed history at the previous scan, 6 at this one. The score rises as the window fills, whether or not the server changes.
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 20 Sept 2026 · Probed https://mcp.aft.page/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=aft.page | CN=WE1,O=Google Trust Services,C=US | 7 Aug 2026 | 5 Nov 2026 | ECDSA 256 | ECDSA-SHA256 | 548a28bdc732c00f0e04ce62b7ef07bf |
| SANs: aft.page, mcp.aft.page, *.mcp.aft.page | ||||||
| CN=WE1,O=Google Trust Services,C=US (CA) | CN=GTS Root R4,O=Google Trust Services LLC,C=US | 13 Dec 2023 | 20 Feb 2029 | ECDSA 256 | ECDSA-SHA384 | 7ff31977972c224a76155d13b6d685e3 |
| CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) | CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE | 15 Nov 2023 | 28 Jan 2028 | ECDSA 384 | SHA256-RSA | 7fe530bf331343bedd821610493d8a1b |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of mcp.aft.page. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| page. | present | 64712 | 8 | Verified |
| aft.page. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 200 |
| Header | Value |
|---|---|
| strict-transport-security | max-age=15552000; includeSubDomains |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://mcp.aft.page/mcp | Verified | 200 | |
| http (plaintext) | http://mcp.aft.page/mcp | HTTPS enforced | 301 | https://mcp.aft.page/mcp |
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
aft_deploys List aft.page deploy history ~84
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.
| Name | Type | Req | Description |
|---|---|---|---|
| edit_token | string | yes | From first deploy / .aft/state.json. Required to update or rollback the same URL. |
| slug | string | yes | Site slug from aft.json or .aft/state.json |
No output schema declared.
No examples provided.
aft_health Check aft.page API ~15
Ping the aft.page deploy API.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
aft_rollback Rollback aft.page site ~98
Point the live slug at a prior deployId from aft_deploys. Same URL. Needs edit_token from .aft/state.json. Claim not required.
| Name | Type | Req | Description |
|---|---|---|---|
| deploy_id | string | yes | Prior deployId from aft_deploys |
| edit_token | string | yes | From first deploy / .aft/state.json. Required to update or rollback the same URL. |
| slug | string | yes | Site slug from aft.json or .aft/state.json |
No output schema declared.
No examples provided.
deploy Deploy to aft.page ~224
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.
| Name | Type | Req | Description |
|---|---|---|---|
| edit_token | string | – | From first deploy / .aft/state.json. Required to update or rollback the same URL. |
| expires | string | – | Optional quick-view expiry, e.g. "1h", "24h", "90s", "7d". Anonymous (unclaimed) deploys only — the link 404s after this. |
| files | array | – | – |
| html | string | – | One HTML document. Ignored if files is set. |
| preferred_slug | string | – | aft.json slug. Required with edit_token. |
No output schema declared.
No examples provided.
deploy_repo Deploy a public GitHub repo ~95
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.
| Name | Type | Req | Description |
|---|---|---|---|
| url | string | yes | GitHub URL or owner/repo, e.g. https://github.com/mdn/beginner-html-site |
No output schema declared.
No examples provided.
What is the aft.page MCP server?
aft.page is an MCP server listed in the public MCP registry as page.aft/mcp. Deploy HTML or dist/ to a live HTTPS URL. No account. Drop, MCP, or CLI. This page covers its hosted endpoint (https://mcp.aft.page/mcp).
Is the aft.page MCP server safe to use?
aft.page scores 75 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the aft.page MCP server expose?
aft.page exposes 5 tools: deploy, deploy_repo, aft_deploys, aft_rollback, aft_health. Their descriptions and schemas cost roughly 516 tokens of context every time the server is loaded.
Does the aft.page MCP server require authentication?
No. We connected to aft.page without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the aft.page MCP server still maintained?
aft.page is still listed as active in the MCP registry. We last reached this channel on 20 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.