MCP servers observed by Lowdown
ai.letsship/ship MCP server: daily status and tool changes
Answered initialize and tools/list on all 21 daily checks recorded in the last 30 days (2026-10-29 to 2026-11-18); 100 tools listed. MCP Registry declaration recorded; observed daily by Lowdown Scanner since 2026-10-29; tool definitions last changed on 2026-11-15 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:ai.letsship/ship
Before installing or connecting: GET https://lowdown-proxy.vercel.app/api/reputation/mcp:ai.letsship/ship?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: 21
- Answered initialize and tools/list: 21
- Required authentication: 0
- No response: 0
- Remotes differed: 0
Does it require authentication?
It did not return HTTP 401/403 on any of the 21 observed days. Lowdown checks without credentials.
Did its tools change recently?
Tool definitions changed on 7 of 20 compared days.
- 2026-11-18: server version changed
- 2026-11-17: server version changed
- 2026-11-15: input or output schemas changed, descriptions changed, tool names changed, server version changed; tool count 99 → 100
- 2026-11-14: input or output schemas changed, server version changed
- 2026-11-13: input or output schemas changed, descriptions changed, server version changed
What tools does it list?
100 tools on 2026-11-18:
activate_sandbox_template_versionadd_site_domainanswer_qa_checkpointapprove_mission_ceilingarchive_missionbind_mcp_serverbuild_sandbox_templatecancel_project_transferclear_agents_overridecreate_missioncreate_scheduled_taskcreate_sitedecline_missiondelete_sandbox_registrydelete_sandbox_templatedelete_scheduled_taskdelete_sitedestroy_environmentdismiss_noticeget_agent_runget_agent_run_logsget_agents_overrideget_artifactget_billingget_environmentget_missionget_noticesget_projectget_project_transferget_sandbox_build_logget_sandbox_capacityget_scheduled_taskget_setup_progressget_siteget_site_database_exportget_site_usagehealthzinspect_missionlist_agent_runslist_artifactslist_billing_ledgerlist_brand_presetslist_credit_offerslist_environmentslist_mcp_bindingslist_mcp_serverslist_missionslist_orgslist_projectslist_sandbox_registrieslist_sandbox_starterslist_sandbox_template_versionslist_sandbox_templateslist_scheduled_task_runslist_scheduled_task_templateslist_scheduled_taskslist_site_database_exportslist_site_deployslist_site_domainslist_site_starterslist_site_templateslist_site_waitlistlist_sitesmark_setup_stepmerge_missionpause_missionpublish_starter_siterefresh_mcp_server_toolsremove_site_domainremove_site_waitlist_entryreport_setup_blockerrequest_more_creditsresume_missionretry_first_site_wordsretry_site_publishrollback_siterun_scheduled_tasksave_sandbox_registrysave_sandbox_templatesend_mission_instructionset_agents_overrideset_mcp_config_pathset_mission_auto_mergeset_mission_dispositionstart_credit_checkoutstart_mcp_server_oauthstart_missionstart_site_database_exportstop_agent_runstop_missiontransfer_project_repositoryunarchive_missionunbind_mcp_serverupdate_projectupdate_scheduled_taskupdate_siteupdate_team_subscriptionverify_site_domainwatch_agent_runwhoami
MCP Registry declaration
- Registry name:
ai.letsship/ship - Declared version: 0.24.0
- Status: active
- Declared hosts:
mcp.letsship.ai
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:ai.letsship/ship", "menu": "install-check"}. The same record without MCP: GET https://lowdown-proxy.vercel.app/api/reputation/mcp:ai.letsship/ship?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).