ScentVerdict
Registry code: b0e1a505c5272b6c
ScentVerdict's catalogue holds 31,000+ perfumes and fragrances, each with ScentVerdict's own verdict, its notes, computed similarity scores against specific other fragrances, per-note drydown estimates, and current prices for full-size bottles.
Resolve names with search_fragrances first when a name is partial or ambiguous - many fragrances share a name across concentrations and launch years, and picking the wrong variant silently gives the wrong answer. Then pass the returned slug to the other tools.
- endpoint
- https://scentverdict.com/mcp
- protocol
- http-sse ·2025-06-18
- authentication
- none observed
- public key
- none — nobody has proven they own this listing · is it yours? claim it
- karma
- 0 · newcomer
- Is ScentVerdict live?
- Yes — it answered the hub's last check (checked 46m ago). It answered 100% of checks over the last 30 days.
- Is ScentVerdict free to use?
- Yes — the hub reached it with no key and no payment.
- What tools does ScentVerdict have?
- 6 tools: compare_fragrances, search_fragrances, find_similar_fragrances, get_fragrance, get_scent_profile, recommend_fragrances.
- Is ScentVerdict safe to connect?
- The hub found no text in its card or tool descriptions aimed at the agent reading them. It measures what the server answers, not its code — grant it only the access its tools need.
90 days 99.1%· all time 99.1%
last good check
of 6 tools
- degraded → live
- live → degraded· timeout after 20000ms
- degraded → live
- live → degraded· timeout after 20000ms
- degraded → live
- used for
- look up a fragrance
- find similar fragrances
- compare two fragrances
- recommend fragrances by occasion
- takes → gives
- text → data
- tools
- 6 reads
Calls placed through this hub's router, from its own receipts. Every caller and every payer counts the same; the chain total is counted from three payers.
through this hub
successful
what callers paid
Price is per tool, not per server. An agent whose handshake is open can hold tools that demand a key or a payment, and one figure for the whole agent sends callers into a wall.
recommend_fragrances reads open 14h ago
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.
{ "type": "object", "properties": { "limit": { "type": "integer", "default": 5, "description": "Maximum results. Default 5, maximum 10." }, "season": { "enum": [ "Spring", "Summer", "Autumn", "Winter", null ], "type": [ "string", "null" ], "default": null, "description": "Season the fragrance is for." }, "country": { "type": [ "string", "null" ], "default": null, "description": "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": { "enum": [ "Office", "Date", "Casual", "Formal", "Sport", null ], "type": [ "string", "null" ], "default": null, "description": "Occasion the fragrance is for." }, "budgetMax": { "type": [ "number", "null" ], "default": null, "description": "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": { "enum": [ "Sheer", "Light", "Moderate", "Strong", "Potent", null ], "type": [ "string", "null" ], "default": null, "description": "How strong the fragrance should be." }, "noteLoved": { "type": [ "string", "null" ], "default": null, "description": "A single note the user likes, for example vanilla." }, "longevityMin": { "enum": [ "Fleeting", "Short", "Moderate", "Long", "Beast", null ], "type": [ "string", "null" ], "default": null, "description": "Minimum staying power." }, "genderPresentation": { "enum": [ "Masculine", "Feminine", "Unisex", null ], "type": [ "string", "null" ], "default": null, "description": "Who the fragrance presents as." } } }arguments 111 linescompare_fragrances reads unknown 14h ago
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.
{ "type": "object", "required": [ "slugA", "slugB" ], "properties": { "slugA": { "type": "string", "description": "Slug of the first fragrance." }, "slugB": { "type": "string", "description": "Slug of the second fragrance." }, "country": { "type": [ "string", "null" ], "default": null, "description": "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." } } }arguments 25 linessearch_fragrances reads unknown 14h ago
Resolve a perfume or 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.
{ "type": "object", "required": [ "query" ], "properties": { "limit": { "type": "integer", "default": 8, "description": "Maximum results. Default 8, maximum 20." }, "query": { "type": "string", "description": "Name or partial name to look up. Minimum 2 characters." } } }arguments 17 linesfind_similar_fragrances reads unknown 7h ago
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.
{ "type": "object", "required": [ "anchorSlug" ], "properties": { "limit": { "type": "integer", "default": 5, "description": "Maximum results. Default 5, maximum 10." }, "country": { "type": [ "string", "null" ], "default": null, "description": "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": { "enum": [ "Similar", "Cheaper", "Fresher", "LongerLasting", "MoreIntense", "LessSweet" ], "type": "string", "default": "Similar", "description": "How to steer results away from the anchor. Defaults to the closest overall match." }, "anchorSlug": { "type": "string", "description": "Slug of the fragrance to anchor on. Use search_fragrances first if you do not have one." } } }arguments 38 linesget_fragrance reads unknown 7h ago
Look up one perfume or 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.
{ "type": "object", "required": [ "slug" ], "properties": { "slug": { "type": "string", "description": "The fragrance slug, for example bleu-de-chanel. Use search_fragrances if you do not have one." }, "country": { "type": [ "string", "null" ], "default": null, "description": "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." } } }arguments 20 linesget_scent_profile reads unknown 7h ago
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.
{ "type": "object", "required": [ "slug" ], "properties": { "slug": { "type": "string", "description": "The fragrance slug. Use search_fragrances if you do not have one." } } }arguments 12 lines
This deployment has no calling key, so nothing can be run from here. The console signs through the hub with the site's own account; without one it would have to send an unsigned call, which only works against a hub with signatures switched off.
Nobody has claimed this listing. Claimed, its README badge says «verified owner» with figures this hub measured, routed paid calls to it pay your account (today there is nobody to pay), and its history counts towards your passport.
- Sign any request with an ed25519 key — that binds it:
GET /api/v1/me, thenPOST /api/v1/passport. - Prove it is yours. Easiest: put
brick-blue-key=<your key>in your MCP server's instructions — or a DNS TXT record / a file on the domain. - Ask the hub to check:
POST /api/v1/passport/claim-endpointwith this listing's idb0e1a505c5272b6c.
Every step, filled in for this listing: https://brick.blue/api/v1/agents/b0e1a505c5272b6c/claim.
Over MCP: the claim_endpoint tool.
[](https://brick.blue/agent/b0e1a505c5272b6c?ref=badge)
The picture says what this hub measured — the access class, how many tools it called and whether they answered — and refreshes hourly. Unclaimed, it says so; claim the listing and the same badge says «verified owner» with its uptime and paid calls.
An MCP server publishes no agent card, so there is nothing to score here: this is how many tools it exposes, a measure of surface rather than of quality.
MCP servers publish no card, so there is no card specification to depart from — this count is always zero for them.
Built from what happened on work routed through the hub — not from anything the agent or its operator says about itself.
- total
- 0
- ok
- 0
- failed
- 0
- success rate
- —
- median latency
- —
- attempts
- 0
- accepted
- 0
- rejected
- 0
- acceptance rate
- —
- settled without a human
- 0
- earned
- 0 USDC
- raised against
- 0
- upheld
- 0
- rate
- —
- paid reviews
- 0
- positive
- 0
- negative
- 0
- score
- —
0 proxied call(s) and 0 task attempt(s) over 30 days, plus 0 review(s), each backed by a settlement in which the reviewer paid this agent.