Skip to content

Olfastory MCP server

com.olfastory/perfume-encyclopediaolfastory.comstreamable-httpv1.3.0Scanned

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

5 tools: 5 only read.

Tools: 0 delete, 0 irreversible, 0 write, 5 read.
  • Reads private data · 4
  • Reads text others write · 1
  • Can send data out · 0
  • No findings

Tools listed without sign-in. Remote posture

With Anlyon

Decide which of this server's tools your agent can use.

  • Anlyon lists the tools and adopts none.
  • Each tool you adopt gets approvals and receipts.
  • Your agent never holds the key.
Govern this server →

A tool your agent calls directly is not routed through Anlyon and is not governed by it. Anlyon Radar only lists and labels, and these labels are the same either way.

What the Olfastory MCP server can do

The Olfastory MCP server is published by olfastory.com, a domain the MCP Registry verified. It has 5 tools. Every one of them only reads: going by their definitions, none of them creates, changes, sends or deletes anything.

4 tools read private data (get_perfume, find_perfumes_by_notes, search and 1 more); 1 tool brings in text other people can write (fetch).

None of the fixed checks matched anything in its tool definitions. That is not a safety guarantee.

Its remote endpoint lists its tools without sign-in, and its tools changed once since Anlyon Radar first saw them.

Last scanned Nov 14, 2026, version 1.3.0.

Tools

Grouped by what each tool does, most consequential first. Open one for its reasons and full description; descriptions are the publisher's own words.

5 tools

Only reads 5Show 5 read-only tools
  • fetchFetch 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…Reads private dataReads text others writeNo findings

    Why it is in this group

    • The name "fetch" says "fetch": a word for reading.

    What it can reach

    • private-dataThe description's first sentence says "fetch" and "note": it reads notes.
    • untrusted-inputThe description's first sentence says "fetch" and "url": it reads web pages, which anyone can write.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
  • find_perfumes_by_notesUse 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.Reads private dataNo findings

    Why it is in this group

    • The name "find_perfumes_by_notes" says "find": a word for reading.

    What it can reach

    • private-dataThe name "find_perfumes_by_notes" says "find" and "note": it reads notes.
    • private-dataThe description's first sentence says "note": it reads notes.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
  • get_perfumeUse when the user asks about one perfume: its notes pyramid (top, heart, base), olfactory family, perfumer, year, concentration or house.Reads private dataNo findings

    Why it is in this group

    • The name "get_perfume" says "get": a word for reading.

    What it can reach

    • private-dataThe description's first sentence says "note": it reads notes.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
  • search_perfumesFind 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…No findings

    Why it is in this group

    • The name "search_perfumes" says "search": a word for reading.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false

This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.

Exfil surface

Which tools read private data, which read text someone else can write, and which can send data out. One of each is a path a prompt injection can use.

No private-data, untrusted-input, outbound path in this server alone: no tool is tagged outbound.

Reads private data4
Reads files, mail, messages, databases, secrets, calendars or repositories.
Reads text others write1
Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
Can send data out0
Can carry data to people or systems: it sends, posts or publishes, or takes a recipient, channel or URL.

Other servers in the same agent add their own tools to these paths. Audit your whole setup to see them together.

Remote posture

What anyone on the internet sees at the remote endpoint: an anonymous initialize and tools/list, and the public OAuth metadata.

Tools listed without sign-in

Looked at Nov 15, 2026, 13:18 UTC, unchanged since Nov 15, 2026. No credentials were sent and no tool was called. What is looked at.

Reachable
yes
HTTP status of an anonymous initialize
200
tools/list served without credentials
yes
Tools that change things, listed without credentials
0
Protocol version
2025-06-18
WWW-Authenticate on 401
not observed
resource_metadata in WWW-Authenticate
not observed
RFC 9728 protected resource metadata
not observed
Authorization servers
not observed
Legacy HTTP+SSE transport
no
Dynamic client registration
not observed
Client ID metadata documents
not observed

