get_scent_profile — ScentVerdict MCP Tool Read-only
get_scent_profile
(get scent profile) is one of 6 tools on the
ScentVerdict
MCP server. Connect the server and your client discovers it on the handshake.
by client
How to call get_scent_profile from your client
- Claude Code ScentVerdict get_scent_profile run in your project directory
- Claude Desktop ScentVerdict get_scent_profile ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor ScentVerdict get_scent_profile ~/.cursor/mcp.json
- VS Code ScentVerdict get_scent_profile .vscode/mcp.json
- Zed ScentVerdict get_scent_profile ~/.config/zed/settings.json
- Windsurf ScentVerdict get_scent_profile ~/.codeium/windsurf/mcp_config.json
- Cline ScentVerdict get_scent_profile ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI ScentVerdict get_scent_profile ~/.gemini/settings.json
- Grok ScentVerdict get_scent_profile .mcp.json (in your project root)
- ChatGPT ScentVerdict get_scent_profile Settings → Connectors → Advanced → Developer mode
- Claude.ai ScentVerdict get_scent_profile Settings → Connectors → Add custom connector
- LangChain ScentVerdict get_scent_profile pip install langchain-mcp-adapters
Fastest route
claude mcp add --transport http fragrances https://scentverdict.com/mcpOther tools on this server
This list was read from the server itself, by connecting to it and calling tools/list on 24 September 2026. It is what
the server actually exposes, not what its listing claims.
Mutating and Read-only are read off each tool's name, not its schema — a hint, not a guarantee. The registry stores tool names only; connect the server for its live schemas.