INDIVIDUAL MCP TOOL

check_formula

Use this when the user has a perfume or accord formula, pasted or drafted earlier in this conversation, and wants to know whether it is IFRA compliant, how much of the finished product it may be, which line to reduce, or which EU allergens the label must declare.

perfumate.appnone authenticationAvailability not checked

LIVE ENDPOINT

https://perfumate.app/mcp

No auth detected

Connect to this endpoint to inspect the live schema for check_formula and invoke it with your own arguments.

Indexed input schema

{}

Risk classification

Inferred read-only · medium confidence · heuristic, not a guarantee.

No write-capable action terms were found; this is not proof that invocation has no side effects.

Parent server

perfumate.app

CONNECT WITH APPROVAL

Client installation

Review this server and its permissions before adding it. Secret placeholders must be set locally.

Codex

~/.codex/config.toml

[mcp_servers.perfumate]
url = "https://perfumate.app/mcp"
enabled = true

Claude Code

.mcp.json

{
  "mcpServers": {
    "perfumate": {
      "type": "http",
      "url": "https://perfumate.app/mcp"
    }
  }
}

Claude Desktop

Settings → Connectors → Add custom connector

Name: perfumate
Remote MCP URL: https://perfumate.app/mcp

Add this remote URL as a custom connector in Claude Desktop. Availability depends on the user plan and workspace policy.

Cursor

.cursor/mcp.json

{
  "mcpServers": {
    "perfumate": {
      "url": "https://perfumate.app/mcp"
    }
  }
}

Visual Studio Code

.vscode/mcp.json

Add to Visual Studio Code

{
  "servers": {
    "perfumate": {
      "type": "http",
      "url": "https://perfumate.app/mcp"
    }
  }
}

Generic MCP

Client-specific MCP configuration

{
  "name": "perfumate",
  "transport": "streamable-http",
  "url": "https://perfumate.app/mcp"
}

MCP Inspector

Run the official MCP Inspector locally and enter the indexed Streamable HTTP endpoint.

Related tools

search_materials — Use this when the user wants to find perfumery materials by scent, family, name or CAS number, for example musks, woods or citrus to put in a formula, or the catalog name of a material they typed loosely.
get_material — Use this when the user asks what one perfumery material smells like, how it is used, how strong or long-lasting it is, or how much of it IFRA allows (its Category 4 fine-fragrance limit, e.
find_starting_formula — Use this when the user wants to build, create, compose or formulate a perfume, fragrance or accord and needs a starting recipe (a rose, a citrus cologne, a clean musk, an amber), or asks what they could make with materials they list.
my_account — Use this when the user asks about their PerfuMate account or how big their bench is.
list_formulas — Use this when the user asks what formulas they have, wants to find one by name, folder or favourite, or before you read or change a formula (it returns the ids the other tools use).
get_formula — Use this when the user wants to see one of their formulas: every line with material, bottle strength, amount, relative and absolute percent, flags and notes, plus totals, concentration, cost and the note pyramid.
list_versions — Use this when the user asks about a formula's history: its version tree with notes and parents, which version is the working copy and which have batches.
create_formula — Use this when the user wants a new formula on their PerfuMate bench, empty or with lines they give (structured, pasted text or an attached file), for example after building one together in this chat.