Copied. Paste it into Claude Code, Cursor or Codex:Fetch and follow the instructions at https://qamcp.dev/setup.md to test my MCP server.
Your AI finds your server in your project, tests it with QAmcp, explains what's wrong in plain words, fixes it with your OK, and tests again. Read the instructions
On their server. What you send to it goes to them.
What you need
Nothing: it answered without a login
Tools
2 tools
Its own safety labels
0 read-only, 2 with no label
Memory it takes
About 200 tokens of your AI's memory, just for its tool descriptions
Tokens are an estimate: the characters in its tool names, descriptions and inputs, divided by 4. The exact number depends on your AI model. Safety labels are what the server says about itself. From the daily test on 14 Nov 2026.
Is LaunchFiles MCP server safe?
None of the hidden-instruction wordings we know were found in its 2 tool descriptions.
0 of its 2 tools are labeled read-only; the others may change or send things.
Overall it scored 87/100 on 14 Nov 2026.
A test can only see what the server shows from outside, not what it does with your data behind the scenes. Connect servers from makers you trust.
What this test does not check
Its source code and packages.
What a tool quietly does behind the scenes, such as writing a file or calling another service.
Instructions hidden inside live tool answers. We only look for those in tool descriptions.
Hidden instructions worded in a way our list doesn't know yet.
Tools that could change something. Those are read, never run.
It lists no public code, so there is nothing to look up in GitHub Security Advisories or OSV.dev. QAmcp tests how a server behaves. It does not scan source code.
What it can do
2 tools, in the server's own words.
launchfiles_seo_indexing_status
Inspect live Google Search Console sitemap and indexing status for a domain or URL.
launchfiles_live_drift_check
Run a live HTTP, legal, sitemap, and Stripe Checkout / seller-brand drift inspection on a public website.
!Uses an older MCP version (2025-11-25). It works today, but it isn't on the July 2026 version (2026-07-28) yet.
note
!
Tools are labeled safe or dangerous1 warning
!2 of 2 tools have no safety label (read-only or dangerous): launchfiles_seo_indexing_status, launchfiles_live_drift_check
note
!
Follows MCP best practices (not scored yet)2 tips (not scored)
!2 tools not labeled read-only don't say whether running them twice is safe (idempotentHint): launchfiles_seo_indexing_status, launchfiles_live_drift_check
!2 tools don't say whether they reach outside services like the web (openWorldHint): launchfiles_seo_indexing_status, launchfiles_live_drift_check
note
✓
ConnectsConnected in 364 ms
pass
✓
Lists its toolsFound 2 tools
pass
✓
Every tool is describedAll 2 tools and their inputs are described
pass
✓
No known hidden instructionsNone of the hidden-instruction wordings we know were found in tool descriptions. New wordings can get past this check.
pass
✓
Fast enoughAll good
✓Connecting took 364 ms
✓Listing tools took 60 ms
pass
–
Tools work with good inputsNot tested
–launchfiles_seo_indexing_status: Not run: no safety label (if you own this server, test again in owner mode)
–launchfiles_live_drift_check: Not run: no safety label (if you own this server, test again in owner mode)
not tested
–
Bad inputs give a clean errorNot tested
not tested
–
Tools work togetherNo safe tool returned data to start a chain from, so chains were not tested (not counted either way)
not tested
–
No secrets leakedNo error messages to check
not tested
–
No known hidden instructions in tool answers (not scored yet)No tool answered, so there were no answers to read
not tested
Show this score on GitHub
Free for every server in the directory. Paste this into your README: the badge always shows the newest score, from the daily test, a test on our website or a Monitor test.