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.

Perfume Picks

NPM · PERFUME-PICKS-MCP · 2 COMPONENTS

Search the Perfume Picks fragrance database: 10,000+ scents with notes, dupes, and wear data.

−3 this week 77 Trust /100

Last scanned (13 hours ago)

Scores higher than 55% of npm servers

Category E-commerce

Trust breakdown (7 categories)

How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score → Why this is hard to score →

Supply Chain Security81
  • No malware found by supply-chain analysis.Pass
  • CVE check failed: a known high-severity CVE affects zod 3.25.76, a direct dependency. A fixed version is available. View diagnostics → Fail
  • No install/post-install scripts declared.Pass
  • 30 of 95 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency45
Schema Quality & AI Usability82
  • AI-judged instruction clarity (excellent).Pass
  • Tool/resource definitions use about 756 tokens (~94/item across 8 items; 8 tools + 0 resources), lean.Pass
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management77
  • Stability observed for 23 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 100% of tool parameters carry a description.Pass
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • We read all 8 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 8 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
  • Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
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.

  • 5 Nov 26 −3
    • Stability: pass → 0.77 functional
  • 24 Oct 26 −5
    • CVE-2023-54404 affects this package: high ▼ security
    • Known CVEs: pass → fail ▼ security
    • Stability: 0.97 → pass security
  • 23 Oct 26 +1
    • Security disclosure: unverified → fail ▼ functional
  • 22 Oct 26 −1
    • Security disclosure: fail → unverified ▼ functional
    • Stability: pass → 0.93 functional
  • 16 Oct 26 0
    • Stability: 0.97 → unverified ▼ security
    • Tool safety: pass → unverified ▼ security
    • Stability: 0.97 → pass security
    • Capabilities: pass → unverified ▼ functional
    • Tool coverage: 100 → unverified ▼ functional
    • First check of Schema quality: unverified functional
    • Package version: 1.0.2 → 1.0.5 functional
  • 15 Oct 26 +1

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

  • 13 Oct 26 +1
    • Security disclosure: unverified → fail ▼ functional
  • 11 Oct 26 +1
    • Security disclosure: fail → unverified ▼ functional
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 5 Nov 2026 · Analysed npm/perfume-picks-mcp@1.0.5

Provenance No attestation

The registry publishes no build provenance for this version, so there is nothing to verify.

Result No attestation
Ecosystem npm

Background: How many MCP packages publish verified provenance →

Vulnerabilities 1 finding
ID CVE Severity Vector Fix available
GHSA-mrhx-c7xc-m3w5 CVE-2023-54404 high CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H yes

Background: What a vulnerability scan can and cannot prove →

Dependencies 95 packages
Packages resolved 95
Stale 30
Tree resolution Complete

Background: SBOMs and build attestations, explained →

MCP tools · 8 exposed · ~756 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
compare_fragrances ~66

Side-by-side comparison: note pyramids, shared and distinct accords, longevity/sillage/compliment scores, concentration, and price difference.

NameTypeReqDescription
fragrance_astringyesFirst fragrance — slug or name
fragrance_bstringyesSecond fragrance — slug or name

No output schema declared.

No examples provided.

find_dupes ~63

Curated dupes for a fragrance — cheaper scents documented to smell like the original, with match percentage and price comparison. The answer to 'what smells like X without the price tag'.

NameTypeReqDescription
fragrancestringyesFragrance slug or name to find dupes for

No output schema declared.

No examples provided.

find_similar ~58

Fragrances most similar to a given one, from Perfume Picks' precomputed similarity ranking over notes and accords.

NameTypeReqDescription
fragrancestringyesFragrance slug or name
limitinteger–Max results (default 5)

No output schema declared.

No examples provided.

get_fragrance ~71

Detailed record for one fragrance: full note pyramid (top/heart/base), accords, concentration, community longevity/sillage/compliment scores, and MSRP. Accepts a Perfume Picks slug or a name like 'Bleu de Chanel'.

NameTypeReqDescription
slug_or_namestringyesFragrance slug or name

No output schema declared.

No examples provided.

get_recommendations ~138

Personalized fragrance picks from note/accord preferences (e.g. 'vanilla', 'oud', 'citrus'), a budget in USD, an occasion ('office', 'date night', 'gift', 'signature scent'), and gender presentation.

NameTypeReqDescription
budgetnumber–Max MSRP in USD
genderstring–Marketed gender category of the fragrance; omit to include all
limitinteger–Max results (default 5)
occasionstring–What the fragrance is for
preferencesarrayyesNotes or accords the wearer enjoys, e.g. ['vanilla','amber','rose']

No output schema declared.

No examples provided.

search_fragrances ~167

Full-text search across 10,000+ fragrances in the Perfume Picks database. Filter by brand, fragrance family, gender, and MSRP (USD). Returns note pyramids, accords, and community wear scores with source attribution.

NameTypeReqDescription
brandstring–Brand name filter, e.g. 'Dior'
fragrance_familystring–Family filter, e.g. 'woody', 'amber', 'fresh'
genderstring–Marketed gender category of the fragrance; omit to include all
limitinteger–Max results (default 10)
price_maxnumber–Maximum MSRP in USD
price_minnumber–Minimum MSRP in USD
querystring–Free-text search: fragrance or brand name

No output schema declared.

No examples provided.

trending_fragrances ~64

Fragrances Perfume Picks users are adding to their wardrobes most over the last 30 days (falls back to catalog popularity when live activity data is unavailable). The method used is labeled in the response.

NameTypeReqDescription
limitinteger–Max results (default 10)

No output schema declared.

No examples provided.

what_to_wear_tonight ~129

A fragrance suggestion for right now, based on mood, occasion (e.g. 'date', 'office tomorrow', 'night out', 'cozy evening in'), and season — scored with Perfume Picks' community compliment, office-safety, and versatility data.

NameTypeReqDescription
genderstring–Marketed gender category of the fragrance; omit to include all
moodstring–How you're feeling
occasionstring–The setting
seasonstring–Season to weight the pick toward — heavier, warmer scents in winter; fresher in summer

No output schema declared.

No examples provided.

Install

How do I install the Perfume Picks MCP server?

Perfume Picks runs locally as an npm package, launched with npx -y perfume-picks-mcp. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

npm · perfume-picks-mcp

# add to Claude Code
claude mcp add bguillow-rgb-perfume-picks -- npx -y perfume-picks-mcp
Common questions

What is the Perfume Picks MCP server?

Perfume Picks is an MCP server listed in the public MCP registry as io.github.bguillow-rgb/perfume-picks. Search the Perfume Picks fragrance database: 10,000+ scents with notes, dupes, and wear data. This page covers its npm package (perfume-picks-mcp).

Is the Perfume Picks MCP server safe to use?

Perfume Picks scores 77 out of 100 on VerifyMCP. We recorded 1 known advisory against it as of 5 November 2026. It declares no install or post-install scripts. 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 Perfume Picks MCP server expose?

Perfume Picks exposes 8 tools: search_fragrances, get_fragrance, find_dupes, find_similar, get_recommendations, and 3 more. Their descriptions and schemas cost roughly 756 tokens of context every time the server is loaded.

Is the Perfume Picks MCP server still maintained?

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

What licence is the Perfume Picks MCP server under?

Perfume Picks declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.