Home / MCP registry index / bot.ai-beauty/beautyos

BeautyOS by AI Beauty Bot

bot.ai-beauty/beautyos in the official MCP registry. Endpoint https://agents.ai-beauty.bot/beauty-os/mcp. Source: github.com/ai-beauty-bot/beauty-os-skill.

The registry describes it as: Free salon CRM: services, staff, clients, online booking and an optional AI receptionist.

We read its 74 tools on 2026-11-16. 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 about every two weeks.

Connect it

The endpoint answers MCP over HTTP; that is how we read it. Add it to your client:

Claude Code
claude mcp add --transport http beautyos https://agents.ai-beauty.bot/beauty-os/mcp
Cursor: ~/.cursor/mcp.json
{
  "mcpServers": {
    "beautyos": {
      "url": "https://agents.ai-beauty.bot/beauty-os/mcp"
    }
  }
}
VS Code
code --add-mcp '{"name":"beautyos","type":"http","url":"https://agents.ai-beauty.bot/beauty-os/mcp"}'

Some servers ask you to sign in the first time a client connects, or want a key from the people who run them; the server's own docs say which.

Let Claude Code check servers as it adds them

With the free lazaretto-guard plugin installed, when Claude Code adds a server for you or writes one into an MCP config, the plugin reads the server's tools first and asks you if one of our rules matches. Install it, restart Claude Code, then ask it to run the command above.

Install lazaretto-guard
claude plugin marketplace add lazaretto-ai/lazaretto-plugins
claude plugin install lazaretto-guard@lazaretto-plugins

Tools it advertises

beautyos_members_list beautyos_member_invite_prepare beautyos_member_update_prepare beautyos_member_revoke_prepare beautyos_member_restore_prepare beautyos_member_resend_prepare beautyos_get_setup_readiness beautyos_complete_setup_prepare beautyos_get_knowledge beautyos_knowledge_create_prepare beautyos_knowledge_update_prepare beautyos_knowledge_delete_prepare beautyos_get_booking_settings beautyos_booking_settings_prepare beautyos_booking_publish_prepare beautyos_list_appointments beautyos_appointment_create_prepare beautyos_appointment_reschedule_prepare beautyos_appointment_cancel_prepare beautyos_find_clients beautyos_client_create_prepare beautyos_client_update_prepare beautyos_get_inbox beautyos_conversation_handoff_prepare beautyos_get_billing beautyos_get_analytics_report beautyos_analytics_report_prepare beautyos_salons_list beautyos_salon_get beautyos_salon_create_prepare beautyos_salon_update_prepare beautyos_catalog_get beautyos_staff_schedule_get beautyos_catalog_file_parse beautyos_catalog_source_read beautyos_catalog_import_prepare beautyos_service_create_prepare beautyos_service_update_prepare beautyos_staff_create_prepare beautyos_staff_update_prepare beautyos_staff_services_replace_prepare beautyos_staff_schedule_replace_prepare beautyos_staff_absence_create_prepare beautyos_agent_get beautyos_agent_configure_prepare beautyos_agent_activate_prepare beautyos_agent_pause_prepare beautyos_agent_test_prepare beautyos_channel_begin beautyos_channel_cancel beautyos_channel_activate beautyos_channel_pause beautyos_channel_disconnect beautyos_channel_status beautyos_channel_presentation beautyos_prepare_salon_change beautyos_prepare_service_change beautyos_prepare_staff_change beautyos_prepare_schedule_change beautyos_prepare_agent_change and 14 more

Tool changes

We compare every full read of this server with the one before. No change in what its tools say has been seen since we started keeping this record on 2026-10-30.

Fingerprint of its tools at our last full read (2026-11-16): 04f68b552c8bd75f. A client can hash the tools it is served the same way and compare; the full value and a hash per tool are in this page as JSON.

Rather than checking back: subscribe to this server's tool changes (a feed, no account and no address needed). Tool names and dates only, never what a tool says.

Run this server? Show the check in your README

The badge reflects the latest read: MCP tool check badge

Markdown
[![MCP tool check](https://lazaretto.dev/mcp-registry/bot-ai-beauty-beautyos/badge.svg)](https://lazaretto.dev/mcp-registry/bot-ai-beauty-beautyos)

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. How tool poisoning works. What we found across the registry. Check another server.

To run the same check every time Claude Code adds a server, install the free lazaretto-guard plugin. Browse every server in the index.

Related

CRM MCP servers

Obriym CRM
com.obriym-crm/mcp
164 tools, nothing matched
2026-11-13
workload.zero
de.workloadzero/mcp
158 tools, nothing matched
2026-11-17
Support Agent Admin by Nova (CIVAI)
co.civai.nova/support-agent-admin
98 tools, nothing matched
2026-11-05
LetsBot
net.letsbot/mcp
95 tools, nothing matched
2026-11-17
Autario
io.github.Autario/autario-mcp
84 tools, nothing matched
2026-11-11
GrowthKit Revenue Intelligence
tools.growthkit/revenue-intelligence
74 tools, nothing matched
2026-11-07