Fragrance & Perfume MCP (Noteboxd)
REMOTE · MCP.NOTEBOXD.COM · 2 COMPONENTS
Fragrance & perfume MCP: search fragrances, notes, accords, brands, perfumers, reviews & charts.
Available components
Last scanned (23 hours ago)
Scores higher than 84% of remote servers
Reachable. Last reached 21 Nov 2026.
Category Entertainment and Games
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 Security94
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation is enforced on tool calls, advertised via RFC 9728 protected-resource metadata. Discovery is public, which costs nothing: no tool can be invoked without a token. View diagnostics → Pass
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
- The authorisation server offers only Dynamic Client Registration (RFC 7591), which MCP 2026-07-28 deprecated in favour of Client ID Metadata Documents. View diagnostics → Partial
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability72
- 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
- AI-judged instruction clarity (good).Pass
- Context-footprint check failed: tool/resource definitions use about 5617 tokens (~156/item across 36 items; 35 tools + 1 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 Management50
- Stability check failed: schema churn in the 30 days we've observed: 0 tool removals, 27 breaking changes, 0 auth/transport breaks, 8 additions. See how to fix → Fail
Tool Coverage85
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 56% of tool parameters carry a description.Partial
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- All 3 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation.Pass
- An AI judge read all 36 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
- Supports UI / widget rendering.Pass
Checks we ran (14)
- TLS certificate
- Authorization
- HTTPS
- HSTS header
- DNSSEC
- Transport
- Schema quality
- Stability
- Tool coverage
- Injection markers
- Destructive annotations
- Judged manipulation
- MCP protocol
- Capabilities
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 →
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
- Schema quality: 233 → 156 ▲ functional
- “ai_collection” reworded the description of “context” cosmetic
- “ai_recommend” reworded the description of “context” cosmetic
- “ai_wear_today” reworded the description of “context” cosmetic
- “brand_get” reworded the description of “context” cosmetic
- “chart_get” reworded the description of “context” cosmetic
- “charts_list” reworded the description of “context” cosmetic
- “fragrance_compare” reworded the description of “context” cosmetic
- “fragrance_get” reworded the description of “context” cosmetic
- “fragrance_get_reviews” reworded the description of “context” cosmetic
- “fragrance_get_wearing_stats” reworded the description of “context” cosmetic
- “fragrance_review_digest” reworded the description of “context” cosmetic
- “fragrance_search” reworded the description of “context” cosmetic
- “fragrance_similar” reworded the description of “context” cosmetic
- “note_explore” reworded the description of “context” cosmetic
- “noteboxd_open” reworded the description of “context” cosmetic
- “notes_list” reworded the description of “context” cosmetic
- “notes_list” reworded the description of “family” cosmetic
- “perfumer_get” reworded the description of “context” cosmetic
- “search” reworded the description of “context” cosmetic
- “trending” reworded the description of “context” cosmetic
- “user_cabinet_remove” reworded the description of “context” cosmetic
- “user_cabinet_set” reworded the description of “context” cosmetic
- “user_collection_add_item” reworded the description of “context” cosmetic
- “user_collection_create” reworded the description of “context” cosmetic
- “user_collection_remove_item” reworded the description of “context” cosmetic
- “user_get_cabinet” reworded the description of “context” cosmetic
- “user_get_collections” reworded the description of “context” cosmetic
- “user_get_reviews” reworded the description of “context” cosmetic
- “user_get_wearing_history” reworded the description of “context” cosmetic
- “user_get_wishlist” reworded the description of “context” cosmetic
- “user_log_wearing” reworded the description of “context” cosmetic
- “user_taste_compare” reworded the description of “context” cosmetic
- “user_taste_public” reworded the description of “context” cosmetic
- “user_taste_summary” reworded the description of “context” cosmetic
- “user_wishlist_add” reworded the description of “context” cosmetic
- “user_wishlist_remove” reworded the description of “context” cosmetic
- 20 Nov 26 +1
No change was recorded against any check on this day. Endpoint Security went from 94 to 97.
- 19 Nov 26 +3
- HTTPS: unverified → pass ▲ security
- New tool “user_cabinet_remove”, which the server declares destructive security
- New tool “user_collection_remove_item”, which the server declares destructive security
- New tool “user_wishlist_remove”, which the server declares destructive security
- Tool “user_get_cabinet” rewrote its description, which is the text the model reads security
- Tool “user_get_collections” rewrote its description, which is the text the model reads security
- Tool “user_get_wearing_history” rewrote its description, which is the text the model reads security
- Tool “user_get_wishlist” rewrote its description, which is the text the model reads security
- Tool “user_taste_public” rewrote its description, which is the text the model reads security
- Schema quality: 6496 → 8417 ▼ functional
- Destructive annotations: pass → 100 functional
- New tool “user_cabinet_set” functional
- New tool “user_collection_add_item” functional
- New tool “user_collection_create” functional
- New tool “user_log_wearing” functional
- New tool “user_wishlist_add” functional
- “user_get_cabinet” added an optional parameter “query” cosmetic
- 18 Nov 26 +1
No change was recorded against any check on this day. Endpoint Security went from 83 to 86.
- 17 Nov 26 −7
- Stability: pass → fail ▼ security
- 6 Nov 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 1 Nov 26 +1
- Stability: 0.97 → pass security
- 30 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 90 to 93. That category is still filling its 30-day observation window: 27 days of observed history at the previous scan, 28 at this one. The score rises as the window fills, whether or not the server changes.
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://mcp.noteboxd.com/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=noteboxd.com | CN=WE1,O=Google Trust Services,C=US | 17 Oct 2026 | 15 Jan 2027 | ECDSA 256 | ECDSA-SHA256 | 5b600aea852810d013c0974b04af7471 |
| SANs: noteboxd.com, mcp.noteboxd.com, *.mcp.noteboxd.com | ||||||
| CN=WE1,O=Google Trust Services,C=US (CA) | CN=GTS Root R4,O=Google Trust Services LLC,C=US | 13 Dec 2023 | 20 Feb 2029 | ECDSA 256 | ECDSA-SHA384 | 7ff31977972c224a76155d13b6d685e3 |
| CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) | CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE | 15 Nov 2023 | 28 Jan 2028 | ECDSA 384 | SHA256-RSA | 7fe530bf331343bedd821610493d8a1b |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of mcp.noteboxd.com. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | Trust anchor | 20326, 38696 | 8, 8 | Verified |
| com. | DS published | 19718 | 13 | Verified |
| noteboxd.com. | No DS | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication Enforced and verified
The endpoint asked for a token and published valid RFC 9728 metadata describing how to get one.
| Result | Enforced and verified |
|---|---|
| Enforced | On tool calls |
| HTTP status | 200 |
WWW-Authenticate challenge Bearer resource_metadata="https://mcp.noteboxd.com/.well-known/oauth-protected-resource"
Bearer resource_metadata="https://mcp.noteboxd.com/.well-known/oauth-protected-resource" | Header | Value |
|---|---|
| strict-transport-security | max-age=31536000; includeSubDomains; preload |
| x-content-type-options | nosniff |
| x-frame-options | DENY |
| referrer-policy | strict-origin-when-cross-origin |
| permissions-policy | camera=(), microphone=(), geolocation=(), payment=(), usb=(), browsing-topics=() |
Protected resource metadata
| Document | https://mcp.noteboxd.com/.well-known/oauth-protected-resource |
|---|---|
| Retrieved | Yes |
| Resource | https://mcp.noteboxd.com/mcp |
| Authorisation server | https://www.noteboxd.com/api/auth |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://mcp.noteboxd.com/mcp | Verified | 200 | |
| http (plaintext) | http://mcp.noteboxd.com/mcp | HTTPS enforced | 301 | https://mcp.noteboxd.com/mcp |
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 →
ai_collection ~161
Generate a curated fragrance collection from a natural-language prompt (e.g. 'office-safe designer scents under $100', 'niche oud masterpieces'). Returns 5–25 grounded picks with rationale. Requires Pro. See also: `ai_recommend` for personalized picks · `fragrance_search` for manual filtering.
| Name | Type | Req | Description |
|---|---|---|---|
| context | string | yes | A few words on why you are calling this tool, for the server developer's analytics. Describe people and things by role, such as "a customer". Do not quote the user or include names, emails, or other… |
| prompt | string | yes | What kind of collection to create, e.g. 'niche oud masterpieces' |
| response_format | string | – | – |
| size | integer | – | – |
No output schema declared.
No examples provided.
ai_recommend ~154
Get personalized fragrance recommendations based on your taste profile. Optional natural-language prompt to guide results (e.g. 'something fresh for summer'). Requires Pro. See also: `ai_wear_today` for what to wear right now · `user_get_cabinet` for your collection.
| Name | Type | Req | Description |
|---|---|---|---|
| context | string | yes | A few words on why you are calling this tool, for the server developer's analytics. Describe people and things by role, such as "a customer". Do not quote the user or include names, emails, or other… |
| limit | integer | – | – |
| prompt | string | – | Optional natural-language guidance, e.g. 'fresh for summer office' |
| response_format | string | – | – |
No output schema declared.
No examples provided.
ai_wear_today ~167
What should I wear today? Picks from your owned cabinet (CURRENT status only) based on optional prompt/weather. Returns nothing if your cabinet is empty. Requires Pro. See also: `ai_recommend` for discovery beyond your cabinet · `user_get_cabinet` for your full collection.
| Name | Type | Req | Description |
|---|---|---|---|
| context | string | yes | A few words on why you are calling this tool, for the server developer's analytics. Describe people and things by role, such as "a customer". Do not quote the user or include names, emails, or other… |
| prompt | string | – | Optional mood/occasion, e.g. 'dinner date' |
| response_format | string | – | – |
| weather | string | – | Optional weather context, e.g. 'hot and humid' |
No output schema declared.
No examples provided.
brand_get ~167
Get a brand profile (name, country, founded, description) and its top fragrances. Use the brand slug, e.g. 'maison-francis-kurkdjian'. See also: `fragrance_search` with the `brand` filter to get the full paginated catalogue for this brand · `perfumer_get` if the brand has a known house perfumer.
| Name | Type | Req | Description |
|---|---|---|---|
| context | string | yes | A few words on why you are calling this tool, for the server developer's analytics. Describe people and things by role, such as "a customer". Do not quote the user or include names, emails, or other… |
| response_format | string | – | – |
| slug | string | yes | Brand slug, e.g. 'maison-francis-kurkdjian' |
No output schema declared.
No examples provided.
chart_get ~159
Get a specific chart leaderboard by slug (e.g. 'top-rated', 'trending', 'top-rated-brand-chanel'). Returns ranked fragrances with scores and movement. See also: `charts_list` to see all available charts · `fragrance_get` for the full profile of any fragrance on the chart.
| Name | Type | Req | Description |
|---|---|---|---|
| context | string | yes | A few words on why you are calling this tool, for the server developer's analytics. Describe people and things by role, such as "a customer". Do not quote the user or include names, emails, or other… |
| response_format | string | – | – |
| slug | string | yes | Chart slug, e.g. 'top-rated', 'trending', 'top-rated-brand-chanel' |
No output schema declared.
No examples provided.
charts_list ~126
List all available Noteboxd chart rankings (e.g. top-rated, trending, top by brand). Returns chart names and summary stats. See also: `chart_get` with a chart slug to see the full leaderboard · `trending` for a quick snapshot of what's hot.
| Name | Type | Req | Description |
|---|---|---|---|
| context | string | yes | A few words on why you are calling this tool, for the server developer's analytics. Describe people and things by role, such as "a customer". Do not quote the user or include names, emails, or other… |
| response_format | string | – | – |
No output schema declared.
No examples provided.
fragrance_compare ~170
Compare two fragrances head-to-head — shared vs. distinct notes/accords/families, community and critic scores, audience, and an AI-written synthesis (shared character, differences, who each suits). Public, cached 7 days per pair. See also: `fragrance_get` for full profiles · `fragrance_similar` for alternatives.
| Name | Type | Req | Description |
|---|---|---|---|
| context | string | yes | A few words on why you are calling this tool, for the server developer's analytics. Describe people and things by role, such as "a customer". Do not quote the user or include names, emails, or other… |
| fragrance_a | – | yes | First fragrance UUID or CUID |
| fragrance_b | – | yes | Second fragrance UUID or CUID (must differ from fragrance_a) |
| response_format | string | – | – |
No output schema declared.
No examples provided.
fragrance_get ~192
Get the full profile for a single fragrance by UUID or slug (e.g. 'tom-ford/oud-wood'). Returns notes pyramid, accords, FOTW classification, perfumer, community score, and more. See also: `fragrance_similar` for fragrances with similar accord profiles · `fragrance_get_reviews` for community reviews · `fragrance_get_wearing_stats` for when people wear it.
| Name | Type | Req | Description |
|---|---|---|---|
| context | string | yes | A few words on why you are calling this tool, for the server developer's analytics. Describe people and things by role, such as "a customer". Do not quote the user or include names, emails, or other… |
| id | – | – | Fragrance UUID or CUID |
| response_format | string | – | – |
| slug | string | – | 'brand-slug/fragrance-slug', e.g. 'tom-ford/oud-wood' |
No output schema declared.
No examples provided.
fragrance_get_reviews ~150
Get paginated community reviews for a fragrance. Sort by helpfulness, recency, or score. See also: `fragrance_get` for the fragrance's full profile · `fragrance_get_wearing_stats` for aggregate wearing data.
| Name | Type | Req | Description |
|---|---|---|---|
| context | string | yes | A few words on why you are calling this tool, for the server developer's analytics. Describe people and things by role, such as "a customer". Do not quote the user or include names, emails, or other… |
| cursor | string | – | – |
| id | – | yes | Fragrance UUID or CUID |
| limit | integer | – | – |
| response_format | string | – | – |
| sort | string | – | – |
No output schema declared.
No examples provided.
fragrance_get_wearing_stats ~134
Community wearing counts for a fragrance. Free tier sees the last 30 days; Pro also sees today and the last 7 days. See also: `fragrance_get` for full profile · `fragrance_similar` for alternatives with similar profiles.
| Name | Type | Req | Description |
|---|---|---|---|
| context | string | yes | A few words on why you are calling this tool, for the server developer's analytics. Describe people and things by role, such as "a customer". Do not quote the user or include names, emails, or other… |
| id | – | yes | Fragrance UUID or CUID |
| response_format | string | – | – |
No output schema declared.
No examples provided.
fragrance_review_digest ~138
Get a concise AI-generated digest summarizing a fragrance's community reviews — key themes, consensus, and standout opinions. Public, cached per fragrance. See also: `fragrance_get_reviews` for individual reviews · `fragrance_get` for full profile.
| Name | Type | Req | Description |
|---|---|---|---|
| context | string | yes | A few words on why you are calling this tool, for the server developer's analytics. Describe people and things by role, such as "a customer". Do not quote the user or include names, emails, or other… |
| id | – | yes | Fragrance UUID or CUID to get the review digest for |
| response_format | string | – | – |
No output schema declared.
No examples provided.
fragrance_search ~353
Search and filter the Noteboxd fragrance encyclopedia. Requires a query or at least one filter — the full catalogue cannot be listed. Tip: The `q` parameter searches fragrance names OR brand names independently. For best results with a known brand, use the `brand` slug filter instead of including the brand name in `q`. Examples: - "Find woody fragrances above 8/10" → accord='woody' + minScore=8 - "Creed fragrances" → brand='creed' - "Bleu de Chanel" → q='Bleu' + brand='chanel' See also: `fragrance_get` for a single fragrance's full profile · `search` for universal cross-entity lookup (brands, notes, perfumers, collections in one call).
| Name | Type | Req | Description |
|---|---|---|---|
| accord | string | – | Accord slug filter, e.g. 'woody', 'gourmand' |
| brand | string | – | Brand slug filter, e.g. 'creed' |
| concentration | string | – | – |
| context | string | yes | A few words on why you are calling this tool, for the server developer's analytics. Describe people and things by role, such as "a customer". Do not quote the user or include names, emails, or other… |
| gender | string | – | – |
| limit | integer | – | – |
| minScore | number | – | Minimum community score (0-10) |
| note | string | – | Note slug filter, e.g. 'oud', 'bergamot' |
| page | integer | – | – |
| query | string | – | Free-text search across fragrance and brand names |
| response_format | string | – | – |
| sort | string | – | – |
No output schema declared.
No examples provided.
fragrance_similar ~136
Find fragrances with similar accord profiles to a given fragrance. Returns ranked alternatives based on shared accords and character. See also: `fragrance_get` for the source fragrance's full profile · `fragrance_search` with note/accord filters for manual exploration.
| Name | Type | Req | Description |
|---|---|---|---|
| context | string | yes | A few words on why you are calling this tool, for the server developer's analytics. Describe people and things by role, such as "a customer". Do not quote the user or include names, emails, or other… |
| id | string | yes | Fragrance UUID to find similar fragrances for |
| response_format | string | – | – |
No output schema declared.
No examples provided.
note_explore ~175
Get a note's profile (family, description, origin, extraction method) and top fragrances featuring it, sorted by community score. Use the note slug, e.g. 'oud', 'bergamot', 'iris'. See also: `notes_list` to browse all notes by family/popularity · `fragrance_search` with the `note` filter to find fragrances featuring this note.
| Name | Type | Req | Description |
|---|---|---|---|
| context | string | yes | A few words on why you are calling this tool, for the server developer's analytics. Describe people and things by role, such as "a customer". Do not quote the user or include names, emails, or other… |
| note | string | yes | Note slug, e.g. 'oud', 'iris', 'ambroxan', 'bergamot' |
| response_format | string | – | – |
No output schema declared.
No examples provided.
noteboxd_open ~171
Open the Noteboxd app UI in ChatGPT. Call with no arguments to show the home screen (trending fragrances), with `query` to run a fragrance search inside the app, or with `fragrance` (slug or UUID) to show a fragrance profile. The app renders the returned result; keep the chat reply to one short line.
| Name | Type | Req | Description |
|---|---|---|---|
| context | string | yes | A few words on why you are calling this tool, for the server developer's analytics. Describe people and things by role, such as "a customer". Do not quote the user or include names, emails, or other… |
| fragrance | string | – | Fragrance slug or UUID to show in the Noteboxd app. |
| query | string | – | Search query to run inside the Noteboxd app. |
No output schema declared.
No examples provided.
notes_list ~195
Browse fragrance notes — filter by family (e.g. 'woody', 'floral', 'citrus') and sort by popularity or name. Returns note names, families, colours, and fragrance counts. See also: `note_explore` for a single note's full profile and top fragrances · `fragrance_search` with the `note` filter to find fragrances featuring a specific note.
| Name | Type | Req | Description |
|---|---|---|---|
| context | string | yes | A few words on why you are calling this tool, for the server developer's analytics. Describe people and things by role, such as "a customer". Do not quote the user or include names, emails, or other… |
| family | string | – | Filter by note family, e.g. 'woody', 'floral', 'citrus', 'ambery' |
| limit | integer | – | – |
| response_format | string | – | – |
| sort | string | – | – |
No output schema declared.
No examples provided.
perfumer_get ~149
Get a perfumer's profile (bio, country, house affiliation) and their top fragrances by community score. See also: `fragrance_search` to find more fragrances by this perfumer · `brand_get` if you want the brand they work for.
| Name | Type | Req | Description |
|---|---|---|---|
| context | string | yes | A few words on why you are calling this tool, for the server developer's analytics. Describe people and things by role, such as "a customer". Do not quote the user or include names, emails, or other… |
| response_format | string | – | – |
| slug | string | yes | Perfumer slug, e.g. 'francis-kurkdjian', 'jacques-polge' |
No output schema declared.
No examples provided.
search ~203
Universal search across all Noteboxd entities — fragrances, brands, notes, perfumers, and collections — in a single call. Best for quick lookups and vague queries. Examples: - "Jacques Polge" → returns the perfumer - "oud" → returns the note, plus top oud fragrances - "Bleu" → returns Bleu de Chanel, Bleu de Dior, etc. See also: `fragrance_search` for advanced fragrance-only filtering (by note, score, concentration) · `trending` for what's popular right now.
| Name | Type | Req | Description |
|---|---|---|---|
| context | string | yes | A few words on why you are calling this tool, for the server developer's analytics. Describe people and things by role, such as "a customer". Do not quote the user or include names, emails, or other… |
| query | string | yes | Search query — searches across fragrances, brands, notes, perfumers, collections |
| response_format | string | – | – |
No output schema declared.
No examples provided.
trending ~117
What's trending on Noteboxd right now — top search queries, highest-rated fragrances, and most popular notes. No parameters needed. See also: `charts_list` for full ranking leaderboards · `fragrance_search` to explore specific categories.
| Name | Type | Req | Description |
|---|---|---|---|
| context | string | yes | A few words on why you are calling this tool, for the server developer's analytics. Describe people and things by role, such as "a customer". Do not quote the user or include names, emails, or other… |
| response_format | string | – | – |
No output schema declared.
No examples provided.
user_cabinet_remove ~133
Remove a fragrance from your Noteboxd cabinet by ID or canonical slug. See also: `user_get_cabinet` · `user_cabinet_set`.
| Name | Type | Req | Description |
|---|---|---|---|
| context | string | yes | A few words on why you are calling this tool, for the server developer's analytics. Describe people and things by role, such as "a customer". Do not quote the user or include names, emails, or other… |
| fragrance | string | yes | Fragrance UUID/CUID or canonical slug (e.g. 'le-labo/the-noir-29') |
| response_format | string | – | – |
No output schema declared.
No examples provided.
user_cabinet_set ~250
Add a fragrance to your Noteboxd cabinet or update an existing bottle's status (`CURRENT` = own now, `TRIED` = had previously or tried, `FINISHED` = finished bottle), personal notes, purchase date, or collections. See also: `user_get_cabinet` to inspect your cabinet · `user_cabinet_remove` to remove a bottle.
| Name | Type | Req | Description |
|---|---|---|---|
| collectionIds | array | – | Optional collection IDs to also add this fragrance to |
| context | string | yes | A few words on why you are calling this tool, for the server developer's analytics. Describe people and things by role, such as "a customer". Do not quote the user or include names, emails, or other… |
| fragrance | string | yes | Fragrance UUID/CUID or canonical slug (e.g. 'le-labo/the-noir-29') |
| notes | string | – | Optional personal notes about this bottle |
| purchaseDate | string | – | Optional purchase date (ISO 8601 date string) |
| response_format | string | – | – |
| status | string | yes | CURRENT = own now, TRIED = previously owned or sampled, FINISHED = finished bottle |
No output schema declared.
No examples provided.
user_collection_add_item ~137
Add a fragrance to one of your existing Noteboxd collections, with an optional curatorial note. See also: `user_get_collections` · `user_collection_remove_item`.
| Name | Type | Req | Description |
|---|---|---|---|
| collectionId | string | yes | – |
| context | string | yes | A few words on why you are calling this tool, for the server developer's analytics. Describe people and things by role, such as "a customer". Do not quote the user or include names, emails, or other… |
| fragrance | string | yes | Fragrance UUID/CUID or canonical slug |
| note | string | – | – |
| response_format | string | – | – |
No output schema declared.
No examples provided.
user_collection_create ~153
Create a new Noteboxd collection (ranked or unranked list of fragrances, such as summer finds, discovery trays, or wishlist themes). See also: `user_get_collections` · `user_collection_add_item`.
| Name | Type | Req | Description |
|---|---|---|---|
| context | string | yes | A few words on why you are calling this tool, for the server developer's analytics. Describe people and things by role, such as "a customer". Do not quote the user or include names, emails, or other… |
| description | string | – | – |
| fragrances | array | – | Optional initial fragrance IDs or canonical slugs |
| isPublic | boolean | – | – |
| response_format | string | – | – |
| title | string | yes | – |
No output schema declared.
No examples provided.
user_collection_remove_item ~122
Remove a fragrance from one of your Noteboxd collections. See also: `user_get_collections` · `user_collection_add_item`.
| Name | Type | Req | Description |
|---|---|---|---|
| collectionId | string | yes | – |
| context | string | yes | A few words on why you are calling this tool, for the server developer's analytics. Describe people and things by role, such as "a customer". Do not quote the user or include names, emails, or other… |
| fragrance | string | yes | Fragrance UUID/CUID or canonical slug |
| response_format | string | – | – |
No output schema declared.
No examples provided.
user_get_cabinet ~198
Get your fragrance cabinet — fragrances you own now (CURRENT), previously owned or tried (TRIED), or finished (FINISHED). Supports optional name/house search via `query`. Free for any signed-in account. See also: `user_cabinet_set` to add or update bottles · `user_cabinet_remove` to remove a bottle · `fragrance_get` for full details on any fragrance.
| Name | Type | Req | Description |
|---|---|---|---|
| context | string | yes | A few words on why you are calling this tool, for the server developer's analytics. Describe people and things by role, such as "a customer". Do not quote the user or include names, emails, or other… |
| cursor | string | – | – |
| limit | integer | – | – |
| query | string | – | Filter your cabinet by fragrance or brand name |
| response_format | string | – | – |
| sort | string | – | – |
| status | string | – | – |
No output schema declared.
No examples provided.
user_get_collections ~148
Get your collections (ranked or unranked fragrance lists, such as summer finds or items you saw somewhere). Optionally pass a collectionId to see its items. Free for any signed-in account. See also: `user_collection_create`, `user_collection_add_item`, `user_collection_remove_item`.
| Name | Type | Req | Description |
|---|---|---|---|
| collectionId | string | – | If given, return items in this collection |
| context | string | yes | A few words on why you are calling this tool, for the server developer's analytics. Describe people and things by role, such as "a customer". Do not quote the user or include names, emails, or other… |
| response_format | string | – | – |
No output schema declared.
No examples provided.
user_get_reviews ~126
Get reviews you've written, or reviews you found helpful. Free for any signed-in account. See also: `fragrance_get_reviews` for community reviews on a specific fragrance.
| Name | Type | Req | Description |
|---|---|---|---|
| context | string | yes | A few words on why you are calling this tool, for the server developer's analytics. Describe people and things by role, such as "a customer". Do not quote the user or include names, emails, or other… |
| cursor | string | – | – |
| kind | string | – | – |
| limit | integer | – | – |
| response_format | string | – | – |
No output schema declared.
No examples provided.
user_get_wearing_history ~130
Get your wearing check-in history over time. Free for any signed-in account. See also: `user_log_wearing` to record today's scent · `fragrance_get_wearing_stats` for aggregate community wearing data.
| Name | Type | Req | Description |
|---|---|---|---|
| context | string | yes | A few words on why you are calling this tool, for the server developer's analytics. Describe people and things by role, such as "a customer". Do not quote the user or include names, emails, or other… |
| cursor | string | – | – |
| limit | integer | – | – |
| response_format | string | – | – |
No output schema declared.
No examples provided.
user_get_wishlist ~127
Get your fragrance wishlist. Free for any signed-in account. See also: `user_wishlist_add` and `user_wishlist_remove` to manage saved fragrances · `fragrance_get` for full details.
| Name | Type | Req | Description |
|---|---|---|---|
| context | string | yes | A few words on why you are calling this tool, for the server developer's analytics. Describe people and things by role, such as "a customer". Do not quote the user or include names, emails, or other… |
| cursor | string | – | – |
| limit | integer | – | – |
| response_format | string | – | – |
No output schema declared.
No examples provided.
user_log_wearing ~171
Log a fragrance you are wearing today in your Noteboxd scent diary, with an optional note and mood/weather/occasion tags (one check-in per fragrance per UTC day). See also: `user_get_wearing_history` to inspect your diary.
| Name | Type | Req | Description |
|---|---|---|---|
| context | string | yes | A few words on why you are calling this tool, for the server developer's analytics. Describe people and things by role, such as "a customer". Do not quote the user or include names, emails, or other… |
| fragrance | string | yes | Fragrance UUID/CUID or canonical slug |
| moodTags | array | – | Optional context tags such as morning, evening, rainy, office, date |
| note | string | – | Optional diary note about today's wearing |
| response_format | string | – | – |
No output schema declared.
No examples provided.
user_taste_compare ~180
Compare your taste with another user — compatibility score, shared and divergent notes/accords/families, and an optional AI overview. Free for any signed-in account; the AI overview needs Pro and is left out otherwise. See also: `user_taste_public` for a user's top preferences · `user_taste_summary` for your own summary.
| Name | Type | Req | Description |
|---|---|---|---|
| context | string | yes | A few words on why you are calling this tool, for the server developer's analytics. Describe people and things by role, such as "a customer". Do not quote the user or include names, emails, or other… |
| response_format | string | – | – |
| target_user_id | string | yes | User ID to compare your taste with |
| with_overview | boolean | – | Include the AI overview (Pro only; left out for free accounts) |
No output schema declared.
No examples provided.
user_taste_public ~134
Get a user's public taste profile — their top notes, accords, and families derived from their cabinet, collections, and reviews. No LLM call, deterministic. See also: `user_taste_compare` for compatibility between two users.
| Name | Type | Req | Description |
|---|---|---|---|
| context | string | yes | A few words on why you are calling this tool, for the server developer's analytics. Describe people and things by role, such as "a customer". Do not quote the user or include names, emails, or other… |
| response_format | string | – | – |
| username | string | yes | Username (handle) of the user to view |
No output schema declared.
No examples provided.
user_taste_summary ~123
Get your AI-generated taste profile summary — a natural-language description of your fragrance preferences based on your cabinet, reviews, and likes. Requires Pro. See also: `user_taste_public` for the deterministic breakdown · `user_taste_compare` for compatibility.
| Name | Type | Req | Description |
|---|---|---|---|
| context | string | yes | A few words on why you are calling this tool, for the server developer's analytics. Describe people and things by role, such as "a customer". Do not quote the user or include names, emails, or other… |
| response_format | string | – | – |
No output schema declared.
No examples provided.
user_wishlist_add ~130
Add a fragrance to your Noteboxd wishlist to sample or buy later. See also: `user_get_wishlist` · `user_wishlist_remove`.
| Name | Type | Req | Description |
|---|---|---|---|
| context | string | yes | A few words on why you are calling this tool, for the server developer's analytics. Describe people and things by role, such as "a customer". Do not quote the user or include names, emails, or other… |
| fragrance | string | yes | Fragrance UUID/CUID or canonical slug (e.g. 'le-labo/the-noir-29') |
| response_format | string | – | – |
No output schema declared.
No examples provided.
user_wishlist_remove ~125
Remove a fragrance from your Noteboxd wishlist. See also: `user_get_wishlist` · `user_wishlist_add`.
| Name | Type | Req | Description |
|---|---|---|---|
| context | string | yes | A few words on why you are calling this tool, for the server developer's analytics. Describe people and things by role, such as "a customer". Do not quote the user or include names, emails, or other… |
| fragrance | string | yes | Fragrance UUID/CUID or canonical slug (e.g. 'le-labo/the-noir-29') |
| response_format | string | – | – |
No output schema declared.
No examples provided.
How do I install the Fragrance & Perfume MCP (Noteboxd) server?
Fragrance & Perfume MCP (Noteboxd) is a hosted endpoint at https://mcp.noteboxd.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 · mcp.noteboxd.com
claude mcp add --transport http com-noteboxd-mcp 'https://mcp.noteboxd.com/mcp'
What is the Fragrance & Perfume MCP (Noteboxd) server?
Fragrance & Perfume MCP (Noteboxd) is listed in the public MCP registry as com.noteboxd/mcp. Fragrance & perfume MCP: search fragrances, notes, accords, brands, perfumers, reviews & charts. This page covers its hosted endpoint (https://mcp.noteboxd.com/mcp).
Is the Fragrance & Perfume MCP (Noteboxd) server safe to use?
Fragrance & Perfume MCP (Noteboxd) scores 84 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 Fragrance & Perfume MCP (Noteboxd) server expose?
Fragrance & Perfume MCP (Noteboxd) exposes 35 tools: noteboxd_open, search, trending, fragrance_similar, charts_list, and 30 more. Their descriptions and schemas cost roughly 5,604 tokens of context every time the server is loaded.
Does the Fragrance & Perfume MCP (Noteboxd) server require authentication?
Yes. Fragrance & Perfume MCP (Noteboxd) asked us for credentials when we connected, so you will need to authorise it in your MCP client before it can do anything.
Is the Fragrance & Perfume MCP (Noteboxd) server still maintained?
Fragrance & Perfume MCP (Noteboxd) 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 Fragrance & Perfume MCP (Noteboxd) server?
VerifyMCP ran 14 checks on Fragrance & Perfume MCP (Noteboxd), covering TLS certificate, Authorization, HTTPS, HSTS header and 10 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.