Skincare MCP
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| find_similar_productsB | Find skincare products with similar ingredients using Jaccard similarity |
| check_red_flagsB | Check if a product contains known irritants for sensitive skin |
| query_databaseA | Run a read-only SQL SELECT query against the local skincare SQLite database. The database has a 'products' table with columns: name, brand, Label (category), price, rank, ingredients, Combination, Dry, Normal, Oily, Sensitive (skin type flags, 0 or 1). Only SELECT statements are allowed. Example: SELECT name, brand, price FROM products WHERE Label = 'Moisturizer' AND rank >= 4.5 LIMIT 5 |
| search_live_productsA | Search Open Beauty Facts for real-time beauty product data. Useful for products not in the local database (e.g. CeraVe, La Roche-Posay). Returns product name, brand, and ingredients for each result. Limited to beauty and personal care products only. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 4 tools
Each tool has a clearly distinct purpose: checking irritants, finding similar products via Jaccard similarity, running SQL queries on a local database, and searching an external database. No overlap or ambiguity.
All tool names follow a consistent verb_noun pattern in snake_case (e.g., check_red_flags, find_similar_products, query_database, search_live_products), making them predictable and easy to parse.
With 4 tools, the set is slightly on the low side but still well-scoped for a skincare-focused MCP covering local and live data, safety checks, and similarity search. Each tool serves a distinct need without redundancy.
The tool surface covers key operations: local query, live search, ingredient safety, and similarity search. Minor gaps like a dedicated product lookup are mitigated by the SQL query tool, but advanced operations (e.g., user profiles or updates) are absent, which is acceptable for a read-only analysis server.