BeautySpark
REMOTE · MCP.BEAUTYSPARK.ME
BeautySpark MCP server for ChatGPT, Claude and other MCP clients
Available components
Last scanned (18 hours ago)
Scores higher than 51% of remote servers
Reachable. Last reached 21 Nov 2026.
Category Design and Media
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 Security57
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation check failed: no authorisation is required to call this server, and it exposes a tool marked destructive (update_my_look). See how to fix → View diagnostics → Fail
- 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
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability43
- 0% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Fail
- AI-judged instruction clarity (good).Pass
- Context-footprint check failed: tool/resource definitions use about 3641 tokens (~140/item across 26 items; 22 tools + 4 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 Management53
- Stability observed for 16 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage99
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 96% of tool parameters carry a description.Partial
- Structured output schemas are declared (95% of tools); any adoption earns full credit.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- All 1 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation.Pass
- An AI judge read all 24 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a current MCP spec version (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 +1
No change was recorded against any check on this day. Stability & Change Management went from 50 to 53. That category is still filling its 30-day observation window: 15 days of observed history at the previous scan, 16 at this one. The score rises as the window fills, whether or not the server changes.
- 19 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 43 to 47. That category is still filling its 30-day observation window: 13 days of observed history at the previous scan, 14 at this one. The score rises as the window fills, whether or not the server changes.
- 16 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 33 to 37. That category is still filling its 30-day observation window: 10 days of observed history at the previous scan, 11 at this one. The score rises as the window fills, whether or not the server changes.
- 14 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 27 to 30. That category is still filling its 30-day observation window: 8 days of observed history at the previous scan, 9 at this one. The score rises as the window fills, whether or not the server changes.
- 12 Nov 26 +1
- Tool “save_my_look” rewrote its description, which is the text the model reads security
- 10 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.
- 8 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.
- 6 Nov 26 +1
- Stability: unverified → 0.03 ▲ functional
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://mcp.beautyspark.me/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=beautyspark.me | CN=WE1,O=Google Trust Services,C=US | 18 Nov 2026 | 16 Feb 2027 | ECDSA 256 | ECDSA-SHA256 | 54c81b54e69c9a1b13321009d61fcddc |
| SANs: beautyspark.me, *.beautyspark.me | ||||||
| CN=WE1,O=Google Trust Services,C=US (CA) | CN=GTS Root R4,O=Google Trust Services LLC,C=US | 13 Dec 2023 | 20 Feb 2029 | ECDSA 256 | ECDSA-SHA384 | 7ff31977972c224a76155d13b6d685e3 |
| CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) | CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE | 15 Nov 2023 | 28 Jan 2028 | ECDSA 384 | SHA256-RSA | 7fe530bf331343bedd821610493d8a1b |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of mcp.beautyspark.me. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | Trust anchor | 20326, 38696 | 8, 8 | Verified |
| me. | DS published | 45352 | 8 | Verified |
| beautyspark.me. | No DS | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
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://mcp.beautyspark.me/mcp | Verified | 200 | |
| http (plaintext) | http://mcp.beautyspark.me/mcp | HTTPS enforced | 302 | https://mcp.beautyspark.me/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 →
check_product_for_season Check a product against the BeautySpark picks ~174
Looks a product (and optional shade) up in BeautySpark's season picks. Returns the seasons it is recommended for, or match: null when BeautySpark has not reviewed it; then do not present any verdict as BeautySpark's. Pass season to also get that season's palette for comparison.
| Name | Type | Req | Description |
|---|---|---|---|
| locale | string | – | The user's language as a language tag, e.g. "de" or "pt-BR". Set it from the user's language. Defaults to English. |
| product | string | yes | Brand and product name, e.g. "ILIA Overglaze". |
| season | string | – | Color season, e.g. "True Winter" or "true_winter". One of the 12 seasons. |
| shade | string | – | Shade name, e.g. "Flambé". |
| Name | Type | Req | Description |
|---|---|---|---|
| match | – | yes | – |
| seasonPalette | object | – | – |
No examples provided.
confirm_look_generation Confirm try-on ~118
Start the try-on prepared by try_look_from_photo. This spends the BeautySpark credits it quoted. The try-on widget calls it when the user presses Confirm. If no widget is showing, ask the user to confirm the cost first and call it only after they agree. Calling it again for the same quote returns the same job without charging again. If it answers conflict, the same quote is still being confirmed: call it again in a few seconds.
| Name | Type | Req | Description |
|---|---|---|---|
| quoteId | string | yes | The quoteId from try_look_from_photo. |
| Name | Type | Req | Description |
|---|---|---|---|
| alreadyStarted | boolean | yes | – |
| jobId | string | yes | – |
No examples provided.
create_upload_url Create photo upload URL ~41
Used by the try-on widget to upload a photo the user picked. Returns an upload URL valid for 15 minutes.
| Name | Type | Req | Description |
|---|---|---|---|
| contentType | string | yes | – |
| Name | Type | Req | Description |
|---|---|---|---|
| headers | object | yes | – |
| uploadId | string | yes | – |
| uploadUrl | string | yes | – |
No examples provided.
delete_my_look Delete my look ~43
Delete a saved look from the user's BeautySpark My Looks. The look is removed.
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | A saved look id from search_my_looks. |
No output schema declared.
No examples provided.
fetch Fetch BeautySpark content (research) ~119
For research modes (deep research, company knowledge). In chat, use get_guide instead. Returns the full text of one item from search: a guide section ("<locale>/<slug>#<anchor>"), an article look ("look:<id>") or a colour-season palette page ("season:<season>").
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | An id returned by search. |
| locale | string | – | The user's language as a language tag, e.g. "de" or "pt-BR". Set it from the user's language. Defaults to English. |
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | – |
| metadata | object | yes | – |
| text | string | yes | – |
| title | string | yes | – |
| url | string | yes | – |
No examples provided.
find_article_looks Find article looks ~180
Find makeup looks shown in BeautySpark articles, filtered by color season, article type and words. With a season, looks made for that season come first; general looks (no season) follow and are labelled. Returns look ids for get_article_look and the article URL to cite.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | – |
| locale | string | – | The user's language as a language tag, e.g. "de" or "pt-BR". Set it from the user's language. Defaults to English. |
| query | string | – | Words to match against the look title, tags and image description, e.g. "smoky", "graphic liner". |
| season | string | – | Color season, e.g. "True Winter" or "true_winter". One of the 12 seasons. |
| type | string | – | Article type. |
| Name | Type | Req | Description |
|---|---|---|---|
| looks | array | yes | – |
No examples provided.
get_article_look Get article look ~117
Get the steps and shades of one makeup look from a BeautySpark article. The id is a look id returned by find_article_looks ("/images/blog/<article-slug>/<look-name>").
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | A look id from find_article_looks, e.g. "/images/blog/<article-slug>/<look-name>". |
| locale | string | – | The user's language as a language tag, e.g. "de" or "pt-BR". Set it from the user's language. Defaults to English. |
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | – |
| shades | – | yes | – |
| steps | – | yes | – |
| thumbnailUrl | string | yes | – |
| title | string | yes | – |
| url | string | yes | – |
| webUrl | string | yes | – |
No examples provided.
get_color_season Get color season palette ~118
BeautySpark's palette for one of the 12 color seasons: best, neutral and avoid colors with hex codes, plus the eye makeup and lips & cheeks advice from the season guide. Cite the returned URLs.
| Name | Type | Req | Description |
|---|---|---|---|
| locale | string | – | The user's language as a language tag, e.g. "de" or "pt-BR". Set it from the user's language. Defaults to English. |
| season | string | yes | Color season, e.g. "True Winter" or "true_winter". One of the 12 seasons. |
| Name | Type | Req | Description |
|---|---|---|---|
| advice | array | yes | – |
| displayName | string | yes | – |
| guideUrl | string | yes | – |
| lang | string | yes | – |
| season | string | yes | – |
| swatches | object | yes | – |
No examples provided.
get_guide Read a BeautySpark guide section ~78
Read one section of a BeautySpark guide in full, by an id from search_guides. Also lists the ids and headings of the other sections of the same article. Cite the returned url.
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | A section id returned by search_guides, e.g. "en/how-to-find-your-undertone#intro". |
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | – |
| lang | string | yes | – |
| metadata | object | yes | – |
| text | string | yes | – |
| title | string | yes | – |
| url | string | yes | – |
No examples provided.
get_look_status Get try-on status ~110
Check a try-on started by confirm_look_generation. Waits up to waitSeconds (at most 25) for it to finish before answering. When completed, the result includes the image URL and, when the look has them, its step-by-step instructions with the colours for each step.
| Name | Type | Req | Description |
|---|---|---|---|
| jobId | string | yes | The jobId from confirm_look_generation. |
| waitSeconds | number | – | Seconds to wait for completion before answering, 0 to 25. Use 25. |
| Name | Type | Req | Description |
|---|---|---|---|
| afterUrl | string | – | – |
| jobId | string | yes | – |
| nextPollMs | integer | yes | – |
| progress | number | yes | – |
| status | string | yes | – |
| step | string|null | yes | – |
| steps | array | – | – |
| stepsNote | string | – | – |
No examples provided.
get_my_look Get my look ~56
Get one saved look in full: steps, products and shades, tags, categories, notes, photos and a link to open it in BeautySpark.
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | A saved look id from search_my_looks. |
| Name | Type | Req | Description |
|---|---|---|---|
| categories | array | yes | – |
| category | – | yes | – |
| createdAt | string | yes | – |
| difficultyLevel | string|null | yes | – |
| estimatedTotalTime | – | yes | – |
| id | string | yes | – |
| inspirationUrl | string|null | yes | – |
| intensityLevel | string|null | yes | – |
| isFavourite | boolean | yes | – |
| notes | string|null | yes | – |
| occasions | array | yes | – |
| personId | string|null | yes | – |
| photos | array | yes | – |
| products | array | yes | – |
| sourceJobId | string|null | yes | – |
| steps | array | yes | – |
| tags | array | yes | – |
| title | string | yes | – |
| updatedAt | string | yes | – |
| webUrl | string | yes | – |
No examples provided.
get_my_profile Get my beauty profile ~44
The user's BeautySpark analysis: color season, undertone, eye shape, face shape and app language. Fields are null until the selfie analysis has been run in the app.
Input schema present but exposes no named parameters.
| Name | Type | Req | Description |
|---|---|---|---|
| eyeShape | – | yes | – |
| faceShape | string|null | yes | – |
| language | string|null | yes | – |
| note | string | – | – |
| season | – | yes | – |
| undertone | string|null | yes | – |
No examples provided.
get_product_picks Get product picks for a color season ~134
BeautySpark's top product pick per category (blush, highlighter, eyeliner, lipstick, lip gloss, bronzer, eyeshadow palette) for a color season, each with the reason and the article it comes from.
| Name | Type | Req | Description |
|---|---|---|---|
| category | string | – | Only return picks of this category. |
| locale | string | – | The user's language as a language tag, e.g. "de" or "pt-BR". Set it from the user's language. Defaults to English. |
| season | string | yes | Color season, e.g. "True Winter" or "true_winter". One of the 12 seasons. |
| Name | Type | Req | Description |
|---|---|---|---|
| picks | array | yes | – |
| season | string | yes | – |
No examples provided.
list_my_generations List my generations ~65
The user's finished BeautySpark look generations, newest first: title, date, thumbnail and whether it is already in My Looks. Pass a jobId to save_generation_to_my_looks to save one.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | How many to return (default 20). |
| Name | Type | Req | Description |
|---|---|---|---|
| generations | array | yes | – |
No examples provided.
list_my_palettes List my palettes ~53
The palettes the user scanned in BeautySpark, with shade names and hex colors. Use them to advise with products the user owns; pass a paletteId as a product's userPaletteId in save_my_look.
Input schema present but exposes no named parameters.
| Name | Type | Req | Description |
|---|---|---|---|
| palettes | array | yes | – |
No examples provided.
save_generation_to_my_looks Save a generation to My Looks ~62
Save a finished BeautySpark generation (a jobId from list_my_generations) as a look in My Looks. Saving the same generation again returns the look already saved.
| Name | Type | Req | Description |
|---|---|---|---|
| jobId | string | yes | A jobId from list_my_generations. |
| Name | Type | Req | Description |
|---|---|---|---|
| created | boolean | yes | – |
| look | object | yes | – |
| summary | string | yes | – |
No examples provided.
save_my_look Save to My Looks ~551
Save a new look to the user's BeautySpark My Looks. Photos can't be added from chat: if the user attached or mentions a photo, tell them before saving that only the text is saved and that they can add the photo with Add photo on the look card, when it shows one, or in BeautySpark from the returned link. Repeating the same save within 10 minutes returns the first look instead of a copy.
| Name | Type | Req | Description |
|---|---|---|---|
| categorySlugs | array | – | Categories: preset slugs (everyday, work, date_night, evening, party, festival, wedding_guest, bridal, prom, holiday, vacation, photoshoot, editorial, no_makeup, smokey, glam, natural_glow, bold_colo… |
| difficultyLevel | string | – | How hard the look is to do. |
| estimatedTotalTime | integer | – | Time for the whole look, in minutes. |
| inspirationUrl | string | – | An http(s) link to what inspired the look, kept as text. Never fetched. |
| intensityLevel | string | – | How strong the whole look is. |
| isFavourite | boolean | – | Mark the look as a favourite. |
| notes | string | – | Free-text notes about the look. |
| occasions | array | – | Free-text occasions, e.g. ["office", "wedding guest"]. |
| personName | string | – | Name of one of the user's persons in BeautySpark (exact name, any case). Leave it out unless the user names someone. |
| products | array | – | Products used. Each: name (required); productType, e.g. "eyeshadow palette"; area; userPaletteId = the paletteId from list_my_palettes when it is a palette the user owns; shades = the pans used, each… |
| steps | array | – | Ordered steps, first to last. Each step: instruction (required); title; area; positions = where on the eye, only when area is "eyes"; technique (free text); toolsNeeded = tool slugs from the allowed… |
| tagNames | array | – | Tag names. A name the user already has reuses that tag; a new name creates one. |
| title | string | yes | Short name for the look, e.g. "Soft bronze smoky eye". |
| Name | Type | Req | Description |
|---|---|---|---|
| created | boolean | yes | – |
| look | object | yes | – |
| summary | string | yes | – |
No examples provided.
search Search BeautySpark (research) ~118
For research modes (deep research, company knowledge). In chat, use search_guides instead. Searches all public BeautySpark content: guide sections (id "<locale>/<slug>#<anchor>"), article looks (id "look:<id>") and colour-season palette pages (id "season:<season>"). Read any result with fetch.
| Name | Type | Req | Description |
|---|---|---|---|
| locale | string | – | The user's language as a language tag, e.g. "de" or "pt-BR". Set it from the user's language. Defaults to English. |
| query | string | yes | – |
| Name | Type | Req | Description |
|---|---|---|---|
| results | array | yes | – |
No examples provided.
search_guides Search BeautySpark guides ~210
Search BeautySpark's makeup and colour-season guides for sections that answer a question, e.g. eyeliner for hooded eyes or how to find your undertone. Returns up to 5 sections with a short snippet and a link; read one in full with get_guide. Cite the returned url. When nothing matches, the result has a note saying no BeautySpark guide covers it.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | Results to return, 1 to 5. Defaults to 5. |
| locale | string | – | The user's language as a language tag, e.g. "de" or "pt-BR". Set it from the user's language. Defaults to English. |
| query | string | yes | Keywords for the makeup or colour question, e.g. "eyeliner hooded eyes". |
| season | string | – | Color season, e.g. "True Winter" or "true_winter". One of the 12 seasons. |
| type | string | – | Only articles of this type. |
| Name | Type | Req | Description |
|---|---|---|---|
| note | string | – | – |
| results | array | yes | – |
No examples provided.
search_my_looks Search my looks ~157
Search the user's saved looks in BeautySpark My Looks by words, tag, category, favourite or person. Returns look ids for get_my_look.
| Name | Type | Req | Description |
|---|---|---|---|
| category | string | – | Only looks in this category (preset slug or the user's own category name). |
| cursor | string | – | nextCursor from the previous page. |
| favourite | boolean | – | true for favourites only. |
| limit | integer | – | Looks per page (default 20). |
| person | string | – | Only looks for this person (exact name, any case). |
| q | string | – | Text to find in look titles, notes, product, shade and palette names. Use tag for tags. |
| tag | string | – | Only looks with this tag name. |
| Name | Type | Req | Description |
|---|---|---|---|
| looks | array | yes | – |
| nextCursor | string|null | yes | – |
| total | integer | yes | – |
No examples provided.
try_look_from_photo Try a look from a photo ~245
Prepare a try-on: BeautySpark recreates a makeup look on the user's selfie. Give one reference: articleLookId (from find_article_looks) or savedLookId (from search_my_looks). Photos (a reference photo or a different selfie) can only be uploaded in the try-on widget, never taken from chat attachments. The saved selfie is used unless the user uploads another in the widget. Returns the credit cost and balance without charging; nothing is generated until confirm_look_generation.
| Name | Type | Req | Description |
|---|---|---|---|
| articleLookId | string | – | A look id from find_article_looks, to try that article look on. |
| referencePhoto | object | – | Set by the try-on widget in ChatGPT. Leave unset. |
| referenceUploadId | string | – | Set by the try-on widget after an upload. Leave unset. |
| savedLookId | string | – | A saved look id from search_my_looks, to try one of the user's own looks on. |
| selfiePhoto | object | – | Set by the try-on widget in ChatGPT. Leave unset. |
| selfieUploadId | string | – | Set by the try-on widget after an upload. Leave unset. |
Structured output declared, but exposes no named fields.
No examples provided.
update_my_look Update my look ~678
Change a saved look. Only the fields you send change; list fields (steps, products, tags, categories, occasions) replace the stored list whole. Look photos are kept. Steps can't be changed while any step has a photoUrl; the user edits those steps in the BeautySpark app. When the look's steps link products or shades, send productRefs and shadeRefs on every step you send ([] for a step with none): a step sent without them is refused unless products is sent too. To unlink every step, send products too.
| Name | Type | Req | Description |
|---|---|---|---|
| categorySlugs | array | – | Categories: preset slugs (everyday, work, date_night, evening, party, festival, wedding_guest, bridal, prom, holiday, vacation, photoshoot, editorial, no_makeup, smokey, glam, natural_glow, bold_colo… |
| difficultyLevel | string | – | How hard the look is to do. |
| estimatedTotalTime | integer | – | Time for the whole look, in minutes. |
| id | string | yes | A saved look id from search_my_looks. |
| inspirationUrl | – | – | An http(s) link to what inspired the look, kept as text. Never fetched. Send null to clear it. |
| intensityLevel | string | – | How strong the whole look is. |
| isFavourite | boolean | – | Mark the look as a favourite. |
| notes | – | – | Free-text notes about the look. Send null to clear it. |
| occasions | array | – | Free-text occasions, e.g. ["office", "wedding guest"]. Replaces the whole stored list, so send the complete list. |
| personName | – | – | Name of one of the user's persons in BeautySpark (exact name, any case). Leave it out unless the user names someone. Send null to clear it. |
| products | array | – | Products used. Each: name (required); productType, e.g. "eyeshadow palette"; area; userPaletteId = the paletteId from list_my_palettes when it is a palette the user owns; shades = the pans used, each… |
| steps | array | – | Ordered steps, first to last. Each step: instruction (required); title; area; positions = where on the eye, only when area is "eyes"; technique (free text); toolsNeeded = tool slugs from the allowed… |
| tagNames | array | – | Tag names. A name the user already has reuses that tag; a new name creates one. Replaces the whole stored list, so send the complete list. |
| title | string | – | Short name for the look, e.g. "Soft bronze smoky eye". |
| Name | Type | Req | Description |
|---|---|---|---|
| created | boolean | yes | – |
| look | object | yes | – |
| summary | string | yes | – |
No examples provided.
How do I install the BeautySpark MCP server?
BeautySpark is a hosted endpoint at https://mcp.beautyspark.me/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 · mcp.beautyspark.me
claude mcp add --transport http thomasfindlay-beautyspark-mcp 'https://mcp.beautyspark.me/mcp'
What is the BeautySpark MCP server?
BeautySpark is an MCP server listed in the public MCP registry as io.github.ThomasFindlay/beautyspark-mcp. BeautySpark MCP server for ChatGPT, Claude and other MCP clients. This page covers its hosted endpoint (https://mcp.beautyspark.me/mcp).
Is the BeautySpark MCP server safe to use?
BeautySpark scores 66 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 BeautySpark MCP server expose?
BeautySpark exposes 22 tools: search_guides, get_guide, search, fetch, get_color_season, and 17 more. Their descriptions and schemas cost roughly 3,471 tokens of context every time the server is loaded.
Does the BeautySpark MCP server require authentication?
No. We connected to BeautySpark without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the BeautySpark MCP server still maintained?
BeautySpark 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 BeautySpark MCP server?
VerifyMCP ran 14 checks on BeautySpark, 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.