Skip to content

LaunchFiles MCP server

app.launchfiles/launchfileslaunchfiles.appstreamable-httpv2.2.1Scanned

Live checkout, UX, Search Console SEO, horizon memory, and zero-touch distribution via MCP.

7 tools: 6 change things and 1 only read.

Tools: 0 delete, 0 irreversible, 6 write, 1 read.
  • Reads private data · 0
  • Reads text others write · 7
  • Can send data out · 7
  • 5 findings, 1 high

Tools listed without sign-in. Remote posture

Anlyon alternative

6 of these tools change something. Run those as governed actions.

Declare what an action changes, and Anlyon puts it under a shared limit, binds every approval to the exact request, and grades the outcome. It works on any HTTPS API you can describe as an action.

Anlyon Radar does not run, proxy or govern this MCP server. A tool your own code calls directly is not routed through Anlyon and is not governed by it.

Import an OpenAPI spec →

What the LaunchFiles MCP server can do

The LaunchFiles MCP server is published by launchfiles.app, a domain the MCP Registry verified. It has 7 tools. It can create or change data (6 tools: launchfiles_live_drift_check, launchfiles_homepage_roast, launchfiles_seo_audit, launchfiles_ux_audit and 2 more), but cannot delete data. 1 tool only reads.

7 tools bring in text other people can write (launchfiles_seo_indexing_status, launchfiles_live_drift_check, launchfiles_homepage_roast and 4 more); 7 tools can send data out of your system (launchfiles_seo_indexing_status, launchfiles_live_drift_check, launchfiles_homepage_roast and 4 more).

The fixed checks matched 5 findings, 1 of them high severity (annotation-conflict and sensitive-path). Each one comes with the text it matched.

Its remote endpoint lists its tools without sign-in, and its tools changed 5 times since Anlyon Radar first saw them.

Last scanned Nov 16, 2026, version 2.2.1.

Tools

Grouped by what each tool does, most consequential first. Open one for its reasons and full description; descriptions are the publisher's own words.

7 tools

