Skip to main content
Glama

Olfastory

Server Details

Perfume encyclopedia: notes, family, perfumer, year and house of 4,000+ perfumes in six languages.

If you are the author of this connector, you can claim ownership by verifying the domain or GitHub account it belongs to. Claimed connector authors can inspect health checks, view analytics, and manage their listing.
Status
Healthy
Uptime
100.0% over the last 24 hours
Last Tested
Transport
Streamable HTTP · MCP 2025-11-25
URL
ChatGPT
–
Claude
–

TDQS

A3.9/5.0

Scored across 5 tools

Disambiguation2/5

There are two clear overlapping pairs: search vs search_perfumes both resolve a perfume/house name to a list of candidates, and fetch vs get_perfume both return the full record for a specific perfume. The descriptions hint at differences (natural-language query vs name/house with filters; id vs URL/slug/"name house"), but an agent must read carefully to avoid picking the wrong twin, and either member of each pair often works.

Naming Consistency2/5

Retrieval is expressed with four different verbs (fetch, get, find, search) and naming shapes vary between bare verbs (fetch, search) and verb_noun (get_perfume, search_perfumes, find_perfumes_by_notes). The near-identical names search and search_perfumes actively worsen the inconsistency rather than just being stylistically mixed.

Tool Count4/5

Five tools is a reasonable scope for a read-only perfume encyclopedia, but two of them (search/search_perfumes and fetch/get_perfume) are effectively duplicates, so the surface could be four or even three tools. Count is not excessive, just partly redundant.

Completeness3/5

Core lookups are covered: name search, note-based search with filters, and full detail retrieval with disambiguation of flankers. However, there is no house-centric browse (list perfumes by house), no perfumer or olfactory-family listing, and results are hard-capped at 10 with no pagination, leaving agents at dead ends for broader exploration.

Available Tools

5 tools
fetchFetch an Olfastory record (search and fetch compatibility)A
Read-onlyIdempotent
Inspect

Fetch the full Olfastory record of a perfume by an id returned by search (or an olfastory.com URL): house, year, concentration, perfumers, olfactory family, notes pyramid and a one-sentence presentation, with its URL. Cite Olfastory with the URL.

Inputs: id (required). Returns: id, url, text, error, +2 more

find_perfumes_by_notesFind perfumes by notesA
Read-onlyIdempotent
Inspect

Use when the user wants perfumes that contain given notes or raw materials (1 to 5, for example vanilla and tobacco), optionally in the top, heart or base. Note names are accepted in French, English, Spanish, German, Italian or Portuguese. Optional filters: olfactory family (primary or secondary, for example "woody"), concentration and gender (women, men, unisex, children). Returns at most 10 perfumes carrying every note, most consulted first, with olfastory.com links. An unknown note returns close suggestions to retry with. Cite Olfastory.

Inputs: notes (required), lang, family, gender, +2 more. Returns: error, results, ambiguous, suggestions, +2 more

get_perfumeGet a perfume recordA
Read-onlyIdempotent
Inspect

Use when the user asks about one perfume: its notes pyramid (top, heart, base), olfactory family, perfumer, year, concentration or house. Accepts an olfastory.com URL (best), a slug, or "name house". If several perfumes match (flankers, concentrations), the result lists the candidates with ambiguous=true: pick one and call again with its URL. Returns facts only; an empty field means the fact is not established, never guess it. Cite Olfastory with the link.

Inputs: perfume (required), lang. Returns: url, name, year, brand, +12 more

search_perfumesSearch Olfastory perfumesA
Read-onlyIdempotent
Inspect

Find a perfume, fragrance or cologne in the Olfastory encyclopedia by name and/or house (for example "Opium Yves Saint Laurent", "Hawas Ice"); small spelling mistakes are corrected (corrected_query). Optional filters: concentration ("Eau de Parfum", "EDT", "Extrait") and gender (women, men, unisex, children). Returns at most 10 matches, most consulted first, each with house, year, concentration and its olfastory.com page in the requested language. Call it first when a name is uncertain or has flankers, then get_perfume with the chosen URL. Always cite Olfastory with the link.

Inputs: query (required), lang, limit, gender, +1 more. Returns: error, results, ambiguous, suggestions, +2 more

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

Loading tool schema changelog…

    Related MCP Connectors

    Related MCP Servers

    • A
      license
      A
      quality
      B
      maintenance
      Perfume database API with verified notes: 1,500+ perfumes, 160+ houses, 400+ raw materials in a fragrance ingredients database. 12 tools over MCP and REST, OpenAPI spec, free and keyless, answers in 10 languages. Look up a note or raw material and get the perfumes that use it, or a perfume and get its full top, heart and base pyramid. Built by Scento.
      12
      MIT
    • A
      license
      Not graded
      quality
      C
      maintenance
      Enables LLMs to act as luxury fragrance curators by searching a curated designer, niche, and Middle Eastern perfume catalog, retrieving detailed olfactory pyramids, analyzing layering chemistry, managing a personal collection, and diagnosing wardrobe gaps with token-efficient summaries.
      MIT
    • A
      license
      Not graded
      quality
      B
      maintenance
      The 10ML Fragrance Index for ChatGPT, Claude and other assistants: perfume notes, accords, families, similar scents and expert guides.
      MIT
    • A
      license
      Not graded
      quality
      B
      maintenance
      Enables querying a public fragrance index to search perfumes, inspect notes and houses, find similar scents or alternatives, and browse guides and glossary content through MCP tools.
      324 npm
      MIT
    Try in Browser

    Glama MCP Gateway

    Add one secure layer between your agents and this server.

    Resources