BeautyOS by AI Beauty Bot
REMOTE · AGENTS.AI-BEAUTY.BOT
Free salon CRM: services, staff, clients, online booking and an optional AI receptionist.
Available components
Last scanned (22 hours ago)
Scores higher than 65% of remote servers
Reachable. Last reached 21 Nov 2026.
Category CRM and Sales
How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →
Endpoint Security92
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation is enforced on tool calls, advertised via RFC 9728 protected-resource metadata. Discovery is public, which costs nothing: no tool can be invoked without a token. View diagnostics → Pass
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
- The authorisation server supports Client ID Metadata Documents, the current MCP client-registration mechanism. View diagnostics → Pass
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability65
- AI-judged instruction clarity (good).Pass
- Tool/resource definitions use about 6360 tokens (~85/item across 74 items; 74 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management17
- Stability observed for 5 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage67
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 0% of tool parameters carry a description.Fail
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- All 3 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation.Pass
- An AI judge read all 75 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
- Supports UI / widget rendering.Pass
Checks we ran (14)
- TLS certificate
- Authorization
- HTTPS
- HSTS header
- DNSSEC
- Transport
- Schema quality
- Stability
- Tool coverage
- Injection markers
- Destructive annotations
- Judged manipulation
- MCP protocol
- Capabilities
Does not apply to this hosted endpoint (2)
- Supply Chain SecurityScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
- Provenance & TransparencyScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
The score does not measure everything. What the score does not measure →
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 21 Nov 26 0
- This server's schema is too large to store in full, so we cannot compare its tools day to day functional
- 20 Nov 26 +1
- This server's schema is too large to store in full, so we cannot compare its tools day to day functional
- 19 Nov 26 0
- This server's schema is too large to store in full, so we cannot compare its tools day to day functional
- 18 Nov 26 +1
- This server's schema is too large to store in full, so we cannot compare its tools day to day functional
- 17 Nov 26 0
- Stability: unverified → 0.03 ▲ functional
- This server's schema is too large to store in full, so we cannot compare its tools day to day functional
- 16 Nov 26 74
First indexed and scored.
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 21 Nov 2026 · Probed https://agents.ai-beauty.bot/beauty-os/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=agents.ai-beauty.bot | CN=YE1,O=Let's Encrypt,C=US | 14 Oct 2026 | 12 Jan 2027 | ECDSA 256 | ECDSA-SHA384 | 579f3b01b0cd3772a93d281ed4d17048ae4 |
| SANs: agents.ai-beauty.bot | ||||||
| CN=YE1,O=Let's Encrypt,C=US (CA) | CN=Root YE,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | ECDSA 384 | ECDSA-SHA384 | 5ddd70dd31f801c85c186a7a04b80afe |
| CN=Root YE,O=ISRG,C=US (CA) | CN=ISRG Root X2,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | ECDSA-SHA384 | 872165fc34b6e5fba8add5b3705fb53a |
| CN=ISRG Root X2,O=Internet Security Research Group,C=US (CA) | CN=ISRG Root X1,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | SHA256-RSA | 6c8f1dc727c7117f7baf853ac980f9cd |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of agents.ai-beauty.bot. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | Trust anchor | 20326, 38696 | 8, 8 | Verified |
| bot. | DS published | 58741 | 8 | Verified |
| ai-beauty.bot. | No DS | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication Enforced and verified
The endpoint asked for a token and published valid RFC 9728 metadata describing how to get one.
| Result | Enforced and verified |
|---|---|
| Enforced | On tool calls |
| HTTP status | 200 |
WWW-Authenticate challenge Bearer resource_metadata="https://agents.ai-beauty.bot/.well-known/oauth-protected-resource/beauty-os/mcp", scope="beautyos.members.read beautyos.members.write beautyos.profile.read beautyos.salons.read beautyos.salons.write beautyos.catalog.read beautyos.catalog.write beautyos.staff.read beautyos.staff.write beautyos.channels.read beautyos.channels.write beautyos.agent.read beautyos.agent.write beautyos.insights.read beautyos.insights.write beautyos.knowledge.read beautyos.knowledge.write beautyos.booking.read beautyos.booking.write beautyos.calendar.read beautyos.calendar.write beautyos.clients.read beautyos.clients.write beautyos.inbox.read beautyos.inbox.write beautyos.billing.read", error="invalid_token"
Bearer resource_metadata="https://agents.ai-beauty.bot/.well-known/oauth-protected-resource/beauty-os/mcp", scope="beautyos.members.read beautyos.members.write beautyos.profile.read beautyos.salons.read beautyos.salons.write beautyos.catalog.read beautyos.catalog.write beautyos.staff.read beautyos.staff.write beautyos.channels.read beautyos.channels.write beautyos.agent.read beautyos.agent.write beautyos.insights.read beautyos.insights.write beautyos.knowledge.read beautyos.knowledge.write beautyos.booking.read beautyos.booking.write beautyos.calendar.read beautyos.calendar.write beautyos.clients.read beautyos.clients.write beautyos.inbox.read beautyos.inbox.write beautyos.billing.read", error="invalid_token" | Header | Value |
|---|---|
| x-content-type-options | nosniff |
| referrer-policy | no-referrer |
Protected resource metadata
| Document | https://agents.ai-beauty.bot/.well-known/oauth-protected-resource/beauty-os/mcp |
|---|---|
| Retrieved | Yes |
| Resource | https://agents.ai-beauty.bot/beauty-os/mcp |
| Authorisation server | https://agents.ai-beauty.bot/beauty-os/oauth |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://agents.ai-beauty.bot/beauty-os/mcp | Verified | 200 | |
| http (plaintext) | http://agents.ai-beauty.bot/beauty-os/mcp | HTTPS enforced | 301 | https://agents.ai-beauty.bot/beauty-os/mcp |
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
beautyos_member_restore_prepare Restore access ~153
Restore a revoked member with the same rights and employee. Sends an invitation only if the member has never activated access. Reuses both records. Requires members.manage and beautyos.members.write. Returns a saved change ID with exact recipient, role, calendar and email effects. No access changes or email before confirmation. Show the effects and call beautyos_apply_change only after explicit approval. Ownership changes and self-role changes are forbidden; external CRM/legacy permissions are unchanged. If a receipt reports accessSaved=true and deliveryError, tell the user the invitation email failed and propose a new confirmed resend; replaying the original operation never resends.
| Name | Type | Req | Description |
|---|---|---|---|
| memberId | string | yes | – |
| salonId | string | yes | – |
No output schema declared.
No examples provided.
beautyos_member_revoke_prepare Revoke access ~143
Revoke BeautyOS access for the resolved memberId while retaining the employee and calendar. Requires members.manage and beautyos.members.write. Returns a saved change ID with exact recipient, role, calendar and email effects. No access changes or email before confirmation. Show the effects and call beautyos_apply_change only after explicit approval. Ownership changes and self-role changes are forbidden; external CRM/legacy permissions are unchanged. If a receipt reports accessSaved=true and deliveryError, tell the user the invitation email failed and propose a new confirmed resend; replaying the original operation never resends.
| Name | Type | Req | Description |
|---|---|---|---|
| memberId | string | yes | – |
| salonId | string | yes | – |
No output schema declared.
No examples provided.
beautyos_member_update_prepare Change team access ~186
Change an existing BeautyOS member role/profile/calendar. own-schedule requires role=staff and an existing staffId. standard staff has broader client access. This does not restore revoked access or send email. Requires members.manage and beautyos.members.write. Returns a saved change ID with exact recipient, role, calendar and email effects. No access changes or email before confirmation. Show the effects and call beautyos_apply_change only after explicit approval. Ownership changes and self-role changes are forbidden; external CRM/legacy permissions are unchanged. If a receipt reports accessSaved=true and deliveryError, tell the user the invitation email failed and propose a new confirmed resend; replaying the original operation never resends.
| Name | Type | Req | Description |
|---|---|---|---|
| accessProfile | string | yes | – |
| memberId | string | yes | – |
| role | string | yes | – |
| salonId | string | yes | – |
| staffId | – | yes | – |
No output schema declared.
No examples provided.
beautyos_members_list Read BeautyOS team access ~70
Read memberships, exact emails, roles, invitation status, retry eligibility and calendar bindings for salonId. Requires members.manage and beautyos.members.read. Does not expose invitation links or tokens. Use beautyos_catalog_get for scheduling employees; memberships are distinct from employees.
| Name | Type | Req | Description |
|---|---|---|---|
| salonId | string | yes | – |
No output schema declared.
No examples provided.
beautyos_prepare_agent_change UI: AI receptionist change preview ~113
App-only adapter for AI settings in the selected salonId. action=configure prepares input.patch, activate checks activation prerequisites, and pause prepares pausing replies. Saves a plan without changing settings or enabling or disabling the agent. In conversation, use beautyos_agent_configure_prepare, beautyos_agent_activate_prepare or beautyos_agent_pause_prepare. Review the effects and obtain explicit confirmation before beautyos_apply_change.
| Name | Type | Req | Description |
|---|---|---|---|
| action | string | yes | – |
| input | object | yes | – |
| salonId | string | – | – |
No output schema declared.
No examples provided.
beautyos_prepare_catalog_import UI: catalog import preview ~98
App-only import adapter: forwards input.rows and optional source information to catalog preparation for the selected salonId, then saves a preview. Does not import services or staff. In conversation, use beautyos_catalog_import_prepare with its specific schema; this adapter serves the form with nested input. Show all effects and apply with beautyos_apply_change only after explicit owner confirmation.
| Name | Type | Req | Description |
|---|---|---|---|
| input | object | yes | – |
| salonId | string | yes | – |
No output schema declared.
No examples provided.
beautyos_prepare_salon_change UI: salon change preview ~115
App-only adapter for the salon form. action=create forwards input to new-salon preparation; action=update forwards patch for an existing salonId. Saves a preview without creating a salon, taking payment or updating its profile. In conversation, use beautyos_salon_create_prepare or beautyos_salon_update_prepare. The form displays effects; apply them separately with beautyos_apply_change only after explicit owner confirmation.
| Name | Type | Req | Description |
|---|---|---|---|
| action | string | yes | – |
| input | object | yes | – |
| salonId | string | – | – |
No output schema declared.
No examples provided.
beautyos_prepare_schedule_change UI: schedule change preview ~122
App-only adapter for the calendar in the selected salonId. action=replace prepares full replacement of rules for input.staffId; action=absence prepares an absence from startsAt to endsAt and the specific cancellations in cancelAppointmentIds. Saves a plan and effects without changing the calendar or cancelling appointments. In conversation, use beautyos_staff_schedule_replace_prepare or beautyos_staff_absence_create_prepare. Apply separately with beautyos_apply_change after explicit confirmation.
| Name | Type | Req | Description |
|---|---|---|---|
| action | string | yes | – |
| input | object | yes | – |
| salonId | string | – | – |
No output schema declared.
No examples provided.
beautyos_prepare_service_change UI: service change preview ~105
App-only adapter for the service form in the selected salonId. action=create prepares input.service; action=update prepares input.serviceId and input.patch. Saves a plan without changing the catalog. In conversation, use beautyos_service_create_prepare or beautyos_service_update_prepare with their specific schemas. The form requests explicit confirmation of the effects before beautyos_apply_change.
| Name | Type | Req | Description |
|---|---|---|---|
| action | string | yes | – |
| input | object | yes | – |
| salonId | string | – | – |
No output schema declared.
No examples provided.
beautyos_prepare_staff_change UI: staff change preview ~116
App-only adapter for the team form in the selected salonId. action=create prepares input.staff; update prepares input.staffId and patch; replace_services prepares full replacement of input.serviceIds for staffId. Saves a plan without changing staff or assignments. In conversation, use beautyos_staff_create_prepare, beautyos_staff_update_prepare or beautyos_staff_services_replace_prepare. Apply separately with beautyos_apply_change after explicit confirmation.
| Name | Type | Req | Description |
|---|---|---|---|
| action | string | yes | – |
| input | object | yes | – |
| salonId | string | – | – |
No output schema declared.
No examples provided.
beautyos_salon_create_prepare Preview new salon ~105
Start CRM setup with salon, catalog, staff, channel and agent permissions granted together at initial authorization. Connecting channels and activating AI remain separate owner choices. Does not publish online booking, subscribe, pay, invite others or activate the agent.
| Name | Type | Req | Description |
|---|---|---|---|
| address | – | – | – |
| creationKey | string | yes | – |
| currency | string | yes | – |
| locale | string | – | – |
| name | string | yes | – |
| phone | – | – | – |
| timezone | string | yes | – |
No output schema declared.
No examples provided.
beautyos_salon_get Read salon profile ~28
Read salon details and current data-source capabilities.
| Name | Type | Req | Description |
|---|---|---|---|
| salonId | string | yes | – |
No output schema declared.
No examples provided.
beautyos_salon_update_prepare Preview salon profile changes ~43
Preview exact local and platform profile edits. External CRM core fields remain provider-owned.
| Name | Type | Req | Description |
|---|---|---|---|
| patch | object | yes | – |
| salonId | string | yes | – |
No output schema declared.
No examples provided.
beautyos_salons_list List linked salons ~23
List only linked salons for which live membership still permits access.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
beautyos_service_create_prepare Prepare service creation ~98
Use this when the owner wants to add one service to salonId. Accepts service with a name, duration and price in minor currency units; checks the current catalog source capabilities and previews supplied values, defaults and staff assignments. Saves a creation plan without creating the service. After review and explicit confirmation, apply change.id and change.version with beautyos_apply_change.
| Name | Type | Req | Description |
|---|---|---|---|
| salonId | string | yes | – |
| service | object | yes | – |
No output schema declared.
No examples provided.
beautyos_service_update_prepare Prepare service update ~94
Use this to update an existing serviceId in salonId. Compares a non-empty patch with current data and previews price, duration and other supported changes, including additional external CRM effects. Saves an update plan without changing the service. Applying it requires owner review and explicit confirmation through beautyos_apply_change.
| Name | Type | Req | Description |
|---|---|---|---|
| patch | object | yes | – |
| salonId | string | yes | – |
| serviceId | string | yes | – |
No output schema declared.
No examples provided.
beautyos_staff_absence_create_prepare Prepare staff absence ~86
Use this to plan an absence for staffId in salonId between startsAt and endsAt. Checks appointment overlaps and the explicit cancelAppointmentIds list, then previews the absence and the specific appointments to cancel. Saves a plan without creating an absence, cancelling appointments or synchronizing the calendar. Applying the absence and listed cancellations requires separate explicit confirmation through beautyos_apply_change.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
beautyos_staff_create_prepare Prepare staff creation ~99
Use this to add one staff member from the staff object to salonId. Checks the catalog and source capabilities; previews the profile, service assignments and default schedule: Monday through Saturday, 09:00-18:00 in native mode. Saves a plan without creating staff or sending an invitation. Apply with beautyos_apply_change only after owner review and explicit confirmation.
| Name | Type | Req | Description |
|---|---|---|---|
| salonId | string | yes | – |
| staff | object | yes | – |
No output schema declared.
No examples provided.
beautyos_staff_schedule_get Read staff schedule ~31
Read dated staff schedule where the current provider supports it; native mode returns weekly rules and appointment conflicts.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
beautyos_staff_schedule_replace_prepare Prepare weekly schedule replacement ~105
Use this to fully replace weekly availability for staffId in salonId with rules containing weekday and minute boundaries. Validates times and source capabilities, and previews the current and proposed schedule in the salon time zone; empty rules make the staff member unavailable when applied. Saves a preview without changing the calendar. Apply with beautyos_apply_change after explicit owner confirmation.
| Name | Type | Req | Description |
|---|---|---|---|
| rules | array | yes | – |
| salonId | string | yes | – |
| staffId | string | yes | – |
No output schema declared.
No examples provided.
beautyos_staff_services_replace_prepare Prepare staff service replacement ~110
Use this to fully replace service assignments for staffId in salonId with serviceIds. Previews current and proposed assignments; an empty list removes assignments when applied. For native catalogs, accounts for implicit assignments of services to all staff and their materialization across the salon. Saves a plan without changing assignments; apply with beautyos_apply_change only after explicit confirmation of all effects.
| Name | Type | Req | Description |
|---|---|---|---|
| salonId | string | yes | – |
| serviceIds | array | yes | – |
| staffId | string | yes | – |
No output schema declared.
No examples provided.
beautyos_staff_update_prepare Prepare staff update ~97
Use this to edit an existing staffId in salonId. Validates a non-empty profile patch, compares it with current values and saves a plan of supported changes. Does not update staff, replace their schedule or send invitations. Explain the differences to the owner; apply separately with beautyos_apply_change after explicit confirmation.
| Name | Type | Req | Description |
|---|---|---|---|
| patch | object | yes | – |
| salonId | string | yes | – |
| staffId | string | yes | – |
No output schema declared.
No examples provided.
beautyos_update_onboarding Save setup progress ~61
Save the selected setup step and assistance preference. Does not mark customer delivery or readiness as verified.
| Name | Type | Req | Description |
|---|---|---|---|
| assistanceNeeded | boolean | – | – |
| expectedRevision | integer | – | – |
| salonId | string | yes | – |
| step | string | yes | – |
No output schema declared.
No examples provided.
beautyos_verify_first_reply Verify an actual delivered reply ~43
Check recent real messaging channels for provider-confirmed assistant delivery. Returns only aggregate evidence; never customer conversations or contact data.
| Name | Type | Req | Description |
|---|---|---|---|
| salonId | string | yes | – |
No output schema declared.
No examples provided.
How do I install the BeautyOS by AI Beauty Bot MCP server?
BeautyOS by AI Beauty Bot is a hosted endpoint at https://agents.ai-beauty.bot/beauty-os/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
remote · agents.ai-beauty.bot
claude mcp add --transport http bot-ai-beauty-beautyos 'https://agents.ai-beauty.bot/beauty-os/mcp'
What is the BeautyOS by AI Beauty Bot MCP server?
BeautyOS by AI Beauty Bot is an MCP server listed in the public MCP registry as bot.ai-beauty/beautyos. Free salon CRM: services, staff, clients, online booking and an optional AI receptionist. This page covers its hosted endpoint (https://agents.ai-beauty.bot/beauty-os/mcp).
Is the BeautyOS by AI Beauty Bot MCP server safe to use?
BeautyOS by AI Beauty Bot scores 76 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the BeautyOS by AI Beauty Bot MCP server expose?
BeautyOS by AI Beauty Bot exposes 74 tools: beautyos_members_list, beautyos_member_invite_prepare, beautyos_member_update_prepare, beautyos_member_revoke_prepare, beautyos_member_restore_prepare, and 69 more. Their descriptions and schemas cost roughly 6,267 tokens of context every time the server is loaded.
Does the BeautyOS by AI Beauty Bot MCP server require authentication?
Yes. BeautyOS by AI Beauty Bot asked us for credentials when we connected, so you will need to authorise it in your MCP client before it can do anything.
Is the BeautyOS by AI Beauty Bot MCP server still maintained?
BeautyOS by AI Beauty Bot is still listed as active in the MCP registry. We last reached this channel on 21 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.
What did VerifyMCP test on the BeautyOS by AI Beauty Bot MCP server?
VerifyMCP ran 14 checks on BeautyOS by AI Beauty Bot, covering TLS certificate, Authorization, HTTPS, HSTS header and 10 more. Supply Chain Security and Provenance & Transparency do not apply to a hosted endpoint, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.