Changes things 6Claude Code: ask
  • launchfiles_domain_horizon_memoryRecall longitudinal multi-run audit memory across Clarity, UX, Search/GSC, Checkout Drift, and Directory Distribution (distributionHistory) for a domain, surfacing verified shipped…Reads text others writeCan send data outNo findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
    • outboundThe input takes a URL (input.url): a request to a URL can carry data to whoever runs it.
    Description, as the server wrote it
    Recall longitudinal multi-run audit memory across Clarity, UX, Search/GSC, Checkout Drift, and Directory Distribution (distributionHistory) for a domain, surfacing verified shipped-change deltas, cross-vertical self-challenges, and the next highest-leverage bet.

    Annotations the server declares

    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: true
  • launchfiles_homepage_roastRun a live 5-second clarity roast + server HTML + checkout drift check on any public homepage, persisting the receipt while keeping response screenshots compact by default.Reads text others writeCan send data out1 finding

    Why it is in this group

    • The description's first verb is "run": a word for a change.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
    • outboundThe input takes a URL (input.url): a request to a URL can carry data to whoever runs it.

    Findings

    • Warn

      The server marks "launchfiles_homepage_roast" read-only (readOnlyHint: true), and its own name, description or input give the class "write".

      Matched text

      annotations: {"readOnlyHint":true,"destructiveHint":false,"idempotentHint":true,"openWorldHint":true}; The description's first verb is "run": a word for a change.

      What this check looks for
    Description, as the server wrote it
    Run a live 5-second clarity roast + server HTML + checkout drift check on any public homepage, persisting the receipt while keeping response screenshots compact by default.

    Annotations the server declares

    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: true
  • launchfiles_live_drift_checkRun a live HTTP, legal, sitemap, and Stripe Checkout / seller-brand drift inspection on a public website.Reads text others writeCan send data out1 finding

    Why it is in this group

    • The description's first verb is "run": a word for a change.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
    • outboundThe input takes a URL (input.url): a request to a URL can carry data to whoever runs it.

    Findings

    • Warn

      The server marks "launchfiles_live_drift_check" read-only (readOnlyHint: true), and its own name, description or input give the class "write".

      Matched text

      annotations: {"readOnlyHint":true,"destructiveHint":false,"idempotentHint":true,"openWorldHint":true}; The description's first verb is "run": a word for a change.

      What this check looks for
    Description, as the server wrote it
    Run a live HTTP, legal, sitemap, and Stripe Checkout / seller-brand drift inspection on a public website.

    Annotations the server declares

    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: true
  • launchfiles_mcp_registry_readinessProbe any live product URL for /llms.txt, /.well-known/mcp.json, /.well-known/mcp-registry-auth, /.well-known/agent-card.json, remote /api/mcp tools/list, official MCP Registry dri…Reads text others writeCan send data out1 finding

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
    • outboundThe input takes a URL (input.url): a request to a URL can carry data to whoever runs it.

    Findings

    • High

      The description refers to "/.well-known/mcp.json".

      Matched text

      description: "...obe any live product URL for /llms.txt, /.well-known/mcp.json, /.well-known/mcp-registry-auth, /.well..."

      What this check looks for
    Description, as the server wrote it
    Probe any live product URL for /llms.txt, /.well-known/mcp.json, /.well-known/mcp-registry-auth, /.well-known/agent-card.json, remote /api/mcp tools/list, official MCP Registry drift, and public companion repository status.

    Annotations the server declares

    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: true
  • launchfiles_seo_auditRun or recall LaunchFiles' Search & SEO Radar: live Search Console CTR-leak prioritization, sitemap crawl on up to 10 routes, SERP landscape, and cross-model claim-verified upgrade…Reads text others writeCan send data out1 finding

    Why it is in this group

    • The description's first verb is "run": a word for a change.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
    • untrusted-inputThe description's first sentence says "crawl": it reads web pages, which anyone can write.
    • outboundThe input takes a URL (input.url): a request to a URL can carry data to whoever runs it.

    Findings

    • Warn

      The server marks "launchfiles_seo_audit" read-only (readOnlyHint: true), and its own name, description or input give the class "write".

      Matched text

      annotations: {"readOnlyHint":true,"destructiveHint":false,"idempotentHint":true,"openWorldHint":true}; The description's first verb is "run": a word for a change.

      What this check looks for
    Description, as the server wrote it
    Run or recall LaunchFiles' Search & SEO Radar: live Search Console CTR-leak prioritization, sitemap crawl on up to 10 routes, SERP landscape, and cross-model claim-verified upgrade package.

    Annotations the server declares

    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: true
  • launchfiles_ux_auditRun LaunchFiles' live Chromium 12-gate Design & UX Radar across desktop (1440x900) and mobile (390x844), returning measured tap-target, landmark, CTA, and hero redesign diagnosis.Reads text others writeCan send data out1 finding

    Why it is in this group

    • The description's first verb is "run": a word for a change.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
    • outboundThe input takes a URL (input.url): a request to a URL can carry data to whoever runs it.

    Findings

    • Warn

      The server marks "launchfiles_ux_audit" read-only (readOnlyHint: true), and its own name, description or input give the class "write".

      Matched text

      annotations: {"readOnlyHint":true,"destructiveHint":false,"idempotentHint":true,"openWorldHint":true}; The description's first verb is "run": a word for a change.

      What this check looks for
    Description, as the server wrote it
    Run LaunchFiles' live Chromium 12-gate Design & UX Radar across desktop (1440x900) and mobile (390x844), returning measured tap-target, landmark, CTA, and hero redesign diagnosis.

    Annotations the server declares

    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: true
