Launchfiles
REMOTE · LAUNCHFILES.APP
Launchfiles hosted MCP: free page radars (design UX, search repair, deploy trust) + workspace tools.
Available components
Last scanned (4 hours ago)
Scores higher than 46% of remote servers
Reachable. Last reached 18 Oct 2026.
Category Marketing and SEO
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 10 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 Usability53
- AI-judged instruction clarity (good).Pass
- Context-footprint check failed: tool/resource definitions use about 1840 tokens (~184/item across 10 items; 10 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 Management17
- Stability observed for 5 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage79
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 36% 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
- We read all 10 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 11 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
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.
- 17 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 10 to 13. That category is still filling its 30-day observation window: 3 days of observed history at the previous scan, 4 at this one. The score rises as the window fills, whether or not the server changes.
- 15 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 3 to 7. That category is still filling its 30-day observation window: 1 days of observed history at the previous scan, 2 at this one. The score rises as the window fills, whether or not the server changes.
- 14 Oct 26 0
- Stability: unverified → 0.03 ▲ functional
- 13 Oct 26 61
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 18 Oct 2026 · Probed https://launchfiles.app/api/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=*.launchfiles.app | CN=YR2,O=Let's Encrypt,C=US | 21 Aug 2026 | 19 Nov 2026 | RSA 2048 | SHA256-RSA | 5ace6d89eff098db2013cd8c40c07829e38 |
| SANs: *.launchfiles.app, launchfiles.app | ||||||
| CN=YR2,O=Let's Encrypt,C=US (CA) | CN=Root YR,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | RSA 2048 | SHA256-RSA | 4ebd24947e24d394802d84a52fd5b319 |
| CN=Root YR,O=ISRG,C=US (CA) | CN=ISRG Root X1,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | RSA 4096 | SHA256-RSA | f24b6d17f9d9ad7cb1c9fea78782699f |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of launchfiles.app. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| app. | present | 23684 | 8 | Verified |
| launchfiles.app. | 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=31536000; includeSubDomains |
| x-content-type-options | nosniff |
| x-frame-options | DENY |
| referrer-policy | strict-origin-when-cross-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://launchfiles.app/api/mcp | Verified | 200 | |
| http (plaintext) | http://launchfiles.app/api/mcp | HTTPS enforced | 308 | https://launchfiles.app/api/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 →
launchfiles_billing_create_checkout ~154
Create provider-agnostic agent checkout. Returns payment_url and/or x402 challenge plus poll_url. Poll until paid to receive agent_api_key once. Does not debit credits or publish.
| Name | Type | Req | Description |
|---|---|---|---|
| customerEmail | string | – | Buyer email (required for card/link; optional for pure x402). |
| idempotencyKey | string | – | – |
| offerId | string | yes | Commercial SKU id (page_draft_long or pack_starter_40). Hunt-shaped ids (hunt, hunt_for_hire, product_hunt, hunt-meter) are founder-only and not for sale. |
| preferredRail | string | – | – |
| provider | string | – | Optional provider id (stripe|xmoney|x402). |
No output schema declared.
No examples provided.
launchfiles_billing_list_providers ~39
List payment providers available for agent checkout (id, enabled, mode, rails). Discover-only; does not spend or mutate ledger.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
launchfiles_billing_poll_checkout ~66
Poll an agent checkout until settled. When paid, returns agent_api_key once and, for page_draft_long, an unlock_token. Does not spend.
| Name | Type | Req | Description |
|---|---|---|---|
| paymentId | string | yes | – |
| payment_id | string | – | – |
| provider | string | – | – |
No output schema declared.
No examples provided.
launchfiles_poll_agent_key ~52
Collect the lf_agent_ key once after the approve link is opened. Pending until then. Second poll redacts the secret.
| Name | Type | Req | Description |
|---|---|---|---|
| pollToken | string | – | – |
| poll_token | string | yes | – |
No output schema declared.
No examples provided.
launchfiles_request_agent_key ~153
Primary agentic mint. Emails a one-time approve link to an allowlisted or approved-waitlist address. Returns poll_token. Does not mint a key until the link is opened. Rejects other addresses. Optional partner_id mints an lf_agent_ key whose scopes carry that partner claim (allowlist only). Omit partner_id for a generic agent key. Developer keys are not minted here. Founder UI is backup.
| Name | Type | Req | Description |
|---|---|---|---|
| string | yes | – | |
| partner_id | string | – | Optional partner id. Must be on LAUNCHFILES_PARTNER_ALLOWLIST or the call returns UNKNOWN_PARTNER and sends no email. The minted secret stays lf_agent_ and stores partner_id:<id> in scopes. |
No output schema declared.
No examples provided.
launchfiles_standalone_deployment_trust_radar_free ~146
Public free Deployment Trust Radar packet (free-full demand probe; no paid tier). Requires deployment URL, use-case description, autonomy level, and data sensitivity. Rate-limited.
| Name | Type | Req | Description |
|---|---|---|---|
| autonomy | string | yes | – |
| data_sensitivity | string | yes | – |
| idempotency_key | string | – | – |
| notify_email | string | – | Optional. If you want a link back to this report later, send an email. Not required. |
| success_looks_like_plain | string | – | – |
| url | string | yes | Target https URL. |
| use_case_plain | string | yes | Plain-language AI job description (≥ ~20 chars). |
No output schema declared.
No examples provided.
launchfiles_standalone_design_ux_radar_free ~474
Public free Design UX Radar preview for one URL. Scores come from fixed rules; a small language model writes the next-step text. Paid tier is not open to the public yet. Does not edit or publish the site. Rate-limited. Optional partner leave-behind fields add structured zones on this JSON response only (not public /cro chrome). client_ref is echoed so the caller can file the pair in their own DB; Launchfiles does not list runs by client. hide_lf_chrome is honored only for an authenticated lf_agent_ key; otherwise the response sets hide_lf_chrome false and wl_entitlement needs_auth. logo_url is an https URL shape check only (no fetch); a bad shape returns LOGO_URL_INVALID and no leave-behind.
| Name | Type | Req | Description |
|---|---|---|---|
| brand_name | string | – | Partner display name. Empty keeps Launchfiles labels. Do not invent a name. |
| client_ref | string | – | Opaque client tag echoed next to run_id. Distro files this pair in Distro's DB. Launchfiles does not isolate or list clients from this echo. |
| device | string | – | – |
| hide_lf_chrome | boolean | – | When true, Launchfiles wordmark and powered-by are removed only if the caller authenticated with lf_agent_ (including a partner-scoped key). Otherwise hide_lf_chrome is false and wl_entitlement is ne… |
| idempotency_key | string | – | – |
| locale | string | – | – |
| logo_url | string | – | Absolute https URL. Shape is checked; this path does not fetch the image. Invalid shape returns LOGO_URL_INVALID. |
| notify_email | string | – | Optional. If you want a link back to this report later, send an email. Not required. |
| partner_id | string | – | Optional. Must match the partner_id claim on the lf_agent_ key. A mismatch or an anonymous claim returns UNAUTHORIZED_PARTNER or NEEDS_AUTH. Omit to use the key's claim. Partner keys also consume the… |
| primary_color | string | – | Optional #RGB or #RRGGBB header accent. Invalid values are ignored. |
| role | string | – | – |
| url | string | yes | Public https URL to analyze (preview mode only). |
No output schema declared.
No examples provided.
launchfiles_standalone_page_draft_paid ~276
Paid Page Draft after a settled page_draft_long checkout, or a founder-issued developer key (no Stripe). Same writer door as the web buyer. Pass unlock_token from billing poll, or Authorization: Bearer with the developer key, plus a brief (who, and proof or proof_mode=no_proof). length=short|medium|long. Optional piece_kind: blog_post | landing_page | essay | social_post | seo_page | other. Omitted piece_kind keeps today's inference (short social/X stays cognition). A developer key may request short. Not a credit debit. Nothing is published. Writer failure is named — never an outline template.
| Name | Type | Req | Description |
|---|---|---|---|
| length | string | – | – |
| next_step | string | – | – |
| paymentId | string | – | – |
| payment_id | string | – | – |
| piece_kind | string | – | Surface. blog_post/essay/landing_page/seo_page with an owned URL can exit cognition even at length=short. social_post stays cognition. Omit to keep today's short→cognition default. |
| proof | string | – | – |
| proof_mode | string | – | – |
| topic | string | – | – |
| unlockToken | string | – | – |
| unlock_token | string | – | – |
| url | string | – | – |
| who | string | – | – |
No output schema declared.
No examples provided.
launchfiles_standalone_page_draft_short ~224
Writer-short draft (~400 words). A founder-issued developer key gets full product access — no Stripe Writer checkout. Same writer door as the web buyer. Send the developer key as Authorization: Bearer (hosted MCP also accepts x-api-key or JSON-RPC _meta). Pass a brief (who, and proof or proof_mode=no_proof). Optional piece_kind: blog_post | landing_page | essay | social_post | seo_page | other. Omitted piece_kind keeps today's short→cognition social/X path. Owned blog/essay + piece_kind can return a pasteable dek. Nothing is published. Writer failure is named — never an outline template.
| Name | Type | Req | Description |
|---|---|---|---|
| next_step | string | – | – |
| piece_kind | string | – | Surface. blog_post/essay with an owned URL can exit cognition and emit a card dek. Omit for today's cognition short. |
| proof | string | – | – |
| proof_mode | string | – | – |
| topic | string | – | – |
| url | string | – | – |
| who | string | – | – |
No output schema declared.
No examples provided.
launchfiles_standalone_search_repair_radar_free ~186
Public free Search Repair Radar teaser. Preview only — never unlocks the $29/mo paid repair packet. Owned product properties that already declare Search Console on their adapter use that bind (no access_token). Other sites need a Google access_token or return needs_auth + human connect URL. Rate-limited.
| Name | Type | Req | Description |
|---|---|---|---|
| access_token | string | – | Optional. OAuth access token with webmasters.readonly for sites that are not an owned adapter property. Not required for an already-bound product GSC property. |
| gsc_site_url | string | – | GSC property e.g. sc-domain:example.com or https://example.com/ |
| idempotency_key | string | – | – |
| notify_email | string | – | Optional. If you want a link back to this report later, send an email. Not required. |
| site_url | string | – | – |
No output schema declared.
No examples provided.
How do I install the Launchfiles MCP server?
Launchfiles is a hosted endpoint at https://launchfiles.app/api/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 · launchfiles.app
claude mcp add --transport http app-launchfiles-launchfiles 'https://launchfiles.app/api/mcp'
What is the Launchfiles MCP server?
Launchfiles is an MCP server listed in the public MCP registry as app.launchfiles/launchfiles. Launchfiles hosted MCP: free page radars (design UX, search repair, deploy trust) + workspace tools. This page covers its hosted endpoint (https://launchfiles.app/api/mcp).
Is the Launchfiles MCP server safe to use?
Launchfiles scores 63 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 Launchfiles MCP server expose?
Launchfiles exposes 10 tools: launchfiles_standalone_design_ux_radar_free, launchfiles_standalone_search_repair_radar_free, launchfiles_standalone_deployment_trust_radar_free, launchfiles_billing_list_providers, launchfiles_billing_create_checkout, and 5 more. Their descriptions and schemas cost roughly 1,770 tokens of context every time the server is loaded.
Does the Launchfiles MCP server require authentication?
No. We connected to Launchfiles without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the Launchfiles MCP server still maintained?
Launchfiles is still listed as active in the MCP registry. We last reached this channel on 18 October 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.