Press5 launch pad
REMOTE · MY.PRESS5.XYZ · 2 COMPONENTS
Publish static websites to a live HTTPS URL from your AI tool. Free tier, instant deploys.
Available components
Last scanned (12 hours ago)
Scores higher than 52% of remote servers
Reachable. Last reached 21 Nov 2026.
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 check failed: no authorisation is required to call this server, and it exposes a tool marked destructive (delete_site). See how to fix → View diagnostics → Fail
- 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 Usability79
- 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
- AI-judged instruction clarity (good).Pass
- Context-footprint check failed: tool/resource definitions use about 1232 tokens (~136/item across 9 items; 9 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management7
- Stability observed for 2 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage87
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 62% of tool parameters carry a description.Partial
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- All 2 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation.Pass
- An AI judge read all 10 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Checks we ran (13)
- TLS certificate
- Authorization
- HTTPS
- HSTS header
- DNSSEC
- Transport
- Schema quality
- Stability
- Tool coverage
- Injection markers
- Destructive annotations
- Judged manipulation
- MCP protocol
Does not apply to this hosted endpoint (2)
- Supply Chain SecurityScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
- Provenance & TransparencyScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
The score does not measure everything. What the score does not measure →
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.
- 21 Nov 26 0
- Tool “get_template” rewrote its description, which is the text the model reads security
- Tool “list_templates” rewrote its description, which is the text the model reads security
- 20 Nov 26 +2
- The server rewrote its instructions, which are the text every model session reads security
- Tool “deploy_site” rewrote its description, which is the text the model reads security
- Schema quality: pass → fail ▼ functional
- Stability: unverified → 0.03 ▲ functional
- The server now declares the “prompts” capability functional
- First check of Schema quality: 100 functional
- New prompt “make_website” functional
- New prompt “publish_site” functional
- New tool “get_template” functional
- New tool “list_templates” functional
- “deploy_site” added an optional parameter “fields” cosmetic
- “deploy_site” added an optional parameter “site_key” cosmetic
- “deploy_site” added an optional parameter “template” cosmetic
- “deploy_site” reworded the description of “site” cosmetic
- “deploy_site” made “files” optional cosmetic
- “deploy_site” made “site” optional cosmetic
- 19 Nov 26 65
First indexed and scored.
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 21 Nov 2026 · Probed https://my.press5.xyz/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_256_GCM_SHA384 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=my.press5.xyz | CN=YE1,O=Let's Encrypt,C=US | 15 Nov 2026 | 13 Feb 2027 | ECDSA 256 | ECDSA-SHA384 | 66cb49518f7eff23f212df05e5796741eab |
| SANs: my.press5.xyz | ||||||
| CN=YE1,O=Let's Encrypt,C=US (CA) | CN=Root YE,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | ECDSA 384 | ECDSA-SHA384 | 5ddd70dd31f801c85c186a7a04b80afe |
| CN=Root YE,O=ISRG,C=US (CA) | CN=ISRG Root X2,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | ECDSA-SHA384 | 872165fc34b6e5fba8add5b3705fb53a |
| CN=ISRG Root X2,O=Internet Security Research Group,C=US (CA) | CN=ISRG Root X1,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | SHA256-RSA | 6c8f1dc727c7117f7baf853ac980f9cd |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of my.press5.xyz. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | Trust anchor | 20326, 38696 | 8, 8 | Verified |
| xyz. | DS published | 3599, 18130 | 8, 8 | Verified |
| press5.xyz. | No DS | 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=31536000 |
| content-security-policy | default-src 'self'; img-src 'self' data:; style-src 'self'; script-src 'none'; form-action 'self' https://checkout.stripe.com https://billing.stripe.com; frame-ancestors 'none'; base-uri 'none' |
| x-content-type-options | nosniff |
| x-frame-options | DENY |
| referrer-policy | same-origin |
| permissions-policy | camera=(), microphone=(), geolocation=() |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://my.press5.xyz/mcp | Verified | 200 | |
| http (plaintext) | http://my.press5.xyz/mcp | HTTPS enforced | 301 | https://my.press5.xyz/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 →
delete_site Delete a site ~86
Delete a site and all its deploys. It goes offline at once and the name becomes free for anyone. Ask the person first.
| Name | Type | Req | Description |
|---|---|---|---|
| confirm | boolean | yes | Must be true |
| site | string | yes | – |
| token | string | – | A press5 token (p5_...). Only needed when the MCP connection has no Authorization header, e.g. right after login_check. |
No output schema declared.
No examples provided.
deploy_site Deploy a static site ~394
Publish a static website (HTML, CSS, JS, images) to the Press5 launch pad and get its live URL. Works with no account: without a token the site gets a random name, goes live at once, and the reply has a claim_url for the person to keep it (unclaimed sites are deleted after 3 days) and a site_key to redeploy the same site. With a token, "site" picks the name (3-42 lowercase letters, digits, hyphens; created the first time if free). Send every file of the built site; this replaces the whole site. Text files as plain content, binary files as base64 with encoding "base64". Best for small sites: for big builds use the HTTP API with a .tar.gz (see https://my.press5.xyz/llms.txt). To start from one of the free starter templates (list_templates), send "template" and optional "fields" instead of files.
| Name | Type | Req | Description |
|---|---|---|---|
| fields | object | – | With template: the text to fill in, by field key, e.g. {"name": "Rosie's Café", "email": "hi@rosies.example"}. |
| files | array | – | – |
| site | string | – | Site name, becomes <site>.on.press5.xyz. Needs a token; leave it out for a random name. |
| site_key | string | – | The site_key from an earlier deploy without an account, to update that same site. |
| spa | boolean | – | Single-page app: serve index.html for unknown paths (client-side routing) |
| template | string | – | Instead of files: the id of a starter template from list_templates, published as it is or with "fields" filled in. |
| token | string | – | A press5 token (p5_...). Only needed when the MCP connection has no Authorization header, e.g. right after login_check. |
No output schema declared.
No examples provided.
get_template Get a starter template ~86
All files of one starter template (HTML and CSS as text, fonts as base64), with "fields" filled in if given. Change them as the person wants, then publish them with deploy_site { files }. No account needed for free templates; premium ones need a token from an account with press5 web hosting.
| Name | Type | Req | Description |
|---|---|---|---|
| fields | object | – | – |
| template | string | yes | – |
No output schema declared.
No examples provided.
list_sites List my sites ~62
List the sites on this Press5 account, with their URLs and status, plus the account limits.
| Name | Type | Req | Description |
|---|---|---|---|
| token | string | – | A press5 token (p5_...). Only needed when the MCP connection has no Authorization header, e.g. right after login_check. |
No output schema declared.
No examples provided.
list_templates Starter templates ~145
List the starter templates, each with a live preview_url and the fields that can be filled in: free ones (café, portfolio, product landing page, link in bio, wedding, tradesperson, CV, coming soon, blog, gaming sites) and premium ones (premium: true: software launch, design studio, fine dining, coach, botanical wedding, esports team) with their own fonts, illustration and motion. No account needed to list or preview them. Premium ones are included with press5 web hosting and need a token from an account that has it. Deploy one with deploy_site { template, fields }, or call get_template to fetch its files and change them first.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
login_check Finish signing in ~47
Check whether the person approved the sign-in from login_start. Call it every few seconds after they say they have pressed Approve. Returns the token once.
| Name | Type | Req | Description |
|---|---|---|---|
| device_code | string | yes | – |
No output schema declared.
No examples provided.
login_start Sign in by email ~83
Start signing in to the Press5 launch pad when you have no token. Press5 emails the person a link to approve this tool (it also creates a free account for a new email). Then call login_check.
| Name | Type | Req | Description |
|---|---|---|---|
| client | string | – | Your name, shown to the person, e.g. "Claude Code" |
| string | yes | The person's email address |
No output schema declared.
No examples provided.
rollback_site Roll back a site ~73
Put an earlier deploy of a site back live. Get deploy ids from site_info.
| Name | Type | Req | Description |
|---|---|---|---|
| deploy | string | yes | – |
| site | string | yes | – |
| token | string | – | A press5 token (p5_...). Only needed when the MCP connection has no Authorization header, e.g. right after login_check. |
No output schema declared.
No examples provided.
site_info Site details ~62
One site with its recent deploys (ids for rollback_site).
| Name | Type | Req | Description |
|---|---|---|---|
| site | string | yes | – |
| token | string | – | A press5 token (p5_...). Only needed when the MCP connection has no Authorization header, e.g. right after login_check. |
No output schema declared.
No examples provided.
How do I install the Press5 launch pad MCP server?
Press5 launch pad is a hosted endpoint at https://my.press5.xyz/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 · my.press5.xyz
claude mcp add --transport http xyz-press5-launch-pad 'https://my.press5.xyz/mcp'
What is the Press5 launch pad MCP server?
Press5 launch pad is an MCP server listed in the public MCP registry as xyz.press5/launch-pad. Publish static websites to a live HTTPS URL from your AI tool. Free tier, instant deploys. This page covers its hosted endpoint (https://my.press5.xyz/mcp).
Is the Press5 launch pad MCP server safe to use?
Press5 launch pad scores 67 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 Press5 launch pad MCP server expose?
Press5 launch pad exposes 9 tools: deploy_site, list_templates, get_template, list_sites, site_info, and 4 more. Their descriptions and schemas cost roughly 1,038 tokens of context every time the server is loaded.
Does the Press5 launch pad MCP server require authentication?
No. We connected to Press5 launch pad without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the Press5 launch pad MCP server still maintained?
Press5 launch pad is still listed as active in the MCP registry. We last reached this channel on 21 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.
What did VerifyMCP test on the Press5 launch pad MCP server?
VerifyMCP ran 13 checks on Press5 launch pad, covering TLS certificate, Authorization, HTTPS, HSTS header and 9 more. Supply Chain Security and Provenance & Transparency do not apply to a hosted endpoint, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.