MCP servers observed by Lowdown
bot.ai-beauty/beautyos MCP server: daily status and tool changes
Answered initialize and tools/list on the only check recorded in the last 30 days (2026-11-17) (Lowdown checks this server every 3 days); 74 tools listed. MCP Registry declaration recorded; observed every 3 days by Lowdown Scanner since 2026-11-17; 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:bot.ai-beauty/beautyos
Before installing or connecting: GET https://lowdown-proxy.vercel.app/api/reputation/mcp:bot.ai-beauty/beautyos?menu=install-check · other questions: menu
Does it respond?
Latest daily check: 2026-11-17: the server answered initialize and tools/list.
- Observed days in the last 30: 1
- Answered initialize and tools/list: 1
- Required authentication: 0
- No response: 0
- Remotes differed: 0
Does it require authentication?
It did not return HTTP 401/403 on any of the 1 observed days. Lowdown checks without credentials.
Did its tools change recently?
Fewer than two days with a complete tools/list observation from the same remote, so nothing was compared.
What tools does it list?
74 tools on 2026-11-17:
beautyos_agent_activate_preparebeautyos_agent_configure_preparebeautyos_agent_getbeautyos_agent_pause_preparebeautyos_agent_testbeautyos_agent_test_preparebeautyos_analytics_report_preparebeautyos_apply_changebeautyos_appointment_cancel_preparebeautyos_appointment_create_preparebeautyos_appointment_reschedule_preparebeautyos_booking_publish_preparebeautyos_booking_settings_preparebeautyos_catalog_file_parsebeautyos_catalog_getbeautyos_catalog_import_preparebeautyos_catalog_source_getbeautyos_catalog_source_readbeautyos_channel_activatebeautyos_channel_beginbeautyos_channel_cancelbeautyos_channel_disconnectbeautyos_channel_pausebeautyos_channel_presentationbeautyos_channel_setup_linkbeautyos_channel_statusbeautyos_client_create_preparebeautyos_client_update_preparebeautyos_complete_setup_preparebeautyos_conversation_handoff_preparebeautyos_find_appointment_slotsbeautyos_find_clientsbeautyos_get_analyticsbeautyos_get_analytics_reportbeautyos_get_billingbeautyos_get_booking_settingsbeautyos_get_dashboardbeautyos_get_inboxbeautyos_get_knowledgebeautyos_get_onboardingbeautyos_get_operationbeautyos_get_profilebeautyos_get_setup_readinessbeautyos_knowledge_create_preparebeautyos_knowledge_delete_preparebeautyos_knowledge_update_preparebeautyos_list_appointmentsbeautyos_list_salonsbeautyos_member_invite_preparebeautyos_member_resend_preparebeautyos_member_restore_preparebeautyos_member_revoke_preparebeautyos_member_update_preparebeautyos_members_listbeautyos_prepare_agent_changebeautyos_prepare_catalog_importbeautyos_prepare_salon_changebeautyos_prepare_schedule_changebeautyos_prepare_service_changebeautyos_prepare_staff_changebeautyos_salon_create_preparebeautyos_salon_getbeautyos_salon_update_preparebeautyos_salons_listbeautyos_service_create_preparebeautyos_service_update_preparebeautyos_staff_absence_create_preparebeautyos_staff_create_preparebeautyos_staff_schedule_getbeautyos_staff_schedule_replace_preparebeautyos_staff_services_replace_preparebeautyos_staff_update_preparebeautyos_update_onboardingbeautyos_verify_first_reply
MCP Registry declaration
- Registry name:
bot.ai-beauty/beautyos - Declared version: 1.0.0
- Status: active
- Declared hosts:
agents.ai-beauty.bot
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:bot.ai-beauty/beautyos", "menu": "install-check"}. The same record without MCP: GET https://lowdown-proxy.vercel.app/api/reputation/mcp:bot.ai-beauty/beautyos?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).