Open Beauty Facts MCP. Check cosmetic ingredients and allergens with one query.
Works with every AI agent you already use
…and any MCP-compatible client
Just plug in your AI agents and start using Vinkius.
Open Beauty Facts connects your AI client to a massive, open database of cosmetic products worldwide. It lets you look up ingredients (INCI), detect allergens, and search for specific beauty items by name or barcode instantly.
Stop guessing about what's in your makeup or skincare routine; check the facts directly.
What your AI agents can do
Get beauty product
Retrieves all specific details for one beauty product using its EAN/UPC barcode.
Search beauty products
Finds groups of products by running a general search based on brand name or product category.
You input a barcode and the server returns the full details for that specific beauty product.
The agent searches the entire database, returning lists of products based on criteria like 'Nivea' or 'sunscreen'.
You get the complete INCI list for any found product.
The server analyzes formulations and flags potential allergens or restricted chemicals.
Ask AI about this MCP
Supported MCP Clients
Waiting for input…
Open Beauty Facts: 2 Tools for Ingredient Analysis
These two tools let you find specific product data using barcodes, or run broad searches across the entire catalog based on brand and category.
019d8465get beauty product
Retrieves all specific details for one beauty product using its EAN/UPC barcode.
019d8465search beauty products
Finds groups of products by running a general search based on brand name or product category.
Choose How to Get Started
Build a custom MCP for your own tools, or connect a ready-made integration from our catalog.
Build Your Own
Turn any API into an MCP. Import a spec, define Agent Skills, or deploy with MCPFusion.
- Import from OpenAPI, Swagger, or YAML specs
- Create Agent Skills with progressive disclosure
- Deploy to edge with MCPFusion framework
- Built in DLP, auth, and compliance on every call
- Real time usage dashboard and cost metering
- Publish to catalog or keep private
Make Your AI Do More
Start with Open Beauty Facts, then connect any of our 4,700+ other servers whenever your AI needs more. One click, no limits.
- Use this MCP plus 4,700+ others, all in one place
- Add new capabilities to your AI anytime you want
- Every connection is secured and compliant automatically
- Track usage and costs across all your servers
- Works with Claude, ChatGPT, Cursor, and more
- New servers added to the catalog every week
What you can do with this MCP connector
You're dealing with cosmetic products? This server connects your AI client straight into a massive, open database covering global beauty items. You don't need an API key; you just point your agent at this data and get real-time facts on what's in whatever makeup or skincare routine someone uses.
When you use it, your agent acts like a personal chemistry lab, letting you skip the guesswork entirely. It gives you direct access to ingredient lists, allergen flags, and full product specs, whether you're checking labels for yourself or running industry research.
To start, you can find any specific item using its barcode by calling get_beauty_product. Just feed it an EAN/UPC number, and the server spits out every detail associated with that exact beauty product. If you don't have a code, you can run a general search across entire groups of products by using search_beauty_products.
This lets your agent find listings based on broad criteria like a specific brand name or an entire category, such as 'sunscreen' or 'lip balm.'
Once the server gives you a list of results—whether from a barcode lookup or a general search—your AI client can perform deep analysis. You'll get the complete INCI ingredient list for every product found. The system analyzes formulations and flags potential allergens or restricted chemicals, so you always know what's in it.
It's gotta be fast and accurate.
So, you run a general search to pull up all products from 'Nivea,' then feed the results into the agent, which instantly pulls the full INCI list for each one and flags any known irritants or restricted substances found in those specific formulas.
How Open Beauty Facts MCP Works
- 1 Subscribe to the Open Beauty Facts MCP Server. It's public access, so no API key is needed.
- 2 Your AI client runs a command (e.g., 'What are the ingredients in X?').
- 3 The server routes the request to the appropriate tool (
get_beauty_productorsearch_beauty_products) and sends back structured product data.
The bottom line is: your agent handles the complex database queries, so you just talk to it naturally.
Who Is Open Beauty Facts MCP For?
Anyone who deals with physical products whose composition matters. Dermatologists need quick verification of patient routines. Cosmetic researchers require data to analyze market trends and ingredient usage. And consumers—anyone tired of reading tiny, confusing labels—need this.
Checks a patient's current skincare routine against known allergens or irritants before recommending new products.
Analyzes the ingredient lists across competing brands to spot market gaps or formulation trends.
Integrates open cosmetic data into a wellness app, allowing users to check product safety without leaving the platform.
What Changes When You Connect
- Stop guessing about safety. Use
get_beauty_productto instantly check a product's full ingredient list using just its barcode. This is faster than looking up the UPC manually. - Compare products across brands efficiently. Use
search_beauty_productsto pull up all body lotions from Brand X, then run an allergen check on each result. - Verify ingredients in real-time. Your agent identifies potential irritants (like specific preservatives) and flags them immediately, so you don't have to read the fine print yourself.
- Structure your research data better. The server returns clean, categorized data that lets your workflow pipeline process ingredient names or brand portfolios reliably.
- Build consumer trust automatically. Your AI client provides verifiable product facts, turning confusing labels into clear answers for your users.
Real-World Use Cases
The Dermatologist's Checkup
A patient brings in a skincare routine full of different products. Instead of manually checking each label online, the dermatologist asks their agent: 'Check these five items for known allergens.' The agent runs get_beauty_product for each barcode and flags specific ingredients like Alcohol Denat.
Market Trend Analysis
A researcher needs to compare anti-aging creams. They ask their agent to use search_beauty_products for 'Anti-Aging Cream' in a category, then run ingredient analysis on the top 10 results to see which common ingredients are used most often.
Consumer Safety Audit
A user is buying sunscreens and worries about chemicals. They ask their agent: 'Find all sunscreen products from Brand Y.' The agent uses search_beauty_products to list them, then analyzes the results for specific preservatives.
Barcode Verification
A customer has a product but can't read the label. They simply give their agent the barcode number. The agent runs get_beauty_product and immediately gives them the full name, brand, and ingredient list.
The Tradeoffs
Searching by vague concepts
Trying to ask: 'What are the best moisturizers for dry skin?' This is too broad; the tool needs a starting point.
→
Start with search_beauty_products and narrow down the category (e.g., body lotion). If you know the brand, use that criteria first.
Using search for single items
Asking: 'What are the ingredients in Nivea Creme?' While possible, it's inefficient because the tool is built for specific lookups.
→
If you have the barcode, always use get_beauty_product first. It gets the single source of truth immediately.
Ignoring ingredient limitations
Asking: 'Tell me all products that contain Glycerin.' The tool searches by product identifiers, not individual ingredients.
→
Use search_beauty_products to find a category first, then use the agent's analysis capability on the returned results.
When It Fits, When It Doesn't
You should use Open Beauty Facts if your problem centers on product composition—specifically ingredients, allergens, or brand-specific details. If you need this tool, you will either have a specific barcode (use get_beauty_product) or you know the general area/brand you're interested in (use search_beauty_products). Don't use it if your problem is logistical—like tracking inventory counts or finding sales data. For those tasks, look for dedicated e-commerce management servers instead.
Independent Platform Disclaimer: Vinkius is an independent platform and is not affiliated with, endorsed by, sponsored by, verified by, or otherwise authorized by Open Beauty Facts. All third-party trademarks, logos, and brand names are the property of their respective owners. Their use on this website is strictly for informational purposes to identify service compatibility and interoperability.
VINKIUS INFRASTRUCTURE
Cloud Hosted
Managed infra
V8 Isolated
Sandboxed per request
Zero-Trust Proxy
No stored credentials
DLP Enforced
Policy on every call
GDPR Compliant
EU data residency
Token Compression
~60% cost reduction
Works with Claude, ChatGPT, Cursor, and more
The Model Context Protocol standardizes how applications expose capabilities to LLMs. Instead of operating in isolation, your AI gains direct access to external platforms, live data, and real-world actions through secure, standardized connections.
This server provides 2 capabilities that interface natively with Claude, ChatGPT, Cursor, and any MCP client. No middleware. No custom integration required.
Available Capabilities
Reading ingredient labels shouldn't feel like a doctoral thesis.
Today, checking a single product means cross-referencing multiple websites or struggling to read tiny print. You copy the barcode, open three browser tabs—one for the brand, one for allergens, and one just for the INCI list—and spend ten minutes confirming if that retinol serum is safe for your skin type.
With this MCP server, you send the product identifier once. Your agent handles the lookup, checks the database against known irritants, retrieves the full ingredient breakdown, and presents it all in a clean summary. You get verifiable data without the manual labor.
Open Beauty Facts: Get the facts on ingredients with `get_beauty_product`.
You used to have to search through massive, messy spreadsheets or multiple API calls just to find one product's details. You had to guess which database was right and what parameters were needed.
Now, you tell your agent the barcode. It runs `get_beauty_product` and returns a single, structured data packet with every detail—ingredients, brand info, everything. The complexity is hidden from you.
Common Questions About Open Beauty Facts MCP
Can I search for products using a barcode? +
Yes! Use the get_product_by_barcode tool. It accepts EAN-13 or UPC barcodes and retrieves the specific product record if it exists in the Open Beauty Facts database.
What is the INCI list? +
INCI stands for International Nomenclature of Cosmetic Ingredients. It is the standardized system used globally to name ingredients on cosmetic packaging.
How can I find allergens in a product? +
The product details retrieved by the tools include a dedicated section for detected allergens based on the ingredient list analyzed by Open Beauty Facts.
How do I set up Open Beauty Facts if I don't have an API key? +
You don't need one; the server is open access. Just subscribe to the MCP server, and your agent can call the tools directly from any compatible client like Claude or Cursor.
What parameters should I use for `search_beauty_products`? +
You pass a category name (e.g., 'sunscreen' or 'body lotion') to the function. This lets your agent filter our entire database instantly, giving you precise lists of products.
Can I use Open Beauty Facts to audit a brand’s full product line? +
Yes. You can instruct your agent to query multiple products by brand name. This helps you compare ingredient usage or spot trends across various SKUs from one manufacturer.
If I use `get_beauty_product` with a barcode that fails, what happens? +
The tool returns a structured error stating no match was found. Your agent can then prompt you to double-check the code or try searching using the brand name instead.
Are there limitations on how many times my AI client can query the server? +
The service is optimized for high use, but extremely rapid calls might trigger temporary throttling. We suggest batching your lookups or pausing briefly between requests to maintain a steady data stream.
Use it with your favorite AI tools
Connect this server to Cursor, Claude, VS Code, and more.
More in this category
Vestiaire Collective
Search, analyze, and manage luxury resale items on Vestiaire Collective — the global community for pre-loved fashion.
Printify
Automate your print-on-demand business — manage shops, create products, and track orders directly from any AI agent.
Duoplane
Equip your AI agent to manage multi-vendor orders, track purchase orders, and monitor vendor inventory via the Duoplane API.
You might also like
Markdown Task Extractor
Instantly scan any local folder of Markdown notes (Obsidian, Notion, Logseq) and aggregate every scattered '- [ ]' to-do item into a single, structured list for your AI.
Nutritionix
Analyze food nutrition from natural language using the industry-leading NLP engine — type any meal description and get instant, precise calorie and macro data.
Celoxis
Empower your AI agents to manage complex portfolios, track project milestones, and analyze resource timesheets on Celoxis.