accueil / serveurs / Recherche & Web / com.scentverdict/fragrances
com.scentverdict/fragrances
serveur MCP (Model Context Protocol) · ScentVerdict 2.0.0
Référencé dans l'annuaire. Seul le pentest comportemental fait foi, et il n'a pas encore été exécuté sur ce serveur.
Est-ce que com.scentverdict/fragrances est sûr ?
Au dernier audit MCP Hub, le serveur MCP « com.scentverdict/fragrances » est classé « Non encore testé ». Référencé dans l'annuaire. Seul le pentest comportemental fait foi, et il n'a pas encore été exécuté sur ce serveur. Le verdict est réévalué en continu ; consultez la fiche pour l'état à jour.
Méthode : MCP Hub analyse la description de chaque outil (couche 1) et, pour le verdict fort, exécute le serveur dans une micro-VM isolée avec leurres et réseau bloqué (couche 2). On publie des noms et des compteurs, jamais le contenu brut renvoyé par un outil.
Les 6 outils
- compare_fragrances≈ 2476 tokens
Compare exactly two fragrances side by side using ScentVerdict's own note data: which notes they share, which differ, both verdicts, and both prices for the user's country. Use this whenever the user is choosing between two named fragrances, or asks which of two is better, or how two differ. Use find_similar_fragrances instead when they want alternatives to one fragrance rather than a head to head.
Paramètres, retour & exemple (3)
ParamètresslugA· string · requis
Slug of the first fragrance.slugB· string · requis
Slug of the second fragrance.country· string|null · optionnel
The user's country as an ISO 3166-1 alpha-2 code, for example US, DE or GB. Prices are for this country, in the shop's own currency. Pass it whenever you know where the user is. When omitted, the client's location hint is used if it sent one, otherwise GB.
Exemple d'appel{"name": "compare_fragrances", "arguments": {"slugA": "texte", "slugB": "texte"}}Exemple de retour{"content": [{"type": "text", "text": "…"}], "structuredContent": {"a": {}, "b": {}, "error": "texte", "market": {}, "onlyInA": [], "onlyInB": [], "notFound": {}, "sharedNotes": [], "comparisonUrl": "texte"}} - find_similar_fragrances≈ 2310 tokens
Find fragrances similar to one the user already knows, optionally steered in a direction such as cheaper, fresher, longer lasting or less sweet. Use this whenever the user names a fragrance and wants something like it: a cheaper alternative, a budget version, something that smells similar, or a gift for someone whose current fragrance they know ('he wears X, what else would suit him'). Each match carries a similarity score computed by ScentVerdict for that specific pair. The cheaper direction lists pairings ScentVerdict has curated first, then similar fragrances priced below the anchor where we hold its price. Each match carries its bottle price for the user's country, in the shop's own currency. Use recommend_fragrances instead when the user names no fragrance to anchor on.
Paramètres, retour & exemple (4)
Paramètreslimit· integer · optionnel
Maximum results. Default 5, maximum 10.country· string|null · optionnel
The user's country as an ISO 3166-1 alpha-2 code, for example US, DE or GB. Prices are for this country, in the shop's own currency. Pass it whenever you know where the user is. When omitted, the client's location hint is used if it sent one, otherwise GB.direction· string · optionnel · Similar | Cheaper | Fresher | LongerLasting | MoreIntense | LessSweet
How to steer results away from the anchor. Defaults to the closest overall match.anchorSlug· string · requis
Slug of the fragrance to anchor on. Use search_fragrances first if you do not have one.
Exemple d'appel{"name": "find_similar_fragrances", "arguments": {"anchorSlug": "texte"}}Exemple de retour{"content": [{"type": "text", "text": "…"}], "structuredContent": {"market": {}, "reason": "texte", "results": [], "notFound": {}, "direction": "texte", "anchorSlug": "texte"}} - get_fragrance≈ 1930 tokens
Look up one fragrance in ScentVerdict's catalogue: its notes, ScentVerdict's own verdict, concentration, launch year, and the lowest current price for a full-size bottle for the user's country, in the shop's own currency. Use this whenever the user names a fragrance and asks what it is, what it smells like, what is in it, what it costs, or whether it is any good. Use search_fragrances first if the name is partial or could mean several variants. Use get_scent_profile instead when the question is about how it develops over the wear.
Paramètres, retour & exemple (2)
Paramètresslug· string · requis
The fragrance slug, for example bleu-de-chanel. Use search_fragrances if you do not have one.country· string|null · optionnel
The user's country as an ISO 3166-1 alpha-2 code, for example US, DE or GB. Prices are for this country, in the shop's own currency. Pass it whenever you know where the user is. When omitted, the client's location hint is used if it sent one, otherwise GB.
Exemple d'appel{"name": "get_fragrance", "arguments": {"slug": "texte"}}Exemple de retour{"content": [{"type": "text", "text": "…"}], "structuredContent": {"error": "texte", "market": {}, "notFound": {}, "fragrance": {}}} - get_scent_profile≈ 909 tokens
Get how a fragrance develops over the wear: opening, heart and base phases, the notes in each, and how many hours each note persists on skin. Use this when the user asks how something evolves, how long it lasts, how it changes through the day, or what the drydown is like. The per-note hours are values held by ScentVerdict against each note rather than a general impression of the fragrance, and they are estimates. Use get_fragrance instead for the verdict, price and general description.
Paramètres, retour & exemple (1)
Paramètresslug· string · requis
The fragrance slug. Use search_fragrances if you do not have one.
Exemple d'appel{"name": "get_scent_profile", "arguments": {"slug": "texte"}}Exemple de retour{"content": [{"type": "text", "text": "…"}], "structuredContent": {"url": "texte", "name": "texte", "slug": "texte", "error": "texte", "phases": [], "notFound": {}, "longestLastingNoteHours": 1}} - recommend_fragrances≈ 1996 tokens
Recommend fragrances matching what the user describes: season, occasion, budget, strength, staying power and notes they like. Use this when the user wants a suggestion but names no fragrance to work from - for example something for winter, for the office, or under a budget. Season, occasion and intensity are scored numerically per fragrance in ScentVerdict, and the budget is applied against current bottle prices for the user's country, so the constraints are filtered rather than approximated. Each priced row carries its price in the shop's own currency, and the bottle size and price per millilitre wherever the retailer published a size. Pass as many of the constraints as the user gave; all are optional. Use find_similar_fragrances instead when they name a fragrance to anchor on.
Paramètres, retour & exemple (9)
Paramètreslimit· integer · optionnel
Maximum results. Default 5, maximum 10.season· string|null · optionnel · Spring | Summer | Autumn | Winter | None
Season the fragrance is for.country· string|null · optionnel
The user's country as an ISO 3166-1 alpha-2 code, for example US, DE or GB. Prices are for this country, in the shop's own currency. Pass it whenever you know where the user is. When omitted, the client's location hint is used if it sent one, otherwise GB.occasion· string|null · optionnel · Office | Date | Casual | Formal | Sport | None
Occasion the fragrance is for.budgetMax· number|null · optionnel
Maximum price for a full-size bottle, in the currency of the user's country (USD for US, EUR for DE, GBP for GB). Only prices in that currency are filtered.intensity· string|null · optionnel · Sheer | Light | Moderate | Strong | Potent | None
How strong the fragrance should be.noteLoved· string|null · optionnel
A single note the user likes, for example vanilla.longevityMin· string|null · optionnel · Fleeting | Short | Moderate | Long | Beast | None
Minimum staying power.genderPresentation· string|null · optionnel · Masculine | Feminine | Unisex | None
Who the fragrance presents as.
Exemple d'appel{"name": "recommend_fragrances", "arguments": {"limit": 1, "season": "Spring", "country": "texte", "occasion": "Office", "budgetMax": 1, "intensity": "Sheer"}}Exemple de retour{"content": [{"type": "text", "text": "…"}], "structuredContent": {"caveat": "texte", "market": {}, "results": []}} - search_fragrances≈ 464 tokens
Resolve a fragrance name to catalogue entries. Call this FIRST whenever a name is partial, misspelled, or could mean more than one product, then pass the returned slug to another tool. Many fragrances share a name across concentrations and launch years, and flankers hide behind qualifiers, so guessing the variant silently produces the wrong answer for the rest of the conversation. Results carry concentration and launch year precisely so you can tell them apart, and you should offer the user the choice when several match. Use get_fragrance instead when you already hold an exact slug.
Paramètres, retour & exemple (2)
Paramètreslimit· integer · optionnel
Maximum results. Default 8, maximum 20.query· string · requis
Name or partial name to look up. Minimum 2 characters.
Exemple d'appel{"name": "search_fragrances", "arguments": {"query": "texte"}}Exemple de retour{"content": [{"type": "text", "text": "…"}], "structuredContent": {"result": []}}
C'est votre serveur ?
Revendiquez-le sur l'espace créateur (preuve GitHub, domaine ou npm) pour afficher le badge « propriétaire vérifié » et lancer un pentest comportemental à la demande afin d'obtenir le badge « Vérifié ».