Build abstracts on Amorphous. An abstract can be anything.
BeautySpark is installed from its publisher's own source and answers where it runs, so this marketplace is not in the path of a single call. There is no address here to send one to, and a panel that pretended otherwise would be showing you an answer we made up. Install it and call it from your own client — the Installation tab has the entry for each one.
What it does
BeautySpark MCP server for ChatGPT, Claude and other MCP clients
Quickstart
# 1 — add it to Claude Code
claude mcp add --scope user --transport http beautyspark-mcp https://mcp.beautyspark.me/mcp
# 2 — ask your agent for something these tools do
# search_guides, get_guide, search and 19 more
BeautySpark costs nothing on mcprush: there is no plan to choose here, no cap to set and nothing mcprush can bill you for.
Collected from a public index. Nobody has claimed this account, so nothing here was written by its author — claim it if it is yours.
Where are you running it?
Every route below installs the same thing and ends at the same approval screen. Nothing here runs on your machine and nothing runs on ours: this server answers at its publisher’s own address, and what you install is the connection straight to it.
This is a public server: it answers at its publisher’s own address and this marketplace is not in the path. Claude Code registers it in one command; --scope user makes it available in every project. The transport below is http, as the publisher's own manifest declares it.
claude mcp add --scope user --transport http beautyspark-mcp https://mcp.beautyspark.me/mcpReconnect, or start a new session, and the tools appear in the model’s tool list.
One config entry pointing straight at the publisher’s own address — this marketplace is not in the path, and nothing from this listing executes on your machine.
22 tools, with what each one reads, writes and reaches shown before you agree — the same list on every route above. Read the tool surface.
Tool surface
What the model actually sees. Descriptions are diffed on every release — see version history.
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| query | string | yes | Keywords for the makeup or colour question, e.g. "eyeliner hooded eyes". |
| locale | string | no | 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 | no | Color season, e.g. "True Winter" or "true_winter". One of the 12 seasons. |
| type | string | no | Only articles of this type. |
| limit | integer | no | Results to return, 1 to 5. Defaults to 5. |
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| id | string | yes | A section id returned by search_guides, e.g. "en/how-to-find-your-undertone#intro". |
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| query | string | yes | — |
| locale | string | no | The user's language as a language tag, e.g. "de" or "pt-BR". Set it from the user's language. Defaults to English. |
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>").
| Parameter | Type | Required | Notes |
|---|---|---|---|
| id | string | yes | An id returned by search. |
| locale | string | no | The user's language as a language tag, e.g. "de" or "pt-BR". Set it from the user's language. Defaults to English. |
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| season | string | yes | Color season, e.g. "True Winter" or "true_winter". One of the 12 seasons. |
| locale | string | no | The user's language as a language tag, e.g. "de" or "pt-BR". Set it from the user's language. Defaults to English. |
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| season | string | yes | Color season, e.g. "True Winter" or "true_winter". One of the 12 seasons. |
| category | string | no | Only return picks of this category. |
| locale | string | no | The user's language as a language tag, e.g. "de" or "pt-BR". Set it from the user's language. Defaults to English. |
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| product | string | yes | Brand and product name, e.g. "ILIA Overglaze". |
| shade | string | no | Shade name, e.g. "Flambé". |
| season | string | no | Color season, e.g. "True Winter" or "true_winter". One of the 12 seasons. |
| locale | string | no | The user's language as a language tag, e.g. "de" or "pt-BR". Set it from the user's language. Defaults to English. |
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| query | string | no | Words to match against the look title, tags and image description, e.g. "smoky", "graphic liner". |
| season | string | no | Color season, e.g. "True Winter" or "true_winter". One of the 12 seasons. |
| type | string | no | Article type. |
| locale | string | no | The user's language as a language tag, e.g. "de" or "pt-BR". Set it from the user's language. Defaults to English. |
| limit | integer | no | — |
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>").
| Parameter | Type | Required | Notes |
|---|---|---|---|
| id | string | yes | A look id from find_article_looks, e.g. "/images/blog/<article-slug>/<look-name>". |
| locale | string | no | The user's language as a language tag, e.g. "de" or "pt-BR". Set it from the user's language. Defaults to English. |
Search the user's saved looks in BeautySpark My Looks by words, tag, category, favourite or person. Returns look ids for get_my_look.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| q | string | no | Text to find in look titles, notes, product, shade and palette names. Use tag for tags. |
| tag | string | no | Only looks with this tag name. |
| category | string | no | Only looks in this category (preset slug or the user's own category name). |
| favourite | boolean | no | true for favourites only. |
| person | string | no | Only looks for this person (exact name, any case). |
| cursor | string | no | nextCursor from the previous page. |
| limit | integer | no | Looks per page (default 20). |
Get one saved look in full: steps, products and shades, tags, categories, notes, photos and a link to open it in BeautySpark.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| id | string | yes | A saved look id from search_my_looks. |
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 in BeautySpark from the returned link. Repeating the same save within 10 minutes returns the first look instead of a copy.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| title | string | yes | Short name for the look, e.g. "Soft bronze smoky eye". |
| notes | string | no | Free-text notes about the look. |
| inspirationUrl | string | no | An http(s) link to what inspired the look, kept as text. Never fetched. |
| isFavourite | boolean | no | Mark the look as a favourite. |
| occasions | array | no | Free-text occasions, e.g. ["office", "wedding guest"]. |
| intensityLevel | string | no | How strong the whole look is. |
| difficultyLevel | string | no | How hard the look is to do. |
| estimatedTotalTime | integer | no | Time for the whole look, in minutes. |
| steps | array | no | 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 v |
| products | array | no | 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 |
| tagNames | array | no | Tag names. A name the user already has reuses that tag; a new name creates one. |
| personName | string | no | Name of one of the user's persons in BeautySpark (exact name, any case). Leave it out unless the user names someone. |
| categorySlugs | array | no | 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_color |
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
| Parameter | Type | Required | Notes |
|---|---|---|---|
| title | string | no | Short name for the look, e.g. "Soft bronze smoky eye". |
| notes | no | Free-text notes about the look. Send null to clear it. | |
| inspirationUrl | no | An http(s) link to what inspired the look, kept as text. Never fetched. Send null to clear it. | |
| isFavourite | boolean | no | Mark the look as a favourite. |
| occasions | array | no | Free-text occasions, e.g. ["office", "wedding guest"]. Replaces the whole stored list, so send the complete list. |
| intensityLevel | string | no | How strong the whole look is. |
| difficultyLevel | string | no | How hard the look is to do. |
| estimatedTotalTime | integer | no | Time for the whole look, in minutes. |
| steps | array | no | 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 v |
| products | array | no | 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 |
| tagNames | array | no | 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. |
| personName | no | 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. | |
| categorySlugs | array | no | 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_color |
| id | string | yes | A saved look id from search_my_looks. |
Delete a saved look from the user's BeautySpark My Looks. The look is removed.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| id | string | yes | A saved look id from search_my_looks. |
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| jobId | string | yes | A jobId from list_my_generations. |
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.
No parameter schema on file.
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.
No parameter schema on file.
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| limit | integer | no | How many to return (default 20). |
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 an
| Parameter | Type | Required | Notes |
|---|---|---|---|
| articleLookId | string | no | A look id from find_article_looks, to try that article look on. |
| savedLookId | string | no | A saved look id from search_my_looks, to try one of the user's own looks on. |
| referenceUploadId | string | no | Set by the try-on widget after an upload. Leave unset. |
| referencePhoto | object | no | Set by the try-on widget in ChatGPT. Leave unset. |
| selfieUploadId | string | no | Set by the try-on widget after an upload. Leave unset. |
| selfiePhoto | object | no | Set by the try-on widget in ChatGPT. Leave unset. |
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:
| Parameter | Type | Required | Notes |
|---|---|---|---|
| quoteId | string | yes | The quoteId from try_look_from_photo. |
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| jobId | string | yes | The jobId from confirm_look_generation. |
| waitSeconds | number | no | Seconds to wait for completion before answering, 0 to 25. Use 25. |
Used by the try-on widget to upload a photo the user picked. Returns an upload URL valid for 15 minutes.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| contentType | string | yes | — |
- Every tool — any call limit is its publisher’s, not ours
- No card, and mcprush charges nothing for it
- Runs at its publisher’s own address — this marketplace is not in the path
- Nothing to cap, because mcprush bills nothing
What counts against your monthly calls
| Tool | Unit | Calls used | Out of the allowance |
|---|
Nothing here is billable: mcprush charges nothing to install BeautySpark or to call it, at any volume.
Two independent axes, because powerful and malicious are different questions. The grade is threat only. The capability level is blast radius, and it is never a penalty on the grade — it is priced as one subtract-only term in the score, where you can see it.
| Term | Level | What it prices | Points |
|---|---|---|---|
| capability-exposure | moderate | capability blast radius (moderate) — client exposure if the model is manipulated | −3 |
| coverage-honesty | manifest | inspection depth (manifest) — how much of the target the scan could see | −4 |
What the scan could actually read
A grade is only as meaningful as its coverage, so the scanner publishes its own depth before it publishes its result.
The scan read each tool’s name, description, input schema and annotations exactly as the server listed them the last time it answered us; no code was reviewed. We ask the server again about once a month, and a list that changed is graded again.
The implementation source was not read — this reflects the declared tool metadata only.
Capability — what it could do if the model were manipulated
Tags derived from each tool’s schema and the implementation, not from what the tool calls itself. moderate is the level these add up to.
| Tool | Capability tags | Why the tag was assigned |
|---|---|---|
| search_guides | no tags | |
| get_guide | no tags | |
| search | untrusted-input | untrusted-input: keyword "fetch" |
| fetch | untrusted-input | untrusted-input: keyword "fetch" |
| get_color_season | no tags | |
| get_product_picks | no tags | |
| check_product_for_season | no tags | |
| find_article_looks | no tags | |
| get_article_look | no tags | |
| search_my_looks | no tags | |
| get_my_look | no tags | |
| save_my_look | state-write | state-write: declares readOnlyHint: false |
| update_my_look | state-write | state-write: declares readOnlyHint: false, destructiveHint: true |
| delete_my_look | state-write | state-write: declares readOnlyHint: false, destructiveHint: true |
| save_generation_to_my_looks | state-write | state-write: declares readOnlyHint: false |
| get_my_profile | no tags | |
| list_my_palettes | no tags | |
| list_my_generations | no tags | |
| try_look_from_photo | state-write | state-write: declares readOnlyHint: false |
| confirm_look_generation | state-write | state-write: declares readOnlyHint: false, destructiveHint: true |
| get_look_status | no tags | |
| create_upload_url | state-write | state-write: declares readOnlyHint: false |
Toxic-flow graph
The lethal trifecta, checked as a graph rather than as a checklist: untrusted input, a sensitive source and an external sink have to meet before there is a path worth worrying about.
The public result for this release does not print the flow graph, so there is nothing to show here. That is not the same as "no paths were found": what the scan did read is above, under coverage.
Supply chain and provenance
This is the first scan of this surface here, so there is nothing yet to compare it against.
Every result on this tab comes from one deterministic pass over the published package — offline, rule by rule, and auditable line by line above. Same methodology version, same bytes, same score.
Release history
This is an address its publisher runs: which release it serves is theirs to choose, so there is nothing here to pin. The history below is for reading; the current release on file is 1.0.0.
No release note was published with this version.
One review per account, from a signed-in account that does not publish this listing. Nothing else is asked — you can say what you think before you install it. Publishers can reply once per review, and a review can be edited or deleted by whoever wrote it.
Any signed-in account that does not publish BeautySpark can review it, once — before installing it or after. A review from an account that has installed it is marked as one.
Nobody has reviewed this listing. The rating on the card is the mean of the reviews written here and nothing else, so there is no rating until somebody writes the first — which takes a signed-in account that does not publish it, and nothing else.