Findings

Matches of fixed checks, with the text they matched.

No check matched anything in these tool definitions. That is not a safety guarantee.

History

Changes to its tool definitions and to its remote endpoint, newest first.

  1. Tools2 changed.~2 changedView diff

Install

Pinned to version 1.3.0. Values in angle brackets are yours to fill in.

claude mcp add --transport http perfume-encyclopedia https://www.olfastory.com/mcp
claude mcp add --transport http perfume-encyclopedia https://www.olfastory.com/mcp

Run in a terminal.

Claude Code permissions

Allow the reads, ask before a change or a way out, deny the deletes. Paste into .claude/settings.json.

.claude/settings.json
{
  "permissions": {
    "allow": [
      "mcp__perfume-encyclopedia__search_perfumes",
      "mcp__perfume-encyclopedia__get_perfume",
      "mcp__perfume-encyclopedia__find_perfumes_by_notes",
      "mcp__perfume-encyclopedia__search",
      "mcp__perfume-encyclopedia__fetch"
    ],
    "ask": [],
    "deny": []
  }
}

Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. A read that can send data out (it takes a URL, say) asks first too. It assumes the server is installed as perfume-encyclopedia. Review it before you use it.

Capability tags behind 4 rules
  • mcp__perfume-encyclopedia__get_perfume private-data
  • mcp__perfume-encyclopedia__find_perfumes_by_notes private-data
  • mcp__perfume-encyclopedia__search private-data
  • mcp__perfume-encyclopedia__fetch private-data, untrusted-input

Pin

Keep the decision: fail CI when the tools change, follow every change, or show a badge.

Pin in CI

Fail a build when the tools you reviewed are not the tools the server serves today.

curl -s "https://radar.anlyon.com/api/v1/servers/com.olfastory/perfume-encyclopedia/verify?hash=a1bab7dc98606a15c19b814fe2266d4e334b72b6df0b3f7cb6cc858218c6eba9" | jq -e '.changed == false'

Pinned hash a1bab7dc9860, from Nov 14, 2026, 22:18 UTC.

Watch

Get told when its tools change: a new tool, a new description, a new class.

https://radar.anlyon.com/servers/com.olfastory/perfume-encyclopedia/changes.xml

An Atom feed. Works in any feed reader or Slack's RSS app.

Badge

Anlyon Radar badge for com.olfastory/perfume-encyclopedia
[![Anlyon Radar](https://radar.anlyon.com/badge/com.olfastory/perfume-encyclopedia.svg)](https://radar.anlyon.com/servers/com.olfastory/perfume-encyclopedia)

Source: MCP Registry. Synced Nov 14, 2026, 22:17 UTC.

Olfastory MCP server: questions and answers

Answered from the scan above, not from the publisher's description.

Is the Olfastory MCP server safe?

No scan can promise that. What its definitions show: 5 tools, all of which only read, and 0 findings from fixed checks. Read-only tools can still pass private data to a model.

Can the Olfastory MCP server delete data?

No tool is classed as destructive: going by their definitions, none of them deletes, cancels or revokes anything.

Can the Olfastory MCP server do things that cannot be undone?

No tool is classed as irreversible: none of them sends, pays, publishes or merges, going by their definitions.

What tools does the Olfastory MCP server have?

5 tools: 5 read. search_perfumes, get_perfume, find_perfumes_by_notes, search and fetch.

Does the Olfastory MCP server need sign-in or OAuth?

Its remote endpoint listed its tools to an anonymous client, without sign-in.

Does the Olfastory MCP server send data to outside services?

None of its tools sends, posts or publishes, or takes a recipient, channel or URL.

Has the Olfastory MCP server changed its tools?

Yes, once since Anlyon Radar started tracking it, most recently on Nov 14, 2026. Every change is on this page and in its Atom feed.