Skip to content

MCP servers › bot.ai-beauty › beautyos

MCP server · registry snapshot 2026-11-16 · last tested 2026-11-16

beautyos MCP server

Registry name bot.ai-beauty/beautyos

BeautyOS by AI Beauty Bot — the publisher's title

by ai-beauty.bot · domain (the registry's namespace rule)repository owner on GitHub: ai-beauty-bot (organization)Source ↗Website ↗

Free salon CRM: services, staff, clients, online booking and an optional AI receptionist. — the publisher's description

5 of 5 record checks metRead-only · tools listed 2026-11-16version 1.0.0JavaScriptstreamable HTTP74 tools

Summary

bot.ai-beauty/beautyos is a remote MCP server listed in the official MCP registry at version 1.0.0, under the namespace of the domain ai-beauty.bot. Its linked repository is github.com/ai-beauty-bot/beauty-os-skill; GitHub reports its owner as ai-beauty-bot, an organization. On 2026-11-16 ProtocolProbe connected to it in read-only mode and read its inventory: 74 tools, 0 resources and 0 prompts.

Record checks

5 of 5 record checks met · 4 do not apply

  • met: Registry entry is active and says how to run it
  • met: Source repository link opens
  • met: Repository is not archived
  • met: Code pushed to the repository in the 90 days before our check
  • met: Repository publishes a security policy (SECURITY.md)
  • not applicable: Package names its licence with a standard (SPDX) identifier
  • not applicable: The version the registry lists can be installed and is not withdrawn
  • not applicable: npm package carries build provenance (attestation)
  • not applicable: No known critical or high advisory in the package or its dependencies
  • Not ranked by downloads: a remote server publishes no download figure
  • Not ranked by stars: 0 stars (ranked from 10)

From public records, not a safety rating. Each check with its reason · Is it safe to install?

Operate this server? Correct a fact · README badge · Run the checks yourself · Claim it

Key facts

Runs
remote (hosted by the publisher)
Transport
streamable HTTP
Your own values
none declared (not a guarantee)
Sign-in
none needed to open a session
Repository
public
Tools
74
Last tested
2026-11-16

Tool list size

25,510 tokens on Claude Opus 5.5

Added to every request that loads this server's tools (74 tools). Counted with Anthropic's token counter on 2026-11-16, from the tool list we read on 2026-11-16. Median across 28,560 counted servers: 2,657 tokens. How it is counted

How a client gets in

Connects without signing in

Read from the server's public metadata on 2026-11-16 (agents.ai-beauty.bot), in our read-only connection; no tool was called. It may have changed since. How it is read

Tool list at the three APIs

Not sent yet for this version (1.0.0).

Add to your client

Observed fact

This server accepted a session without any credential and lists 29 tools whose name or declaration suggests they change data (beautyos_member_update_prepare, beautyos_member_revoke_prepare, beautyos_knowledge_create_prepare, beautyos_knowledge_update_prepare, beautyos_knowledge_delete_prepare and 24 more). That is our reading of the names; we did not call them. Source: our connection, 2026-11-16.

How fresh this is

Live-tested
yes, a real session (not a text-only review)
Last tested
2026-11-16
Mode
read-only (no tool calls)
Latest version
1.0.0, published 2026-11-16 (registry, as of the 2026-11-16 snapshot)
First listed version
2026-11-16 (earliest version still in the registry; older removed versions would be earlier)
Registry data
snapshot 2026-11-16
Package and repository
checked 2026-11-16
Engine
mcp-runtime-engine@0.1.0 · sdk@1.32.0

Dead or stale signals

None found in the records we hold

Looked for and not found: deprecated in the registry; repository link does not open; repository archived; no push in over 365 days. Does not apply: listed version cannot be installed or is withdrawn. Each line is a dated fact from a public record. It does not say whether the server still works, and a record can change after the date shown.

Changes since the last refresh

New in the registry: not in the list of 2026-11-15, listed on 2026-11-16 with version 1.0.0 (published 2026-11-16).

Source: the official MCP Registry list on 2026-11-15 and on 2026-11-16.

What it is

What does this server offer?

Observed inventory
74tools
0resources
0prompts

None of its 74 tools are described as changing anything. For 74 the reading was uncertain, so no mark is shown.

  • beautyos_members_list

    “Read memberships, exact emails, roles, invitation status, retry eligibility and calendar bindings for salonId.”

    Publisher declares: read-only yes · destructive no · idempotent yes · open-world yes

    1 input, 1 required
    • salonIdstringrequired
  • beautyos_member_invite_prepare

    “Invite a NEW BeautyOS member by email.”

    Publisher declares: read-only no · destructive no · idempotent no · open-world yes

    8 inputs, 3 required
    • emailstringrequired
    • displayNamestring or null
    • whatsappPhonestring or null
    • rolestringrequired
    • accessProfilestring
    • staffIdstring or null
    • createStaffboolean
    • salonIdstringrequired
  • beautyos_member_update_prepare

    “Change an existing BeautyOS member role/profile/calendar.”

    Publisher declares: read-only no · destructive no · idempotent no · open-world yes

    5 inputs, 5 required
    • salonIdstringrequired
    • memberIdstringrequired
    • rolestringrequired
    • accessProfilestringrequired
    • staffIdstring or nullrequired
  • beautyos_member_revoke_prepare

    “Revoke BeautyOS access for the resolved memberId while retaining the employee and calendar.”

    Publisher declares: read-only no · destructive yes · idempotent no · open-world yes

    2 inputs, 2 required
    • salonIdstringrequired
    • memberIdstringrequired
  • beautyos_member_restore_prepare

    “Restore a revoked member with the same rights and employee.”

    Publisher declares: read-only no · destructive no · idempotent no · open-world yes

    2 inputs, 2 required
    • salonIdstringrequired
    • memberIdstringrequired
  • beautyos_member_resend_prepare

    “Resend an expired or undelivered invitation for an existing member with canRetryInvitation=true.”

    Publisher declares: read-only no · destructive no · idempotent no · open-world yes

    2 inputs, 2 required
    • salonIdstringrequired
    • memberIdstringrequired
  • beautyos_get_setup_readiness

    “Use this to review required salon-data readiness.”

    Publisher declares: read-only no · destructive no · idempotent no · open-world yes

    1 input, 1 required
    • salonIdstringrequired
  • beautyos_complete_setup_prepare

    “Use this to preview completing CRM setup after salon data is ready.”

    Publisher declares: read-only no · destructive no · idempotent no · open-world yes

    1 input, 1 required
    • salonIdstringrequired
  • beautyos_get_knowledge

    “Use this to read salon FAQs, policies and promotions.”

    Publisher declares: read-only yes · destructive no · idempotent yes · open-world yes

    3 inputs, 1 required
    • salonIdstringrequired
    • limitinteger
    • offsetinteger
  • beautyos_knowledge_create_prepare

    “Use this to preview a new FAQ, policy or promotion.”

    Publisher declares: read-only no · destructive no · idempotent no · open-world yes

    2 inputs, 2 required
    • salonIdstringrequired
    • entryobjectrequired
  • beautyos_knowledge_update_prepare

    “Use this to preview edits to an existing knowledge entry.”

    Publisher declares: read-only no · destructive no · idempotent no · open-world yes

    4 inputs, 3 required
    • salonIdstringrequired
    • entryIdstringrequired
    • offsetinteger
    • patchobjectrequired
  • beautyos_knowledge_delete_prepare

    “Use this to preview removal of an entry.”

    Publisher declares: read-only no · destructive yes · idempotent no · open-world yes

    3 inputs, 2 required
    • salonIdstringrequired
    • entryIdstringrequired
    • offsetinteger
Show 62 more tools
  • beautyos_get_booking_settings

    “Use this to review online-booking settings, including bookingStart and appearance, readiness and the public URL.”

    Publisher declares: read-only no · destructive no · idempotent no · open-world yes

    1 input, 1 required
    • salonIdstringrequired
  • beautyos_booking_settings_prepare

    “Use this to preview online-booking text, address slug, time windows, cancellation rules, bookingStart (service or staff), and appearance (logoUrl, coverUrl, galleryUrls, accentColor).”

    Publisher declares: read-only no · destructive no · idempotent no · open-world yes

    2 inputs, 2 required
    • salonIdstringrequired
    • patchobjectrequired
  • beautyos_booking_publish_prepare

    “Use this to preview publication or unpublication of online booking.”

    Publisher declares: read-only no · destructive yes · idempotent no · open-world yes

    2 inputs, 2 required
    • salonIdstringrequired
    • enabledbooleanrequired
  • beautyos_list_appointments

    “Use this to review appointments over an explicit period of at most 90 days.”

    Publisher declares: read-only yes · destructive no · idempotent yes · open-world yes

    Takes no inputs.

  • beautyos_appointment_create_prepare

    “Use this to preview a booking for an existing verified client, staff member and services.”

    Publisher declares: read-only no · destructive no · idempotent no · open-world yes

    2 inputs, 2 required
    • salonIdstringrequired
    • appointmentobjectrequired
  • beautyos_appointment_reschedule_prepare

    “Use this to preview moving a selected booking.”

    Publisher declares: read-only no · destructive no · idempotent no · open-world yes

    4 inputs, 4 required
    • salonIdstringrequired
    • appointmentIdstringrequired
    • currentStartsAtstringrequired
    • patchobjectrequired
  • beautyos_appointment_cancel_prepare

    “Use this to preview cancelling a selected booking.”

    Publisher declares: read-only no · destructive yes · idempotent no · open-world yes

    4 inputs, 3 required
    • salonIdstringrequired
    • appointmentIdstringrequired
    • currentStartsAtstringrequired
    • reasonstring
  • beautyos_find_clients

    “Use this to find an existing client by a user-supplied name or contact search.”

    Publisher declares: read-only yes · destructive no · idempotent yes · open-world yes

    4 inputs, 2 required
    • salonIdstringrequired
    • limitinteger
    • offsetinteger
    • searchstringrequired
  • beautyos_client_create_prepare

    “Use this to preview creation of a client from user-supplied details.”

    Publisher declares: read-only no · destructive no · idempotent no · open-world yes

    2 inputs, 2 required
    • salonIdstringrequired
    • clientobjectrequired
  • beautyos_client_update_prepare

    “Use this to preview changes to the selected client found with the supplied search.”

    Publisher declares: read-only no · destructive no · idempotent no · open-world yes

    4 inputs, 4 required
    • salonIdstringrequired
    • clientIdstringrequired
    • searchstringrequired
    • patchobjectrequired
  • beautyos_get_inbox

    “Use this to review a page of salon conversations, optionally only those needing human attention.”

    Publisher declares: read-only yes · destructive no · idempotent yes · open-world yes

    5 inputs, 1 required
    • salonIdstringrequired
    • limitinteger
    • offsetinteger
    • attentionOnlyboolean
    • includePreviewboolean
  • beautyos_conversation_handoff_prepare

    “Use this to preview transferring one selected conversation to a human.”

    Publisher declares: read-only no · destructive no · idempotent no · open-world yes

    3 inputs, 2 required
    • salonIdstringrequired
    • conversationIdstringrequired
    • offsetinteger
  • beautyos_get_billing

    “Use this to read the current plan, trial, client usage, monthly Copilot/report allowances with reset dates and feature entitlements.”

    Publisher declares: read-only yes · destructive no · idempotent yes · open-world yes

    1 input, 1 required
    • salonIdstringrequired
  • beautyos_get_analytics_report

    “Use this to read an existing AI growth report for the chosen period and staff/service filters.”

    Publisher declares: read-only yes · destructive no · idempotent yes · open-world yes

    4 inputs, 1 required
    • salonIdstringrequired
    • rangeDaysnumber
    • staffIdstring
    • serviceId
  • beautyos_analytics_report_prepare

    “Use this to preview generation of an AI growth report with the existing BeautyOS calculations.”

    Publisher declares: read-only no · destructive no · idempotent no · open-world yes

    4 inputs, 1 required
    • salonIdstringrequired
    • rangeDaysnumber
    • staffIdstring
    • serviceId
  • beautyos_salons_list

    “List only linked salons for which live membership still permits access.”

    Publisher declares: read-only yes · destructive no · idempotent yes · open-world yes

    Takes no inputs.

  • beautyos_salon_get

    “Read salon details and current data-source capabilities.”

    Publisher declares: read-only yes · destructive no · idempotent yes · open-world yes

    1 input, 1 required
    • salonIdstringrequired
  • beautyos_salon_create_prepare

    “Start CRM setup with salon, catalog, staff, channel and agent permissions granted together at initial authorization.”

    Publisher declares: read-only no · destructive yes · idempotent no · open-world yes

    7 inputs, 4 required
    • namestringrequired
    • phonestring or null
    • addressstring or null
    • timezonestringrequired
    • currencystringrequired
    • localestring
    • creationKeystringrequired
  • beautyos_salon_update_prepare

    “Preview exact local and platform profile edits.”

    Publisher declares: read-only no · destructive yes · idempotent no · open-world yes

    2 inputs, 2 required
    • salonIdstringrequired
    • patchobjectrequired
  • beautyos_catalog_get

    “Read native services, staff, assignments and weekly schedules.”

    Publisher declares: read-only yes · destructive no · idempotent yes · open-world yes

    1 input, 1 required
    • salonIdstringrequired
  • beautyos_staff_schedule_get

    “Read dated staff schedule where the current provider supports it; native mode returns weekly rules and appointment conflicts.”

    Publisher declares: read-only yes · destructive no · idempotent yes · open-world yes

    Takes no inputs.

  • beautyos_catalog_file_parse

    “Use this from the app to parse a bounded CSV, TSV or XLSX file.”

    Publisher declares: read-only no · destructive no · idempotent no · open-world yes

    2 inputs, 2 required
    • salonIdstringrequired
    • fileobjectrequired
  • beautyos_catalog_source_read

    “Use this to extract text from a public website url for the catalog of salonId.”

    Publisher declares: read-only no · destructive no · idempotent no · open-world yes

    2 inputs, 2 required
    • salonIdstringrequired
    • urlstringrequired
  • beautyos_catalog_import_prepare

    “Use this to prepare importing structured rows of services and staff into salonId.”

    Publisher declares: read-only no · destructive no · idempotent no · open-world yes

    3 inputs, 2 required
    • salonIdstringrequired
    • rowsarrayrequired
    • sourceobject
  • beautyos_service_create_prepare

    “Use this when the owner wants to add one service to salonId.”

    Publisher declares: read-only no · destructive no · idempotent no · open-world yes

    2 inputs, 2 required
    • salonIdstringrequired
    • serviceobjectrequired
  • beautyos_service_update_prepare

    “Use this to update an existing serviceId in salonId.”

    Publisher declares: read-only no · destructive no · idempotent no · open-world yes

    3 inputs, 3 required
    • salonIdstringrequired
    • serviceIdstringrequired
    • patchobjectrequired
  • beautyos_staff_create_prepare

    “Use this to add one staff member from the staff object to salonId.”

    Publisher declares: read-only no · destructive no · idempotent no · open-world yes

    2 inputs, 2 required
    • salonIdstringrequired
    • staffobjectrequired
  • beautyos_staff_update_prepare

    “Use this to edit an existing staffId in salonId.”

    Publisher declares: read-only no · destructive no · idempotent no · open-world yes

    3 inputs, 3 required
    • salonIdstringrequired
    • staffIdstringrequired
    • patchobjectrequired
  • beautyos_staff_services_replace_prepare

    “Use this to fully replace service assignments for staffId in salonId with serviceIds.”

    Publisher declares: read-only no · destructive no · idempotent no · open-world yes

    3 inputs, 3 required
    • salonIdstringrequired
    • staffIdstringrequired
    • serviceIdsarrayrequired
  • beautyos_staff_schedule_replace_prepare

    “Use this to fully replace weekly availability for staffId in salonId with rules containing weekday and minute boundaries.”

    Publisher declares: read-only no · destructive no · idempotent no · open-world yes

    3 inputs, 3 required
    • salonIdstringrequired
    • staffIdstringrequired
    • rulesarrayrequired
  • beautyos_staff_absence_create_prepare

    “Use this to plan an absence for staffId in salonId between startsAt and endsAt.”

    Publisher declares: read-only no · destructive no · idempotent no · open-world yes

    Takes no inputs.

  • beautyos_agent_get

    “Read the existing text-agent configuration and current activation state.”

    Publisher declares: read-only yes · destructive no · idempotent yes · open-world yes

    1 input, 1 required
    • salonIdstringrequired
  • beautyos_agent_configure_prepare

    “Use this when the user wants to change the salon text AI receptionist settings.”

    Publisher declares: read-only no · destructive yes · idempotent no · open-world yes

    2 inputs, 2 required
    • salonIdstringrequired
    • patchobjectrequired
  • beautyos_agent_activate_prepare

    “Use this when the user wants to enable the salon text AI receptionist.”

    Publisher declares: read-only no · destructive yes · idempotent no · open-world yes

    2 inputs, 1 required
    • salonIdstringrequired
    • skipTestboolean
  • beautyos_agent_pause_prepare

    “Use this when the user wants to pause automatic replies from the salon text AI receptionist.”

    Publisher declares: read-only no · destructive yes · idempotent no · open-world yes

    1 input, 1 required
    • salonIdstringrequired
  • beautyos_agent_test_prepare

    “Use this when the user requests an optional isolated text AI receptionist test.”

    Publisher declares: read-only no · destructive yes · idempotent no · open-world yes

    2 inputs, 2 required
    • salonIdstringrequired
    • messagestringrequired
  • beautyos_channel_begin

    “Prepare connecting the selected salon channel, keeping AI inactive.”

    Publisher declares: read-only no · destructive yes · idempotent no · open-world yes

    4 inputs, 3 required
    • salonIdstringrequired
    • channelTypestringrequired
    • operationKeystringrequired
    • replaceAttemptIdstring
  • beautyos_channel_cancel

    “Prepare cancelling a connection attempt.”

    Publisher declares: read-only no · destructive yes · idempotent no · open-world yes

    3 inputs, 3 required
    • salonIdstringrequired
    • channelTypestringrequired
    • attemptIdstringrequired
  • beautyos_channel_activate

    “Prepare enabling AI on a verified connected channel.”

    Publisher declares: read-only no · destructive yes · idempotent no · open-world yes

    3 inputs, 2 required
    • salonIdstringrequired
    • channelTypestringrequired
    • skipTestboolean
  • beautyos_channel_pause

    “Prepare pausing AI; keep the channel connected.”

    Publisher declares: read-only no · destructive yes · idempotent no · open-world yes

    2 inputs, 2 required
    • salonIdstringrequired
    • channelTypestringrequired
  • beautyos_channel_disconnect

    “Prepare actual provider disconnection; existing credentials and message access may be removed.”

    Publisher declares: read-only no · destructive yes · idempotent no · open-world yes

    2 inputs, 2 required
    • salonIdstringrequired
    • channelTypestringrequired
  • beautyos_channel_status

    “Read fresh provider connection and separate AI activation state.”

    Publisher declares: read-only yes · destructive no · idempotent yes · open-world yes

    3 inputs, 2 required
    • salonIdstringrequired
    • channelTypestringrequired
    • attemptIdstring
  • beautyos_channel_presentation

    “App-only transient QR or trusted external setup link for the bound attempt.”

    Publisher declares: read-only yes · destructive no · idempotent yes · open-world yes

    3 inputs, 3 required
    • salonIdstringrequired
    • channelTypestringrequired
    • attemptIdstringrequired
  • beautyos_prepare_salon_change

    “App-only adapter for the salon form.”

    Publisher declares: read-only no · destructive no · idempotent no · open-world yes

    3 inputs, 2 required
    • actionstringrequired
    • salonIdstring
    • inputobjectrequired
  • beautyos_prepare_service_change

    “App-only adapter for the service form in the selected salonId.”

    Publisher declares: read-only no · destructive no · idempotent no · open-world yes

    3 inputs, 2 required
    • actionstringrequired
    • salonIdstring
    • inputobjectrequired
  • beautyos_prepare_staff_change

    “App-only adapter for the team form in the selected salonId.”

    Publisher declares: read-only no · destructive no · idempotent no · open-world yes

    3 inputs, 2 required
    • actionstringrequired
    • salonIdstring
    • inputobjectrequired
  • beautyos_prepare_schedule_change

    “App-only adapter for the calendar in the selected salonId.”

    Publisher declares: read-only no · destructive no · idempotent no · open-world yes

    3 inputs, 2 required
    • actionstringrequired
    • salonIdstring
    • inputobjectrequired
  • beautyos_prepare_agent_change

    “App-only adapter for AI settings in the selected salonId.”

    Publisher declares: read-only no · destructive no · idempotent no · open-world yes

    3 inputs, 2 required
    • actionstringrequired
    • salonIdstring
    • inputobjectrequired
  • beautyos_find_appointment_slots

    “Use this to find available times for selected existing native BeautyOS services and one staff member over at most 7 days.”

    Publisher declares: read-only yes · destructive no · idempotent yes · open-world yes

    Takes no inputs.

  • beautyos_get_analytics

    “Show visual analytics with charts when the user asks for salon analytics or charts; not a salon-setup follow-up.”

    Publisher declares: read-only yes · destructive no · idempotent yes · open-world yes

    4 inputs, 1 required
    • salonIdstringrequired
    • rangeDaysnumber
    • staffIdstring
    • serviceIdstring
  • beautyos_get_profile

    “Read a pairwise profile identifier and currently granted scope names, without email or credentials.”

    Publisher declares: read-only yes · destructive no · idempotent yes · open-world yes

    Takes no inputs.

  • beautyos_get_dashboard

    “Open the visual BeautyOS workspace only when the user explicitly asks to see or use it.”

    Publisher declares: read-only yes · destructive no · idempotent yes · open-world yes

    1 input
    • salonIdstring
  • beautyos_list_salons

    “List only explicitly linked salons with current access.”

    Publisher declares: read-only yes · destructive no · idempotent yes · open-world yes

    Takes no inputs.

  • beautyos_get_onboarding

    “Use first after connecting BeautyOS, without salonId, to read the current setup state.”

    Publisher declares: read-only yes · destructive no · idempotent yes · open-world yes

    1 input
    • salonIdstring
  • beautyos_update_onboarding

    “Save the selected setup step and assistance preference.”

    Publisher declares: read-only no · destructive yes · idempotent no · open-world yes

    4 inputs, 2 required
    • salonIdstringrequired
    • stepstringrequired
    • expectedRevisioninteger
    • assistanceNeededboolean
  • beautyos_prepare_catalog_import

    “App-only import adapter: forwards input.rows and optional source information to catalog preparation for the selected salonId, then saves a preview.”

    Publisher declares: read-only no · destructive no · idempotent no · open-world yes

    2 inputs, 2 required
    • salonIdstringrequired
    • inputobjectrequired
  • beautyos_apply_change

    “Apply only an existing reviewed preview with exact expectedVersion, confirmation:true and stable idempotencyKey.”

    Publisher declares: read-only no · destructive yes · idempotent yes · open-world yes

    4 inputs, 4 required
    • changeIdstringrequired
    • expectedVersionstringrequired
    • confirmationbooleanrequired
    • idempotencyKeystringrequired
  • beautyos_get_operation

    “Read an owned persistent preview or operation receipt and its external-step states in the conversation, without opening a workspace.”

    Publisher declares: read-only yes · destructive no · idempotent yes · open-world yes

    1 input, 1 required
    • operationIdstringrequired
  • beautyos_catalog_source_get

    “Read a bounded page of the persisted, untrusted source from an earlier file or website read.”

    Publisher declares: read-only yes · destructive no · idempotent yes · open-world yes

    4 inputs, 2 required
    • salonIdstringrequired
    • sourceIdstringrequired
    • offsetinteger
    • limitinteger
  • beautyos_agent_test

    “Prepare an isolated product-backend agent test.”

    Publisher declares: read-only no · destructive yes · idempotent no · open-world yes

    2 inputs, 2 required
    • salonIdstringrequired
    • messagestringrequired
  • beautyos_channel_setup_link

    “Use when a confirmed channel.begin receipt or fresh channel status reports a pending attempt with attemptId, or when the user asks to resume that attempt.”

    Publisher declares: read-only yes · destructive no · idempotent yes · open-world yes

    3 inputs, 3 required
    • salonIdstringrequired
    • channelTypestringrequired
    • attemptIdstringrequired
  • beautyos_verify_first_reply

    “Check recent real messaging channels for provider-confirmed assistant delivery.”

    Publisher declares: read-only yes · destructive no · idempotent yes · open-world yes

    1 input, 1 required
    • salonIdstringrequired

Each quoted sentence is the first sentence of the publisher’s own description. The kind of tool and the “changes data” mark are our AI model’s reading of that description, not something we tested: two differently worded runs had to agree, otherwise no label is shown, and nobody has checked them by hand. A tool without the “changes data” mark is described as only reading, searching or calculating, or the two runs did not agree. No tool was called. Read the publisher’s full description before relying on it. “Publisher declares” lists the hints the server itself sends with the tool (MCP annotations: read-only, destructive, idempotent, open-world); they are the publisher's claims, not checked by us. Inputs are the parameters in the tool's own input schema: name, declared type, whether it is required, and the first sentence of its description. Read 2026-11-16.

How well are its tools described?

Features #4 and #5

How clearly this server's own tool descriptions say what a tool does, and how consistent its tool list is. The first part is an AI model's yes/no reading of each description; the second part is counted. We do not turn it into a grade.

Descriptions

AI reading of each description

No AI reading was available for this server's tools (the two runs did not agree, or the listing was not reviewed).

Counted from the listing

Parameters with a description
0% of 180
Tools with a description
100% of 74
Typical description length
301 characters

The tool set

Counted from the listing

Tools
74
Size of the list
about 22,284 tokens for an agent to load (characters ÷ 4)
Naming
74 of 74 names use snake_case

AI reading: easy to mix up

No pair found.

The AI items cover 0 of 74 tools: for a tool where two differently worded runs disagreed, that item is left out. They were not checked by hand, and no tool was called. “Easy to mix up” means two tools whose names or descriptions overlap without saying how they differ; the AI found none, comparing tools within groups of 40. We do not rate whether the tool set is complete or whether side effects are spelled out, because our AI reading of those was not reliable enough.

How do I add it to my client?

Config from the registry entry

From the remote endpoint (Streamable HTTP)

We connected to this URL on 2026-11-16 (a read-only session: no tool was called).

Add to CursorAn install link in the format Cursor documents, holding the Cursor config below.

Claude Desktop or claude.ai
Settings → Connectors → Add custom connector, then paste:
https://agents.ai-beauty.bot/beauty-os/mcp
Cursor · .cursor/mcp.json in a project, or ~/.cursor/mcp.json
{
  "mcpServers": {
    "beautyos": {
      "url": "https://agents.ai-beauty.bot/beauty-os/mcp"
    }
  }
}
VS Code · .vscode/mcp.json
{
  "servers": {
    "beautyos": {
      "type": "http",
      "url": "https://agents.ai-beauty.bot/beauty-os/mcp"
    }
  }
}
VS Code (command line) · Bash or zsh terminal (macOS, Linux)
code --add-mcp '{"name":"beautyos","type":"http","url":"https://agents.ai-beauty.bot/beauty-os/mcp"}'
Claude Code
claude mcp add --transport http beautyos https://agents.ai-beauty.bot/beauty-os/mcp
Cline · cline_mcp_settings.json (Cline CLI: ~/.cline/data/settings/; in the editor: MCP Servers → Configure → Configure MCP Servers)
{
  "mcpServers": {
    "beautyos": {
      "type": "streamableHttp",
      "url": "https://agents.ai-beauty.bot/beauty-os/mcp",
      "disabled": false,
      "autoApprove": []
    }
  }
}
Gemini CLI · ~/.gemini/settings.json, or .gemini/settings.json in a project
{
  "mcpServers": {
    "beautyos": {
      "httpUrl": "https://agents.ai-beauty.bot/beauty-os/mcp"
    }
  }
}
OpenAI Codex · ~/.codex/config.toml, or .codex/config.toml in a trusted project
[mcp_servers.beautyos]
url = "https://agents.ai-beauty.bot/beauty-os/mcp"
Zed · Zed settings file (command: zed: open settings file)
{
  "context_servers": {
    "beautyos": {
      "url": "https://agents.ai-beauty.bot/beauty-os/mcp"
    }
  }
}
Try it in the MCP Inspector · runs on your machine, opens in your browser · Node 22.19+
npx @modelcontextprotocol/inspector@2.11.0 --server-url https://agents.ai-beauty.bot/beauty-os/mcp --transport http
  • The server runs on the operator's infrastructure; it may ask you to sign in when you first connect.
  • Zed's docs we read on 2026-10-26 describe remote servers by URL and do not name the transport.
  • The MCP Inspector lists the server's tools, resources and prompts; a tool you call there runs for real.

Built from the server's registry entry with each client's documented format (checked 2026-10-14; the Cursor link and the VS Code command 2026-10-19; the MCP Inspector command 2026-10-21; Cline, Gemini CLI, OpenAI Codex and Zed 2026-10-26). Values in < > are yours to fill in; this page never contains a key. Where the server needs a setting the entry does not declare, it can still fail to start.

What do the published files and outside lists say?

Read as text · nothing run · no tool called

Package files

  • MCP SDK in the package files. Not read yet: added with the next daily run.
  • Build workflow. Not read yet: added with the next daily run.

Outside lists

  • CVE records (NVD). No CVE record in the NVD feeds we read links this server's repository. Source: read 2026-11-16. This product uses the NVD API but is not endorsed or certified by the NVD.
  • GitHub advisories. No GitHub advisory names this entry's listed package. Source: read 2026-11-16. GitHub Advisory Database, CC BY 4.0
  • Docker MCP catalogue. Not in the Docker MCP catalogue on 2026-11-16. Source: read 2026-11-16.
  • Cline marketplace. Not in the Cline marketplace on 2026-11-16. Source: read 2026-11-16.

Own host

  • security.txt. No security.txt at https://agents.ai-beauty.bot/.well-known/ (HTTP 404, 2026-11-16). No security.txt at https://ai-beauty.bot/.well-known/ (HTTP 404, 2026-11-16). Source: agents.ai-beauty.bot/.well-known/security.txt · read 2026-11-16.
  • A2A agent card. No A2A agent card at https://agents.ai-beauty.bot/.well-known/ (HTTP 404, 2026-11-16). No A2A agent card at https://ai-beauty.bot/.well-known/ (HTTP 404, 2026-11-16). Source: agents.ai-beauty.bot/.well-known/agent-card.json · read 2026-11-16.

Read as text from published files and outside lists. Nothing was installed or run, and no tool was called. A fact, not a rating. How each fact is read

Does the registry listing match what we found?

Feature #6

The registry checks an entry when it is published (each new version), and nothing re-checks it on a schedule. A difference below is about the listing, not a judgement of the publisher.

Registry saysWe foundResultSource · date
Remote endpoint agents.ai-beauty.bot/beauty-os/mcpSession openedmatchesour test · 2026-11-16
No credential declared as requiredOpened a session without any credentialmatchesour test · 2026-11-16
Repository github.com/ai-beauty-bot/beauty-os-skillOpens publiclymatchesapi.github.com · 2026-11-16

Who made it?

Feature #7 · lineage

Facts about the publisher. We do not turn them into a trust score.

Namespace
bot.ai-beauty
GitHub owner
an organization (ai-beauty-bot)
Repository
github.com/ai-beauty-bot/beauty-os-skill
Stars
0
Repository age
0–30 days
Last push
0–30 days ago
Archived
no
Security policy
SECURITY.md

Source: the registry entry and api.github.com · 2026-11-16; security policy read from GitHub · 2026-11-16.

Publish this server? Run these checks against it yourself before release, from your own machine: a server the command starts, or your own server at its URL after a one-time proof that you control it: npx protocolprobe-selftest.

Choosing

Record checks

Public records · not a safety rating

5 of 5 record checks met · 4 do not apply

  • Not ranked by downloads: a remote server publishes no download figure
  • Not ranked by stars: 0 stars (ranked from 10)
  • MetRegistry entry is active and says how to run itActive, with a package or a remote address.
  • MetSource repository link opensThe linked GitHub repository is public.
  • MetRepository is not archivedNot archived.
  • MetCode pushed to the repository in the 90 days before our checkLast push 0-30 days before our check.
  • MetRepository publishes a security policy (SECURITY.md)SECURITY.md found.
  • Does not applyPackage names its licence with a standard (SPDX) identifierRemote server: it ships no package.
  • Does not applyThe version the registry lists can be installed and is not withdrawnRemote server: it ships no package.
  • Does not applynpm package carries build provenance (attestation)Remote server: it ships no package.
  • Does not applyNo known critical or high advisory in the package or its dependenciesRemote server: it ships no package.

Read from public records only: the registry entry, npm/PyPI, GitHub and advisory databases, checked 2026-11-16 (security policy 2026-11-16). No tool was called. Only “met” and “not met” are counted, so the total differs between servers; a check that does not apply or that we could not run is listed, never counted against it. It is not a safety rating, and the same rules apply to every server. How each check works · Leaderboards · How we stay neutral

Common questions about bot.ai-beauty/beautyos

Answered from the data above

Who publishes bot.ai-beauty/beautyos?

The registry ties the namespace bot.ai-beauty to the domain ai-beauty.bot; only its owner can publish under it. Its linked repository is github.com/ai-beauty-bot/beauty-os-skill; GitHub reports its owner as ai-beauty-bot, an organization. These are facts from the registry and GitHub, not a rating.

Is bot.ai-beauty/beautyos safe to install?

We do not rate servers as safe or unsafe. 5 of its 5 applicable record checks are met (facts from public records, each listed on this page). What the records show: Its source repository opens publicly. Its repository had a push in the last 90 days. These are facts with their sources on this page, not a safety guarantee, and we did not run its tools.

Does bot.ai-beauty/beautyos need an API key or sign-in?

It opened a session without any credential on 2026-11-16. The registry entry declares no required credential; no declaration is not a guarantee.

Has bot.ai-beauty/beautyos been security tested?

Partly. 3 of the 15 checks that apply to it were exercised. It accepted a session without any credential and lists tools whose names suggest they change data. We did not call them. ProtocolProbe publishes no security verdict for a named server.

Does bot.ai-beauty/beautyos publish a security policy?

Yes: its repository has a public security policy (github.com/ai-beauty-bot/beauty-os-skill/blob/HEAD/SECURITY.md). That is the publisher's statement, not permission for us to test the server, and we call none of its tools.

Where is the source code of bot.ai-beauty/beautyos?

In github.com/ai-beauty-bot/beauty-os-skill, which opens publicly.

Found this page useful?

Anonymous · no sign-in

A quick, anonymous reaction — no account, no email. One per kind from your browser. The tally updates when the page is next refreshed, and it is only a rough count, never a safety rating or a measured number of people.

Compare with another server

Side by side: registry entry, our read-only session, the tools and the 18 classification fields. Same values as each page; no score.

Security testing

What did we test, and what did we leave out?

18 checks · features #1, #2

Open without sign-in

It accepted a session without any credential and lists tools whose names suggest they change data. We did not call them. No security score is given; a check we did not run is never counted as passed.

The 18 checks at a glanceour test · 2026-11-16
  1. Inventory: exercised
  2. Hidden instructions: exercised
  3. Real execution: not run · our policy
  4. Secret leak: not run · nothing to check it against
  5. Internal addresses: not run · our policy
  6. Unconfirmed changes: not run · our policy
  7. Bad input: not run · our policy
  8. Model requests: not run · nothing to check it against
  9. Sensitive questions: not run · nothing to check it against
  10. Folder boundary: not run · our policy
  11. Log leaks: not run · nothing to check it against
  12. Hidden content: not run · nothing to check it against
  13. Fake assistant turns: not applicable
  14. Token passthrough: not applicable
  15. Token audience: not applicable
  16. Sign-in redirect: not run · our policy
  17. Consent handling: not testable from outside
  18. Sign-in metadata: exercised

3 exercised12 not run (reason given)3 not applicable

Each check ends in exactly one state: exercised, not run (with the reason), or not applicable (with the reason). 3 of the 15 checks that apply to it were exercised. We do not publish security-check outcomes for named servers. These 18 checks are separate from the record checks at the top of this page, which read public records only.

Exercised · 3
  • 1Inventory
    tool-list
    Reads the declared tools, resources and prompts.exercised
  • 2Hidden instructions
    description-poisoning
    Looks for hidden instructions in tool descriptions.exercised
  • 18Sign-in metadata
    oauth-url-scheme
    Checks the published sign-in metadata for unsafe URLs.exercised
Not run, with the reason · 12
  • 3Real execution
    real-execution
    Calls a tool and checks what really happens.This check calls the server's tools. ProtocolProbe calls no server's tools for anything it publishes, except for a server whose operator has claimed it and given permission (that server's page says so); an operator can run this check on their own server with our self-test command.not run · our policy
  • 4Secret leak
    canary-leak
    Plants a fake secret and checks whether it leaks.This check needs at least one successful tool call to have something to check, and no tool was called.not run · nothing to check it against
  • 5Internal addresses
    ssrf
    Checks whether a tool can be steered to internal addresses.This check calls the server's tools. ProtocolProbe calls no server's tools for anything it publishes, except for a server whose operator has claimed it and given permission (that server's page says so); an operator can run this check on their own server with our self-test command.not run · our policy
  • 6Unconfirmed changes
    write-without-confirmation
    Checks whether tools that change data act without asking.This check calls the server's tools. ProtocolProbe calls no server's tools for anything it publishes, except for a server whose operator has claimed it and given permission (that server's page says so); an operator can run this check on their own server with our self-test command.not run · our policy
  • 7Bad input
    error-handling
    Sends bad input and watches how the server answers.This check calls the server's tools. ProtocolProbe calls no server's tools for anything it publishes, except for a server whose operator has claimed it and given permission (that server's page says so); an operator can run this check on their own server with our self-test command.not run · our policy
  • 8Model requests
    sampling
    Checks whether the server asks the client's model to act for it.This check needs at least one successful tool call to have something to check, and no tool was called.not run · nothing to check it against
  • 9Sensitive questions
    elicitation-sensitive-data
    Checks whether the server asks users for sensitive data.This check needs at least one successful tool call to have something to check, and no tool was called.not run · nothing to check it against
  • 10Folder boundary
    root-boundary
    Checks whether the server reaches outside the folders it was given.This check calls the server's tools. ProtocolProbe calls no server's tools for anything it publishes, except for a server whose operator has claimed it and given permission (that server's page says so); an operator can run this check on their own server with our self-test command.not run · our policy
  • 11Log leaks
    logging-side-channel
    Checks whether log messages carry data they should not.This check needs at least one successful tool call to have something to check, and no tool was called.not run · nothing to check it against
  • 12Hidden content
    audience-hiding
    Checks resources that hide content from the user.This check needs content the server returns, and nothing was read or called.not run · nothing to check it against
  • 16Sign-in redirect
    open-redirect
    Checks the sign-in redirect for abuse.Testing the sign-in redirect means sending probes to the operator's sign-in service, which we do not do.not run · our policy
  • 17Consent handling
    confused-deputy
    Checks consent handling when one service acts for another.Depends on the operator's own consent screen, which differs per server and cannot be tested from outside.not testable from outside
Does not apply to this server · 3
  • 13Fake assistant turns
    fake-assistant-turn
    Checks prompts that pose as the assistant's own words.The server exposes no prompts.not applicable
  • 14Token passthrough
    token-passthrough
    Checks whether the server forwards a user's token to other services.The server opened a session without sign-in, so there is no token flow to check.not applicable
  • 15Token audience
    token-audience-validation
    Checks whether tokens meant for another service are accepted.The server opened a session without sign-in, so there is no token flow to check.not applicable

Source: our own test, 2026-11-16, mcp-runtime-engine@0.1.0. Which checks count and why follows our published scoring model.

What happened during the test?

Feature #8

The steps in order, as the test record holds them.

  1. 0 msStarted a read-only session with the server's remote endpoint
  2. 1,157 msConnected after 0 redirects. No credential was sent or needed.
  3. Read the inventory: 74 tools, 0 resources, 0 prompts.
  4. 4,281 msFinished: 3 checks exercised.

Reference

How is it classified?

18 fields

One value per field, each with its source. Fields written by AI models are marked. A field with no value says why.

TopicAI-classified
pending: added at the next monthly refresh
listed 2026-11-16; not classified yet
Pricing modelAI-classified
pending: added at the next monthly refresh
the website is not read yet
Programming language
api.github.com · 2026-11-16
Hosting type
registry · 2026-11-16
MCP capability
resources, tools
our test · 2026-11-16
Transport
streamable HTTP
registry · 2026-11-16
Required credentials
none declared
registry · 2026-11-16 · no declaration is not a guarantee
Package registry
does not apply
remote-only server: no package is shipped, so there is no package registry
Freshness
0–30 days
registry updatedAt · 2026-11-16
Lifecycle status
registry · 2026-11-16
License class
does not apply
remote-only server: ships no package, so there is nothing to look up in a package registry
Integrity hash
does not apply
remote-only server: ships no package, so there is nothing to look up in a package registry
Signature / provenance
does not apply
remote-only server: ships no package, so there is nothing to look up in a package registry
Dependency advisories
does not apply
ships no package, so there are no dependencies to audit
Popularity
does not apply
remote-only server: ships no package, so there is nothing to look up in a package registry
Publisher signals
owner: an organization · repository age: 0–30 days · stars: 0–9
api.github.com · 2026-11-16
Maintenance
api.github.com · 2026-11-16
Environment
the publisher's infrastructure
where it runs, from the hosting type · 2026-11-16

“Not stated” means the source did not state it; “does not apply” means it does not apply to this kind of server; “our limit” means our own lookup failed. A linked value opens the directory filtered to the same value.

Cite or correct this page

Sources and corrections

Suggested citation

ProtocolProbe. “bot.ai-beauty/beautyos: MCP server record.” Data checked 2026-11-16. https://protocolprobe.com/mcp/servers/bot.ai-beauty/beautyos

Figures are valid for the date shown. Our facts on this page are CC BY 4.0: reuse them with a link and the check date. Quoted text (the publisher’s descriptions, website quotes, tool names) is not ours to license.

As JSON: this record in the API · API documentation.

Badge for your README

ProtocolProbe: 5 of 5 record checks met

[![ProtocolProbe](https://protocolprobe.com/api/v1/badge/bot.ai-beauty/beautyos)](https://protocolprobe.com/mcp/servers/bot.ai-beauty/beautyos)

It shows this server's record-check count: facts from public records, no tool called. It is not a security rating or a pass. It links here and updates after each data reload.

Something wrong, or is this yours?

If a fact here is wrong, tell us and we will re-check it. If you operate this server, you can run our checks on it yourself with the free self-test command; we call no server’s tools ourselves for anything shown here, except for a server whose operator has claimed it and given permission (that server's page says so).

Write to hello@protocolprobe.com · corrections log · methodology