Home / MCP registry index / app.launchfiles/launchfiles
Launchfiles
app.launchfiles/launchfiles in the official MCP registry.
Endpoint https://launchfiles.app/api/mcp.
The registry describes it as: Launchfiles hosted MCP: free page radars (design UX, search repair, deploy trust) + workspace tools.
We read its 10 tools on 2026-10-22. Nothing in them matched our tool-poisoning rules. It also sets server instructions, text a client puts in front of the model on connect; those were read too.
A clean read means these rules found nothing, not that the server is harmless. A server can change its tools at any time, which is why the index reads it again every week.
Tools it advertises
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 launchfiles_billing_poll_checkout launchfiles_request_agent_key launchfiles_poll_agent_key launchfiles_standalone_page_draft_paid launchfiles_standalone_page_draft_short
Run this server? Show the check in your README
The badge reflects the latest weekly read: 
[](https://lazaretto.dev/mcp-registry/app-launchfiles-launchfiles)How this was checked
Lazaretto connects to the endpoint the way any MCP client does, asks the server to introduce itself and list its tools, and reads every name, description, parameter schema and server instruction for tool poisoning: hidden directive blocks, orders to read local secrets, parameters built to carry secrets or the conversation out, orders that redirect another server's tools, and invisible characters. It never calls a tool. What we found across the registry.
To run the same check every time Claude Code adds a server, install the free lazaretto-guard plugin. Browse every server in the index.