MCP servers observed by Lowdown
app.launchfiles/launchfiles MCP server: daily status and tool changes
Answered initialize and tools/list on the last 5 consecutive daily checks (2026-11-14 to 2026-11-18); 7 tools listed. 29 of 30 observed days in the last 30 had this result. MCP Registry declaration recorded; observed daily by Lowdown Scanner since 2026-10-19; tool definitions last changed on 2026-11-16 after 1 days without change; no agent-reported interactions.
Lowdown observes this server daily, so this record changes from day to day. A copy older than 1 day may be outdated. Current record (JSON): GET https://lowdown-proxy.vercel.app/api/reputation/mcp:app.launchfiles/launchfiles
Before installing or connecting: GET https://lowdown-proxy.vercel.app/api/reputation/mcp:app.launchfiles/launchfiles?menu=install-check · other questions: menu
Does it respond?
Latest daily check: 2026-11-18: the server answered initialize and tools/list.
- Observed days in the last 30: 30
- Answered initialize and tools/list: 29
- Required authentication: 0
- No response: 1
- Remotes differed: 0
Does it require authentication?
It did not return HTTP 401/403 on any of the 30 observed days. Lowdown checks without credentials.
Did its tools change recently?
Tool definitions changed on 8 of 29 compared days.
- 2026-11-17: server version changed
- 2026-11-16: input or output schemas changed, descriptions changed, tool names changed, server version changed; tool count 2 → 7
- 2026-11-15: input or output schemas changed, descriptions changed, tool names changed; tool count 1 → 2
- 2026-11-14: input or output schemas changed, descriptions changed, tool names changed, server version changed; tool count 15 → 1
- 2026-11-11: input or output schemas changed
What tools does it list?
7 tools on 2026-11-18:
launchfiles_domain_horizon_memorylaunchfiles_homepage_roastlaunchfiles_live_drift_checklaunchfiles_mcp_registry_readinesslaunchfiles_seo_auditlaunchfiles_seo_indexing_statuslaunchfiles_ux_audit
MCP Registry declaration
- Registry name:
app.launchfiles/launchfiles - Declared version: 2.2.1
- Status: active
- Declared hosts:
launchfiles.app
Before installing: how to check
From an agent: add the remote MCP server https://lowdown-proxy.vercel.app/mcp (streamable HTTP, no authentication) and call get_lowdown with {"target": "mcp:app.launchfiles/launchfiles", "menu": "install-check"}. The same record without MCP: GET https://lowdown-proxy.vercel.app/api/reputation/mcp:app.launchfiles/launchfiles?menu=install-check
The same facts in machine-readable form are in this page's <script type="application/json" id="lowdown-evidence"> block (schema lowdown.evidence-snapshot v1).