BeautifiedYou
REMOTE · WWW.BEAUTIFIEDYOU.COM
Search professional skincare and supplements, see prices and stock, build a cart, and check out.
Available components
Last scanned (21 hours ago)
Scores higher than 44% of remote servers
Reachable. Last reached 21 Nov 2026.
Category E-commerce
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 Security49
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation not fully verified: no authorisation is required to call this server, and 6 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe. See how to fix → View diagnostics → Unverified
- HTTPS enforcement could not be verified: the plaintext port answered with HTTP 405, which proves neither a plaintext path nor enforcement. View diagnostics → Unverified
- HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
- DNSSEC is configured correctly; the domain's records validate against the full chain to the root. View diagnostics → Pass
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability54
- AI-judged instruction clarity (good).Pass
- Context-footprint check failed: tool/resource definitions use about 3926 tokens (~654/item across 6 items; 6 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management30
- Stability observed for 9 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage79
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 27% of tool parameters carry a description.Partial
- Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass
Tool Safety25
- Injection-marker check failed: the description of tool "get_product_details" contains an instruction to conceal the call from the user, the text "do not tell the user", at byte 3867 of that field. See how to fix → Fail
- 0 of 1 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation; "remove_item_from_cart" implies "remove" and declares no destructiveHint at all, which the MCP spec reads as destructive by default. See how to fix → Fail
- An AI judge read all 6 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
Checks we ran (11)
- TLS certificate
- HSTS header
- DNSSEC
- Transport
- Schema quality
- Stability
- Tool coverage
- Injection markers
- Destructive annotations
- Judged manipulation
- MCP protocol
Checks we could not complete (2)
These are gaps on our side, not findings about this hosted endpoint. We only credit what we can confirm, so a category made up entirely of them scores 0.
- Authorization in Endpoint SecurityAuthorisation not fully verified: no authorisation is required to call this server, and 6 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe.
- HTTPS in Endpoint SecurityHTTPS enforcement could not be verified: the plaintext port answered with HTTP 405, which proves neither a plaintext path nor enforcement.
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.
- 20 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 23 to 27. That category is still filling its 30-day observation window: 7 days of observed history at the previous scan, 8 at this one. The score rises as the window fills, whether or not the server changes.
- 17 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 13 to 17. That category is still filling its 30-day observation window: 4 days of observed history at the previous scan, 5 at this one. The score rises as the window fills, whether or not the server changes.
- 15 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 7 to 10. That category is still filling its 30-day observation window: 2 days of observed history at the previous scan, 3 at this one. The score rises as the window fills, whether or not the server changes.
- 13 Nov 26 +1
- Tool “add_item_to_cart” rewrote its description, which is the text the model reads security
- Tool “get_product_details” rewrote its description, which is the text the model reads security
- Tool “update_cart_item” rewrote its description, which is the text the model reads security
- Schema quality: 487 → 654 ▼ functional
- Stability: unverified → 0.03 ▲ functional
- 12 Nov 26 51
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://www.beautifiedyou.com/api/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=www.beautifiedyou.com,O=DERMAGLOBE INC,L=San Dimas,ST=California,C=US | CN=GeoTrust TLS RSA CA G1,OU=www.digicert.com,O=DigiCert Inc,C=US | 13 Sept 2026 | 30 Mar 2027 | RSA 2048 | SHA256-RSA | 2f939ffa6a811932305ca360d1219f8 |
| SANs: www.beautifiedyou.com, beautifiedyou.com | ||||||
| CN=GeoTrust TLS RSA CA G1,OU=www.digicert.com,O=DigiCert Inc,C=US (CA) | CN=DigiCert Global Root G2,OU=www.digicert.com,O=DigiCert Inc,C=US | 2 Nov 2017 | 2 Nov 2027 | RSA 2048 | SHA256-RSA | d07782a133fc6f9a57296e131ffd179 |
| CN=DigiCert Global Root G2,OU=www.digicert.com,O=DigiCert Inc,C=US (CA) | CN=DigiCert Global Root CA,OU=www.digicert.com,O=DigiCert Inc,C=US | 18 Jan 2024 | 9 Nov 2031 | RSA 2048 | SHA256-RSA | fe032ab844d033106c50c8e13c8b068 |
Background: What to check on a remote MCP endpoint →
DNSSEC secure
Validation of www.beautifiedyou.com. — Secure
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | Trust anchor | 20326, 38696 | 8, 8 | Verified |
| com. | DS published | 19718 | 13 | Verified |
| beautifiedyou.com. | DS published | 2371 | 13 | Verified |
| www.beautifiedyou.com. | Verified address RRset verified with the apex keys |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 200 |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://www.beautifiedyou.com/api/mcp | Verified | 200 | |
| http (plaintext) | http://www.beautifiedyou.com/api/mcp | Inconclusive | 405 |
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 →
add_item_to_cart ~1,201
Add one or more items to the shopping cart. If no cart exists, this tool makes a new cart. This tool adds products and gift certificates. Steps 1. Call the 'search_products' tool to find a product. 2. Call the 'get_product_details' tool to get the variants and the modifier options. 3. Call this tool to add the item. 4. Call the 'create_checkout_url' tool to get a checkout URL. The response returns the whole cart. Each item in 'cart.lineItems' has an 'entityId'. Use it as 'line_item_id' in the 'update_cart_item' tool. Use it as 'item_id' in the 'remove_item_from_cart' tool. Rules Send 'quantity' and 'productEntityId' for each item. If the configuration that the user chose has a variant, send 'variantEntityId'. Send 'variantEntityId' as null only for a configuration with no variant. See "Configurations with no variant" for when this is allowed. Modifier options A modifier option is a product choice that is not a variant. Examples are an engraving message and a nicotine strength. The 'get_product_details' tool returns these options in 'modifierOptions'. If the product has no 'modifierOptions' and you send a variant, do not send 'selectedOptions'. If you send a variant in 'variantEntityId', do not send a variant option in 'selectedOptions'. The variant sets those options. An option is required if 'isRequired' is 'true'. Send each required option. If you do not send a required option, the server does not add the item. To send an option: 1. Read the bucket name from 'selectedOptionsKey'. 2. Add the option to 'item.selectedOptions' in that bucket. 3. Send the 'optionEntityId' of the option. 4. For a choice option, send 'optionValueEntityId'. Its number is the 'valueEntityId' of the value that the user selected. Send only the buckets that you need. Example. A required choice option has a 'selectedOptionsKey' of "multipleChoices", an 'optionEntityId' of 108, and a selected value with a 'valueEntityId' of 251: { "item": { "quantity": 1,…
| Name | Type | Req | Description |
|---|---|---|---|
| item | object | yes | – |
| Name | Type | Req | Description |
|---|---|---|---|
| cart | null|object | yes | – |
| message | string | – | – |
| success | boolean | yes | – |
No examples provided.
create_checkout_url ~112
CreateResult a checkout URL for a cart assigned to a current session Arguments: None, but requires a cart to be present in the current session. Returns: - checkoutURL - the URL to redirect the user to for checkout - errors - any errors encountered during the process (like, cart not found, etc.) Flow: - Call 'manage_cart' with 'create_cart' operation to create a new cart. - Call this tool to create a checkout URL for the cart assigned to the current session.
Input schema present but exposes no named parameters.
| Name | Type | Req | Description |
|---|---|---|---|
| checkoutURL | null|string | – | – |
| message | string | – | – |
| success | boolean | yes | – |
No examples provided.
get_product_details ~1,417
Get the details of one or more products. The details are the variants, the options, and the images. Arguments productIds - The list of product IDs. Get these IDs from the 'search_products' tool. Request only the products that the user needs. The server has a maximum count of IDs. The default maximum is 20. If you send too many IDs, the server returns an error. Then send fewer IDs. option_values - The option IDs and the value IDs of one variant. Use this argument with one product ID only. This argument applies to the B2C catalog. For a B2B buyer, the tool returns all the variants. Then select one variant. channelId - Optional. This argument selects the B2B catalog. The default is the channel of the request. variantCursor - Optional. This argument gets the next page of variants. Use this argument with one product ID only. Take the value from 'nextVariantCursor' in the previous result. If 'nextVariantCursor' is absent, or is null, or is the text "null", do not send this argument. Results The tool returns a list of products in 'products'. The output schema gives all the fields. A product has 'modifierOptions' only if the product has modifier options. A product has 'variantOptions' only if the product has variant options. A variant has a price, an inventory level, a purchase flag, and bulk prices only for a B2B buyer. If the tool does not find a product, the list does not include that product. Modifier options A modifier option is a product choice that is not a variant. Examples are an engraving message and a gift note. A variant option is never a modifier option. If a product has no 'modifierOptions', add the product to the cart without 'selectedOptions'. An option is required if 'isRequired' is 'true'. Send each required option to the 'add_item_to_cart' tool. If you do not send a required option, the server does not add the item. A variant selection does not replace a required option. Each option has 'optionEntityId', 'displayName', and '…
| Name | Type | Req | Description |
|---|---|---|---|
| channelId | null|integer | – | – |
| option_values | null|array | – | – |
| productIds | null|array | yes | – |
| variantCursor | null|string | – | – |
| Name | Type | Req | Description |
|---|---|---|---|
| message | string | – | – |
| products | null|array | yes | – |
| success | boolean | yes | – |
| totalCount | integer | yes | – |
No examples provided.
remove_item_from_cart ~211
Remove an item from the shopping cart. This tool removes the item completely. To lower the quantity, use the 'update_cart_item' tool. Steps 1. Call the 'add_item_to_cart' tool to put items in the cart. 2. Call this tool to remove an item. 3. Call the 'create_checkout_url' tool to get a checkout URL. Rules A cart with items must exist. Send 'item_id' to select the cart item to remove. It is the 'entityId' of that item in the cart that the last cart tool call returned, for example 'add_item_to_cart'. It is not 'productEntityId' or 'variantEntityId'.
| Name | Type | Req | Description |
|---|---|---|---|
| item_id | string | yes | The 'entityId' of the cart item to remove. Take it from 'cart.lineItems.physicalItems' or 'cart.lineItems.digitalItems' in the latest cart response. It is not 'productEntityId' or 'variantEntityId'. |
| Name | Type | Req | Description |
|---|---|---|---|
| cart | null|object | yes | – |
| message | string | – | – |
| success | boolean | yes | – |
No examples provided.
search_products ~614
Search products by a term Arguments: term - the search term to look for products. It should be at least 3 characters long. cursor - optional, used for pagination. If provided, it will return the next page of results after. Pagination: Supports pagination with 'cursor' arguments. If 'cursor' is not provided, it will return the first page of results. Value for 'cursor' can be obtained from the 'nextCursor' field in the response. If 'nextCursor' is null, it means there are no more results to fetch. If value of cursor is null (or a string representation of 'null') dont send it in the payload. Results: Each product includes 'requiresFileUpload'. When true, the product has a required file-upload option (e.g. "upload your design") and shouldn't be added to cart through this assistant. Do not attempt to purchase it — tell the user it must be ordered on the website. Stock: Each product carries 'inStock'. It reports whether the store has units on hand. It does NOT report whether the item can be bought. - false does NOT mean the purchase will fail. Many stores accept orders for out-of-stock items - backorder, pre-order, or made-to-order goods that are fabricated after ordering. Whether a given store does is not exposed by this API. So: tell the user the item is out of stock and may take longer to arrive, then ADD IT if they still want it. Do not refuse on 'inStock: false' alone. - If the store really does block it, 'add_item_to_cart' fails and returns the reason. Relay that reason to the user. Attempting the add is the only reliable way to find out. - true only means no out-of-stock condition is reported. A store that does not track inventory reports true for every product, so never state or imply a quantity. - 'inventoryLevel' appears only on stores that publish stock figures; absent means undisclosed, not zero. Flow: - Call this tool with a 'term' argument and optionally with 'cursor' to search for products. - if you find a matching product, call 'get_p…
| Name | Type | Req | Description |
|---|---|---|---|
| context | null|string | – | Additional information about the request such as user demographics, mood, location, or other relevant details that could help in tailoring the response appropriately. Should not contains PII. |
| cursor | null|string | – | – |
| term | string | yes | – |
| Name | Type | Req | Description |
|---|---|---|---|
| message | string | – | – |
| nextCursor | string | – | – |
| products | null|array | yes | – |
| success | boolean | yes | – |
No examples provided.
update_cart_item ~371
Change an item that is already in the shopping cart. Use this tool to change the quantity, the variant, or the modifier options of one cart item. A cart must exist and must have items. Steps 1. Call the 'add_item_to_cart' tool to put an item in the cart. 2. Call this tool to change the item. 3. Call the 'create_checkout_url' tool to get a checkout URL. Rules Send 'line_item_id' to select the cart item to change. It is the 'entityId' of that item in the cart that the last cart tool call returned, for example 'add_item_to_cart'. It is not 'productEntityId' or 'variantEntityId'. Send 'quantity' and 'productEntityId' in 'item'. If the configuration that the user chose has a variant, send 'variantEntityId'. If it has no variant, see "Configurations with no variant" in the 'add_item_to_cart' tool. The same rules apply here, including when to send 'variantEntityId' as null. Modifier options 'item.selectedOptions' works as it works in the 'add_item_to_cart' tool. The 'get_product_details' tool returns these options in 'modifierOptions'. If the product has required modifier options, send them again in this request. If you do not send them, the server does not change the item. Send only the buckets that you need.
| Name | Type | Req | Description |
|---|---|---|---|
| item | object | yes | – |
| line_item_id | string | yes | The 'entityId' of the cart item to change. Take it from 'cart.lineItems.physicalItems' or 'cart.lineItems.digitalItems' in the latest cart response. It is not 'productEntityId' or 'variantEntityId'. |
| Name | Type | Req | Description |
|---|---|---|---|
| cart | null|object | yes | – |
| message | string | – | – |
| success | boolean | yes | – |
No examples provided.
How do I install the BeautifiedYou MCP server?
BeautifiedYou is a hosted endpoint at https://www.beautifiedyou.com/api/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 · www.beautifiedyou.com
claude mcp add --transport http com-beautifiedyou-store 'https://www.beautifiedyou.com/api/mcp'
What is the BeautifiedYou MCP server?
BeautifiedYou is an MCP server listed in the public MCP registry as com.beautifiedyou/store. Search professional skincare and supplements, see prices and stock, build a cart, and check out. This page covers its hosted endpoint (https://www.beautifiedyou.com/api/mcp).
Is the BeautifiedYou MCP server safe to use?
BeautifiedYou scores 55 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 BeautifiedYou MCP server expose?
BeautifiedYou exposes 6 tools: add_item_to_cart, create_checkout_url, get_product_details, remove_item_from_cart, search_products, update_cart_item. Their descriptions and schemas cost roughly 3,926 tokens of context every time the server is loaded.
Does the BeautifiedYou MCP server require authentication?
No. We connected to BeautifiedYou without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the BeautifiedYou MCP server still maintained?
BeautifiedYou 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 BeautifiedYou MCP server?
VerifyMCP ran 11 checks on BeautifiedYou, covering TLS certificate, HSTS header, DNSSEC, Transport and 7 more. 2 items could not be completed, a gap on our side rather than a finding about BeautifiedYou: Authorization and HTTPS. 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.