Only reads 1Show 1 read-only tool
  • launchfiles_seo_indexing_statusInspect live Google Search Console sitemap and indexing status for a domain or URL.Reads text others writeCan send data outNo findings

    Why it is in this group

    • The name "launchfiles_seo_indexing_status" says "status": a word for reading.

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
    • untrusted-inputThe description's first sentence says "inspect" and "url": it reads web pages, which anyone can write.
    • untrusted-inputThe input takes a URL (input.url), and the tool reads it: it reads web pages, which anyone can write.
    • outboundThe input takes a URL (input.url): a request to a URL can carry data to whoever runs it.

    Claude Code: ask, because it is tagged outbound.

    Description, as the server wrote it
    Inspect live Google Search Console sitemap and indexing status for a domain or URL.

    Annotations the server declares

    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: true

This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.

Exfil surface

Which tools read private data, which read text someone else can write, and which can send data out. One of each is a path a prompt injection can use.

No private-data, untrusted-input, outbound path in this server alone: no tool is tagged private-data.

Reads private data0
Reads files, mail, messages, databases, secrets, calendars or repositories.

Other servers in the same agent add their own tools to these paths. Audit your whole setup to see them together.

Remote posture

What anyone on the internet sees at the remote endpoint: an anonymous initialize and tools/list, and the public OAuth metadata.

Tools listed without sign-in

Looked at Nov 20, 2026, 18:29 UTC, unchanged since Nov 20, 2026. No credentials were sent and no tool was called. What is looked at.

Reachable
yes
HTTP status of an anonymous initialize
200
tools/list served without credentials
yes
Tools that change things, listed without credentials
6
Protocol version
2025-06-18
WWW-Authenticate on 401
not observed
resource_metadata in WWW-Authenticate
not observed
RFC 9728 protected resource metadata
https://launchfiles.app/.well-known/oauth-protected-resource/api/mcp
Authorization servers
not observed
Legacy HTTP+SSE transport
no
Dynamic client registration
not observed
Client ID metadata documents
not observed
  • WarnThe whole server

    The endpoint served tools/list without credentials, and the list has 6 tools that change things (6 write). Whether a call also works without credentials was not tested: tools are never called.

    Matched text

    https://launchfiles.app/api/mcp: tools/list returned 7 tools to an anonymous client, including launchfiles_live_drift_check (write), launchfiles_homepage_roast (write), launchfiles_seo_audit (write), launchfiles_ux_audit (write), launchfiles_domain_horizon_memory (write) and 1 more

    What this check looks for

Posture changes

  1. Nov 20, 2026
    • Tools that change things, listed without credentials: 0 to 6
  2. Nov 13, 2026
    • Tools that change things, listed without credentials: 10 to 0
    • RFC 9728 protected resource metadata: https://launchfiles.app/.well-known/oauth-protected-resource to https://launchfiles.app/.well-known/oauth-protected-resource/api/mcp
  3. Nov 6, 2026
    • Tools that change things, listed without credentials: 9 to 10
  4. Oct 29, 2026
    • Tools that change things, listed without credentials: 8 to 9

Findings

Matches of fixed checks, with the text they matched.

1 high4 warn
  • The description refers to "/.well-known/mcp.json".

    Matched text

    description: "...obe any live product URL for /llms.txt, /.well-known/mcp.json, /.well-known/mcp-registry-auth, /.well..."

    What this check looks for
  • The server marks "launchfiles_live_drift_check" read-only (readOnlyHint: true), and its own name, description or input give the class "write".

    Matched text

    annotations: {"readOnlyHint":true,"destructiveHint":false,"idempotentHint":true,"openWorldHint":true}; The description's first verb is "run": a word for a change.

    What this check looks for
  • The server marks "launchfiles_homepage_roast" read-only (readOnlyHint: true), and its own name, description or input give the class "write".

    Matched text

    annotations: {"readOnlyHint":true,"destructiveHint":false,"idempotentHint":true,"openWorldHint":true}; The description's first verb is "run": a word for a change.

    What this check looks for
  • The server marks "launchfiles_seo_audit" read-only (readOnlyHint: true), and its own name, description or input give the class "write".

    Matched text

    annotations: {"readOnlyHint":true,"destructiveHint":false,"idempotentHint":true,"openWorldHint":true}; The description's first verb is "run": a word for a change.

    What this check looks for
  • The server marks "launchfiles_ux_audit" read-only (readOnlyHint: true), and its own name, description or input give the class "write".

    Matched text

    annotations: {"readOnlyHint":true,"destructiveHint":false,"idempotentHint":true,"openWorldHint":true}; The description's first verb is "run": a word for a change.

    What this check looks for

