io.github.parfica/fragrances
REMOTE · PARFICA.COM · 2 COMPONENTS · SCANNED SEP 24
Fragrance encyclopedia: note pyramids, accords, perfumers and dupes (parfica.com).
Available components
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 Security57
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation not yet verified: we couldn't confirm whether this endpoint requires it. View diagnostics → Unverified
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- HSTS not yet verified: we couldn't read the response headers to check for it. View diagnostics → Unverified
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability0
- Transport check failed: declared streamable-http, but we couldn't connect to verify it. See how to fix → View diagnostics → Fail
Schema Quality & AI Usability0
- Schema not yet verified: we couldn't read the endpoint's schema.Unverified
Stability & Change Management0
- Stability not yet verified: not enough scan history yet (needs a 30-day window).Unverified
Tool Coverage0
- Tool coverage not yet verified: we couldn't read the endpoint's tools.Unverified
Tool Safety0
- Tool safety not yet verified: we couldn't read the endpoint's tools.Unverified
Capabilities0
- Capabilities not yet verified: we couldn't read the endpoint's capabilities.Unverified
Unverified: 5 categories
Categories scored 0 because we could not verify them: authentication we do not have, an unreachable endpoint, or not enough scan history. We only credit what we can confirm.
How do I install the io.github.parfica/fragrances MCP server?
io.github.parfica/fragrances is a hosted endpoint at https://parfica.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 · parfica.com
claude mcp add --transport http parfica-fragrances 'https://parfica.com/mcp'
{
"mcpServers": {
"parfica-fragrances": {
"url": "https://parfica.com/mcp"
}
}
} {
"servers": {
"parfica-fragrances": {
"type": "http",
"url": "https://parfica.com/mcp"
}
}
} [mcp_servers.parfica-fragrances] url = "https://parfica.com/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"parfica-fragrances": {
"type": "remote",
"url": "https://parfica.com/mcp",
"enabled": true
}
}
} openclaw mcp add parfica-fragrances --url 'https://parfica.com/mcp' --transport streamable-http
mcp_servers:
parfica-fragrances:
url: "https://parfica.com/mcp" {
"McpServers": {
"parfica-fragrances": {
"Transport": "http",
"Url": "https://parfica.com/mcp"
}
}
} assistant mcp add parfica-fragrances -t streamable-http -u 'https://parfica.com/mcp'
{
"mcpServers": {
"parfica-fragrances": {
"type": "http",
"url": "https://parfica.com/mcp"
}
}
} The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.
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.
- 24 Sept 26 0
- Endpoint reachability: reachable → unreachable ▼ security
- Tool safety: pass → unverified ▼ security
- HSTS header: pass → unverified ▼ security
- Stability: pass → unverified ▼ security
- Transport: pass → fail ▼ security
- Authorization: Authorisation not yet verified: we couldn't confirm whether this endpoint requires it. security
- Capabilities: fail → unverified ▼ functional
- Tool coverage: 100 → unverified ▼ functional
- 23 Sept 26 +55
- Stability: unverified → pass ▲ security
- Injection markers: unverified → pass ▲ security
- Transport: fail → pass ▲ security
- Authorization: Authorisation not fully verified: no authorisation is required to call this server, and 3 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe. security
- MCP protocol: unverified → fail ▼ functional
- Endpoint reachability: not serving MCP → reachable ▲ functional
- Tool coverage: unverified → 100 ▲ functional
- 22 Sept 26 −55
- Endpoint reachability: reachable → not serving MCP ▼ security
- Stability: pass → unverified ▼ security
- Tool safety: pass → unverified ▼ security
- Transport: pass → fail ▼ security
- Authorization: Authorisation not fully verified: no authorisation is required to connect, but we couldn't read the tool list to see what that exposes. security
- Capabilities: fail → unverified ▼ functional
- Tool coverage: 100 → unverified ▼ functional
- 15 Sept 26 +55
- Stability: unverified → pass ▲ security
- Injection markers: unverified → pass ▲ security
- Transport: fail → pass ▲ security
- Authorization: Authorisation not fully verified: no authorisation is required to call this server, and 3 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe. security
- MCP protocol: unverified → fail ▼ functional
- Endpoint reachability: not serving MCP → reachable ▲ functional
- Tool coverage: unverified → 100 ▲ functional
- 13 Sept 26 −55
- Endpoint reachability: reachable → not serving MCP ▼ security
- Tool safety: pass → unverified ▼ security
- Stability: pass → unverified ▼ security
- Transport: pass → fail ▼ security
- Authorization: Authorisation not fully verified: no authorisation is required to connect, but we couldn't read the tool list to see what that exposes. security
- Tool coverage: 100 → unverified ▼ functional
- Capabilities: fail → unverified ▼ functional
- 12 Sept 26 +55
- Stability: unverified → pass ▲ security
- Injection markers: unverified → pass ▲ security
- Transport: fail → pass ▲ security
- Authorization: Authorisation not fully verified: no authorisation is required to call this server, and 3 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe. security
- MCP protocol: unverified → fail ▼ functional
- Endpoint reachability: not serving MCP → reachable ▲ functional
- Tool coverage: unverified → 100 ▲ functional
- 11 Sept 26 −55
- Endpoint reachability: reachable → not serving MCP ▼ security
- Tool safety: pass → unverified ▼ security
- Stability: pass → unverified ▼ security
- Transport: pass → fail ▼ security
- Authorization: Authorisation not fully verified: no authorisation is required to connect, but we couldn't read the tool list to see what that exposes. security
- Capabilities: fail → unverified ▼ functional
- Tool coverage: 100 → unverified ▼ functional
- First check of Schema quality: unverified functional
- 4 Sept 26 0
- Stability: 0.97 → pass security
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 24 Sept 2026 · Probed https://parfica.com/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=parfica.com | CN=WE1,O=Google Trust Services,C=US | 8 Sept 2026 | 7 Dec 2026 | ECDSA 256 | ECDSA-SHA256 | d382adfeb6b3e0d91337823f9e2ef1d5 |
| SANs: parfica.com, *.parfica.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 parfica.com. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| com. | present | 19718 | 13 | Verified |
| parfica.com. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication Inconclusive
We could not reach the endpoint well enough to judge its authorisation posture.
| Result | Inconclusive |
|---|
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://parfica.com/mcp | Unreachable | ||
| http (plaintext) | http://parfica.com/mcp | HTTPS enforced | 301 | https://parfica.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 →
find_dupes ~64
Find fragrances that smell similar ("dupes") to a given one, by distinctive-note overlap. Returns matches with similarity ranking.
| Name | Type | Req | Description |
|---|---|---|---|
| slug | string | yes | Fragrance slug, e.g. "maison-francis-kurkdjian-baccarat-rouge-540" |
No output schema declared.
No examples provided.
fragrance_info ~66
Full profile of a fragrance on parfica.com by its slug: brand, year, gender, concentration, family, note pyramid, accords, perfumers, community rating.
| Name | Type | Req | Description |
|---|---|---|---|
| slug | string | yes | Fragrance slug from search_fragrance, e.g. "creed-aventus" |
No output schema declared.
No examples provided.
search_fragrance ~67
Search the parfica.com fragrance encyclopedia by name (Latin or Cyrillic), brand, note or perfumer. Returns matching fragrances, brands, notes and perfumers with links.
| Name | Type | Req | Description |
|---|---|---|---|
| query | string | yes | Search query, e.g. "Aventus" or "Авентус" |
No output schema declared.
No examples provided.
What is the io.github.parfica/fragrances MCP server?
io.github.parfica/fragrances is an MCP server listed in the public MCP registry as io.github.parfica/fragrances. Fragrance encyclopedia: note pyramids, accords, perfumers and dupes (parfica.com). This page covers its hosted endpoint (https://parfica.com/mcp).
Is the io.github.parfica/fragrances MCP server safe to use?
io.github.parfica/fragrances scores 80 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 io.github.parfica/fragrances MCP server expose?
io.github.parfica/fragrances exposes 3 tools: search_fragrance, fragrance_info, find_dupes. Their descriptions and schemas cost roughly 197 tokens of context every time the server is loaded.
Does the io.github.parfica/fragrances MCP server require authentication?
Its publisher declares no required credentials for io.github.parfica/fragrances. We have not been able to confirm that against the live endpoint, and a server can require authorisation without declaring it here.
Is the io.github.parfica/fragrances MCP server still maintained?
io.github.parfica/fragrances is still listed in the MCP registry, though our most recent checks did not reach this channel. We last reached this channel on 23 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.