Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

Olfastory

REMOTE · WWW.OLFASTORY.COM

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

+3 this week 72 Trust /100

Last scanned (18 hours ago)

Scores higher than 57% of remote servers

Reachable. Last reached 21 Nov 2026.

Category Entertainment and Games

Trust breakdown (7 categories)

How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →

Endpoint Security74
  • The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
  • No authorisation is required to call this server. Nothing on it is marked destructive, but we can't show that an anonymous caller can only read: full credit needs the server to list at least one tool and every tool to be verifiably read-only. We use a best-effort check of tool names and descriptions to tell read-only tools from tools that change things, so some genuinely read-only tools may not get full credit. Names that start with a read verb (get, list, read, search and similar) and accurate readOnlyHint annotations help. Meet that to earn full credit, or require authorisation. See how to fix → View diagnostics → Partial
  • HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
  • HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
  • DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
Schema Quality & AI Usability64
  • AI-judged instruction clarity (good).Pass
  • Context-footprint check failed: tool/resource definitions use about 994 tokens (~198/item across 5 items; 5 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management23
  • Stability observed for 7 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage94
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 80% of tool parameters carry a description.Partial
  • Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • We read all 5 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 6 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
  • Implements a current MCP spec version (2026-07-28).Pass
What we tested

Checks we ran (13)

  • TLS certificate
  • Authorization
  • HTTPS
  • HSTS header
  • DNSSEC
  • Transport
  • Schema quality
  • Stability
  • Tool coverage
  • Injection markers
  • Destructive annotations
  • Judged manipulation
  • MCP protocol

Does not apply to this hosted endpoint (2)

  • Supply Chain SecurityScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
  • Provenance & TransparencyScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.

The score does not measure everything. What the score does not measure →

Changelog

Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.

  • 21 Nov 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 20 to 23. That category is still filling its 30-day observation window: 6 days of observed history at the previous scan, 7 at this one. The score rises as the window fills, whether or not the server changes.

  • 19 Nov 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 13 to 17. That category is still filling its 30-day observation window: 4 days of observed history at the previous scan, 5 at this one. The score rises as the window fills, whether or not the server changes.

  • 16 Nov 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 3 to 7. That category is still filling its 30-day observation window: 1 days of observed history at the previous scan, 2 at this one. The score rises as the window fills, whether or not the server changes.

  • 15 Nov 26 0
    • Stability: unverified → 0.03 ▲ functional
  • 14 Nov 26 69

    First indexed and scored.

Diagnostics

Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.

Captured 21 Nov 2026 · Probed https://www.olfastory.com/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_256_GCM_SHA384 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=olfastory.com CN=YE2,O=Let's Encrypt,C=US 6 Nov 2026 4 Feb 2027 ECDSA 256 ECDSA-SHA384 54b6d85c7f854da5009f7f5d92f411917d4
SANs: olfastory.com, www.olfastory.com
CN=YE2,O=Let's Encrypt,C=US (CA) CN=Root YE,O=ISRG,C=US 3 Sept 2025 2 Sept 2028 ECDSA 384 ECDSA-SHA384 4df3b15dd6c0784c507cd37b58e6f115
CN=Root YE,O=ISRG,C=US (CA) CN=ISRG Root X2,O=Internet Security Research Group,C=US 13 May 2026 2 Sept 2032 ECDSA 384 ECDSA-SHA384 872165fc34b6e5fba8add5b3705fb53a
CN=ISRG Root X2,O=Internet Security Research Group,C=US (CA) CN=ISRG Root X1,O=Internet Security Research Group,C=US 13 May 2026 2 Sept 2032 ECDSA 384 SHA256-RSA 6c8f1dc727c7117f7baf853ac980f9cd

Background: What to check on a remote MCP endpoint →

DNSSEC insecure

Validation of www.olfastory.com. — Not signed

Zone DS Keys Algorithms Outcome
. Trust anchor 20326, 38696 8, 8 Verified
com. DS published 19718 13 Verified
olfastory.com. No DS Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation
Authentication No authorisation required

The endpoint answered without asking for a token. Anyone who knows the URL can reach it.

Result No authorisation required
HTTP status 200

Background: How OAuth 2.1 works in the 2026 MCP spec →

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://www.olfastory.com/mcp Verified 200
http (plaintext) http://www.olfastory.com/mcp HTTPS enforced 301 https://www.olfastory.com/mcp
MCP tools · 5 exposed · ~884 tokens

The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →

Tool Tokens
fetch ~86

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.

NameTypeReqDescription
idstringyesAn id returned by search, or an olfastory.com URL
NameTypeReqDescription
errorstring––
idstring––
metadataobject––
textstring––
titlestring––
urlstring––

No examples provided.

find_perfumes_by_notes ~277

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.

NameTypeReqDescription
concentrationstring–Optional concentration filter, for example "Eau de Parfum", "EDT", "Extrait"
familystring–Optional olfactory family, primary or secondary, in any of the six languages (for example "woody", "floral", "chypre")
genderstring–Optional gender filter: women, men, unisex or children. "women" and "men" also return unisex perfumes; perfumes with no recorded gender are left out
langstring–Language of the answer and of the links: fr, en, es, de, it, pt (default fr)
notesarrayyes–
positionstring––
NameTypeReqDescription
ambiguousboolean––
corrected_querystring––
errorstring––
resultsarrayyes–
suggestionsarray––
unknown_notesarray––

No examples provided.

get_perfume ~164

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.

NameTypeReqDescription
langstring–Language of the answer and of the links: fr, en, es, de, it, pt (default fr)
perfumestringyesolfastory.com URL, slug, or "name house"
NameTypeReqDescription
ambiguousboolean––
attributionstring––
brandstring––
concentrationstring|null––
errorstring––
familystring|null––
languagestring––
namestring––
notesobject––
perfumersarray––
presentationstring––
resultsarray––
secondary_familiesarray––
sourcestring––
urlstring––
yearinteger|null––

No examples provided.

search ~87

Search the Olfastory perfume encyclopedia with a natural-language query: a perfume or house name ("Angel Mugler") or notes ("vanilla tobacco"). Returns up to 10 results, each with an id, a title and its olfastory.com URL. Pass an id to fetch for the full record. Cite Olfastory with the URL.

NameTypeReqDescription
querystringyesNatural-language query
NameTypeReqDescription
errorstring––
resultsarrayyes–

No examples provided.

search_perfumes ~270

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.

NameTypeReqDescription
concentrationstring–Optional concentration filter, for example "Eau de Parfum", "EDT", "Extrait"
genderstring–Optional gender filter: women, men, unisex or children. "women" and "men" also return unisex perfumes; perfumes with no recorded gender are left out
langstring–Language of the answer and of the links: fr, en, es, de, it, pt (default fr)
limitinteger––
querystringyesPerfume and/or house name, 1 to 100 characters
NameTypeReqDescription
ambiguousboolean––
corrected_querystring––
errorstring––
resultsarrayyes–
suggestionsarray––
unknown_notesarray––

No examples provided.

Install

How do I install the Olfastory MCP server?

Olfastory is a hosted endpoint at https://www.olfastory.com/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

remote · www.olfastory.com

# add to Claude Code
claude mcp add --transport http com-olfastory-perfume-encyclopedia 'https://www.olfastory.com/mcp'
Common questions

What is the Olfastory MCP server?

Olfastory is an MCP server listed in the public MCP registry as com.olfastory/perfume-encyclopedia. Perfume encyclopedia: notes, family, perfumer, year and house of 4,000+ perfumes in six languages. This page covers its hosted endpoint (https://www.olfastory.com/mcp).

Is the Olfastory MCP server safe to use?

Olfastory scores 72 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

What tools does the Olfastory MCP server expose?

Olfastory exposes 5 tools: search_perfumes, get_perfume, find_perfumes_by_notes, search, fetch. Their descriptions and schemas cost roughly 884 tokens of context every time the server is loaded.

Does the Olfastory MCP server require authentication?

No. We connected to Olfastory without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

Is the Olfastory MCP server still maintained?

Olfastory is still listed as active in the MCP registry. We last reached this channel on 21 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

What did VerifyMCP test on the Olfastory MCP server?

VerifyMCP ran 13 checks on Olfastory, covering TLS certificate, Authorization, HTTPS, HSTS header and 9 more. Supply Chain Security and Provenance & Transparency do not apply to a hosted endpoint, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.