History

Changes to its tool definitions and to its remote endpoint, newest first.

  1. PostureRemote posture changed. Tools that change things, listed without credentials: 0 -> 6.View diff
    • Tools that change things, listed without credentials: 0 to 6
  2. Tools7 changed.~7 changedView diff
  3. Tools5 added.+5 addedView diff
  4. Tools2 added, 15 removed.+2 added−15 removedView diff
    • Added:launchfiles_live_drift_checkChanges things
    • Added:launchfiles_seo_indexing_statusOnly reads
    • Removed:get_portfolio_agent_feedback_summary
    • Removed:get_vertical_redesign_spec
    • Removed:launchfiles_billing_create_checkout
    • Removed:launchfiles_billing_list_providers
    • Removed:launchfiles_billing_poll_checkout
    • Removed:launchfiles_poll_agent_key
    • Removed:launchfiles_request_agent_key
    • Removed:launchfiles_standalone_deployment_trust_radar_free
    • Removed:launchfiles_standalone_design_ux_radar_free
    • Removed:launchfiles_standalone_page_draft_paid
    • Removed:launchfiles_standalone_page_draft_short
    • Removed:launchfiles_standalone_search_repair_radar_free
    • Removed:run_ux_radar_proof
    • Removed:submit_agent_feedback
    • Removed:validate_copy_manifest
  5. PostureRemote posture changed. Tools that change things, listed without credentials: 10 -> 0; RFC 9728 protected resource metadata: https://launchfiles.app/.well-known/oauth-protected-resource -> https://launchfiles.app/.well-known/oauth-protected…View diff
    • Tools that change things, listed without credentials: 10 to 0
    • RFC 9728 protected resource metadata: https://launchfiles.app/.well-known/oauth-protected-resource to https://launchfiles.app/.well-known/oauth-protected-resource/api/mcp
  6. Tools2 added, 5 changed.+2 added~5 changedView diff
    • Added:get_portfolio_agent_feedback_summaryOnly reads
    • Added:submit_agent_feedbackChanges things
    • Changed:get_vertical_redesign_specOnly readsdescriptioninputSchema
    • Changed:launchfiles_standalone_page_draft_paidChanges thingsinputSchema
    • Changed:launchfiles_standalone_page_draft_shortChanges thingsinputSchema
    • Changed:run_ux_radar_proofChanges thingsdescriptioninputSchema
    • Changed:validate_copy_manifestOnly readsdescriptioninputSchema
  7. PostureRemote posture changed. Tools that change things, listed without credentials: 9 -> 10.View diff
    • Tools that change things, listed without credentials: 9 to 10
  8. Tools3 added.+3 addedView diff
    • Added:get_vertical_redesign_specOnly reads
    • Added:run_ux_radar_proofChanges things
    • Added:validate_copy_manifestOnly reads
  9. PostureRemote posture changed. Tools that change things, listed without credentials: 8 -> 9.View diff
    • Tools that change things, listed without credentials: 8 to 9

Install

Pinned to version 2.2.1. Values in angle brackets are yours to fill in.

claude mcp add --transport http launchfiles https://launchfiles.app/api/mcp
claude mcp add --transport http launchfiles https://launchfiles.app/api/mcp

Run in a terminal.

Claude Code permissions

Allow the reads, ask before a change or a way out, deny the deletes. Paste into .claude/settings.json.

.claude/settings.json
{
  "permissions": {
    "allow": [],
    "ask": [
      "mcp__launchfiles__launchfiles_seo_indexing_status",
      "mcp__launchfiles__launchfiles_live_drift_check",
      "mcp__launchfiles__launchfiles_homepage_roast",
      "mcp__launchfiles__launchfiles_seo_audit",
      "mcp__launchfiles__launchfiles_ux_audit",
      "mcp__launchfiles__launchfiles_domain_horizon_memory",
      "mcp__launchfiles__launchfiles_mcp_registry_readiness"
    ],
    "deny": []
  }
}

Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. A read that can send data out (it takes a URL, say) asks first too. It assumes the server is installed as launchfiles. Review it before you use it.

Capability tags behind 7 rules
  • mcp__launchfiles__launchfiles_seo_indexing_status untrusted-input, outbound
  • mcp__launchfiles__launchfiles_live_drift_check untrusted-input, outbound
  • mcp__launchfiles__launchfiles_homepage_roast untrusted-input, outbound
  • mcp__launchfiles__launchfiles_seo_audit untrusted-input, outbound
  • mcp__launchfiles__launchfiles_ux_audit untrusted-input, outbound
  • mcp__launchfiles__launchfiles_domain_horizon_memory untrusted-input, outbound
  • mcp__launchfiles__launchfiles_mcp_registry_readiness untrusted-input, outbound

Pin

Keep the decision: fail CI when the tools change, follow every change, or show a badge.

Pin in CI

Fail a build when the tools you reviewed are not the tools the server serves today.

curl -s "https://radar.anlyon.com/api/v1/servers/app.launchfiles/launchfiles/verify?hash=c10ae62fdc4ee1dc368eae79626f671969ed53ada90bc43cc6c96cb9eb3a6203" | jq -e '.changed == false'

Pinned hash c10ae62fdc4e, from Nov 16, 2026, 08:17 UTC.

Watch

Get told when its tools change: a new tool, a new description, a new class.

https://radar.anlyon.com/servers/app.launchfiles/launchfiles/changes.xml

An Atom feed. Works in any feed reader or Slack's RSS app.

Badge

Anlyon Radar badge for app.launchfiles/launchfiles
[![Anlyon Radar](https://radar.anlyon.com/badge/app.launchfiles/launchfiles.svg)](https://radar.anlyon.com/servers/app.launchfiles/launchfiles)

Source: MCP Registry · repository. Synced Nov 16, 2026, 08:17 UTC.

LaunchFiles MCP server: questions and answers

Answered from the scan above, not from the publisher's description.

Is the LaunchFiles MCP server safe?

No scan can promise that. What its definitions show: 7 tools, 6 of which can change, send or delete something, and 5 findings (1 high) from fixed checks. Allow the reads, ask before each change, and deny the deletes; the permissions block on this page does that.

Can the LaunchFiles MCP server delete data?

No tool is classed as destructive: going by their definitions, none of them deletes, cancels or revokes anything.

Can the LaunchFiles MCP server do things that cannot be undone?

No tool is classed as irreversible: none of them sends, pays, publishes or merges, going by their definitions.

What tools does the LaunchFiles MCP server have?

7 tools: 6 write, 1 read. launchfiles_live_drift_check, launchfiles_homepage_roast, launchfiles_seo_audit, launchfiles_ux_audit, launchfiles_domain_horizon_memory, launchfiles_mcp_registry_readiness and launchfiles_seo_indexing_status.

Does the LaunchFiles MCP server need sign-in or OAuth?

Its remote endpoint listed its tools to an anonymous client, without sign-in.

Does the LaunchFiles MCP server send data to outside services?

7 tools can carry data out (it sends, posts or publishes, or takes a recipient, channel or URL): launchfiles_seo_indexing_status, launchfiles_live_drift_check, launchfiles_homepage_roast, launchfiles_seo_audit, launchfiles_ux_audit, launchfiles_domain_horizon_memory and 1 more.

Has the LaunchFiles MCP server changed its tools?

Yes, 5 times since Anlyon Radar started tracking it, most recently on Nov 16, 2026. Every change is on this page and in its Atom feed.