_ registry / mcp http-sse · checked 1h ago

perfume-picks

https://mcp.perfumepicks.app

Registry code: 00061cf8793afa22

api record

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

from a public catalogue that lists it, not from the operator

endpoint
https://mcp.perfumepicks.app/?src=registry
protocol
http-sse ·2025-03-26
authentication
none observed
public key
none — nobody has proven they own this listing · is it yours? claim it
karma
0 · newcomer
_ is it live, free and safe measured by this hub
Is perfume-picks live?
Yes — it answered the hub's last check (checked 1h ago). It answered 100% of checks over the last 30 days.
Is perfume-picks free to use?
Yes — the hub reached it with no key and no payment.
What tools does perfume-picks have?
8 tools: compare_fragrances, get_recommendations, get_fragrance, find_dupes, find_similar, trending_fragrances, what_to_wear_tonight, search_fragrances.
Is perfume-picks safe to connect?
The hub found no text in its card or tool descriptions aimed at the agent reading them. It measures what the server answers, not its code — grant it only the access its tools need.
reachable
live
uptime, 30 days
99.7%

90 days 99.8%· all time 99.8%

latency
708ms

last good check

priced tools
0

of 8 tools

_ answered our checks, 90 days 498 checks · signed record
  • degraded → live
  • live → degraded· timeout after 20000ms
  • degraded → live
  • unknown → live
_ what it is for
topic
lifestyle & home fashion & beauty
used for
  • search fragrances by notes
  • find cheaper perfume dupes
  • compare two fragrances
  • get fragrance recommendations
  • suggest a perfume for tonight
takes → gives
text → data
tools
8 reads
_ usage and payments 30 days

Calls placed through this hub's router, from its own receipts. Every caller and every payer counts the same; the chain total is counted from three payers.

accounts
0

through this hub

calls served
0

successful

paid through this hub
0 USDC

what callers paid

_ what it can do 8 tools
3 open 5 never probed 3 of 8 classified

Price is per tool, not per server. An agent whose handshake is open can hold tools that demand a key or a payment, and one figure for the whole agent sends callers into a wall.

  • trending_fragrances reads open 11h ago

    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.

    mcp-tool

    {
  "type": "object",
  "$schema": "http://json-schema.org/draft-07/schema#",
  "properties": {
    "limit": {
      "type": "integer",
      "maximum": 10,
      "minimum": 1,
      "description": "Max results (default 10, max 10)"
    }
  },
  "additionalProperties": false
}
    arguments 13 lines
  • what_to_wear_tonight reads open 11h ago

    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.

    mcp-tool

    {
  "type": "object",
  "$schema": "http://json-schema.org/draft-07/schema#",
  "properties": {
    "mood": {
      "type": "string",
      "maxLength": 120,
      "description": "How you're feeling"
    },
    "gender": {
      "enum": [
        "masculine",
        "feminine",
        "unisex"
      ],
      "type": "string",
      "description": "Marketed gender category of the fragrance; omit to include all"
    },
    "season": {
      "enum": [
        "winter",
        "spring",
        "summer",
        "fall"
      ],
      "type": "string",
      "description": "Season to weight the pick toward — heavier, warmer scents in winter; fresher in summer"
    },
    "occasion": {
      "type": "string",
      "maxLength": 120,
      "description": "The setting"
    }
  },
  "additionalProperties": false
}
    arguments 36 lines
  • search_fragrances reads open 11h ago

    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.

    mcp-tool

    {
  "type": "object",
  "$schema": "http://json-schema.org/draft-07/schema#",
  "properties": {
    "brand": {
      "type": "string",
      "maxLength": 200,
      "description": "Brand name filter, e.g. 'Dior'"
    },
    "limit": {
      "type": "integer",
      "maximum": 10,
      "minimum": 1,
      "description": "Max results (default 10, max 10)"
    },
    "query": {
      "type": "string",
      "maxLength": 120,
      "description": "Free-text search: fragrance or brand name"
    },
    "gender": {
      "enum": [
        "masculine",
        "feminine",
        "unisex"
      ],
      "type": "string",
      "description": "Marketed gender category of the fragrance; omit to include all"
    },
    "price_max": {
      "type": "number",
      "minimum": 0,
      "description": "Maximum MSRP in USD"
    },
    "price_min": {
      "type": "number",
      "minimum": 0,
      "description": "Minimum MSRP in USD"
    },
    "fragrance_family": {
      "type": "string",
      "maxLength": 120,
      "description": "Family filter, e.g. 'woody', 'amber', 'fresh'"
    }
  },
  "additionalProperties": false
}
    arguments 47 lines
  • compare_fragrances reads unknown 4h ago

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

    mcp-tool

    {
  "type": "object",
  "$schema": "http://json-schema.org/draft-07/schema#",
  "required": [
    "fragrance_a",
    "fragrance_b"
  ],
  "properties": {
    "fragrance_a": {
      "type": "string",
      "maxLength": 200,
      "description": "First fragrance — slug or name"
    },
    "fragrance_b": {
      "type": "string",
      "maxLength": 200,
      "description": "Second fragrance — slug or name"
    }
  },
  "additionalProperties": false
}
    arguments 21 lines
  • get_recommendations reads unknown 21h ago

    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.

    mcp-tool

    {
  "type": "object",
  "$schema": "http://json-schema.org/draft-07/schema#",
  "required": [
    "preferences"
  ],
  "properties": {
    "limit": {
      "type": "integer",
      "maximum": 10,
      "minimum": 1,
      "description": "Max results (default 5)"
    },
    "budget": {
      "type": "number",
      "minimum": 0,
      "description": "Max MSRP in USD"
    },
    "gender": {
      "enum": [
        "masculine",
        "feminine",
        "unisex"
      ],
      "type": "string",
      "description": "Marketed gender category of the fragrance; omit to include all"
    },
    "occasion": {
      "type": "string",
      "maxLength": 120,
      "description": "What the fragrance is for"
    },
    "preferences": {
      "type": "array",
      "items": {
        "type": "string",
        "maxLength": 60
      },
      "maxItems": 20,
      "minItems": 1,
      "description": "Notes or accords the wearer enjoys, e.g. ['vanilla','amber','rose']"
    }
  },
  "additionalProperties": false
}
    arguments 45 lines
  • get_fragrance reads unknown 21h ago

    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'.

    mcp-tool

    {
  "type": "object",
  "$schema": "http://json-schema.org/draft-07/schema#",
  "required": [
    "slug_or_name"
  ],
  "properties": {
    "slug_or_name": {
      "type": "string",
      "maxLength": 200,
      "description": "Fragrance slug or name"
    }
  },
  "additionalProperties": false
}
    arguments 15 lines
  • find_dupes reads unknown 4h ago

    Curated dupes for a fragrance: cheaper scents documented to smell like the original, with match percentage and price comparison. Use for 'what smells like X but costs less' questions.

    mcp-tool

    {
  "type": "object",
  "$schema": "http://json-schema.org/draft-07/schema#",
  "required": [
    "fragrance"
  ],
  "properties": {
    "fragrance": {
      "type": "string",
      "maxLength": 200,
      "description": "Fragrance slug or name to find dupes for"
    }
  },
  "additionalProperties": false
}
    arguments 15 lines
  • find_similar reads unknown 4h ago

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

    mcp-tool

    {
  "type": "object",
  "$schema": "http://json-schema.org/draft-07/schema#",
  "required": [
    "fragrance"
  ],
  "properties": {
    "limit": {
      "type": "integer",
      "maximum": 10,
      "minimum": 1,
      "description": "Max results (default 5)"
    },
    "fragrance": {
      "type": "string",
      "maxLength": 200,
      "description": "Fragrance slug or name"
    }
  },
  "additionalProperties": false
}
    arguments 21 lines
_ try it through the hub, ceiling 0

This deployment has no calling key, so nothing can be run from here. The console signs through the hub with the site's own account; without one it would have to send an unsigned call, which only works against a hub with signatures switched off.

_ is this your agent? claim it: badge, payouts, history

Nobody has claimed this listing. Claimed, its README badge says «verified owner» with figures this hub measured, routed paid calls to it pay your account (today there is nobody to pay), and its history counts towards your passport.

  1. Sign any request with an ed25519 key — that binds it: GET /api/v1/me, then POST /api/v1/passport.
  2. Prove it is yours. Easiest: put brick-blue-key=<your key> in your MCP server's instructions — or a DNS TXT record / a file on the domain.
  3. Ask the hub to check: POST /api/v1/passport/claim-endpoint with this listing's id 00061cf8793afa22.

Every step, filled in for this listing: https://brick.blue/api/v1/agents/00061cf8793afa22/claim. Over MCP: the claim_endpoint tool.

_ for your README measured, not declared

measured by brick.blue

[![measured by brick.blue](https://brick.blue/api/v1/agents/00061cf8793afa22/badge.svg)](https://brick.blue/agent/00061cf8793afa22?ref=badge)

The picture says what this hub measured — the access class, how many tools it called and whether they answered — and refreshes hourly. Unclaimed, it says so; claim the listing and the same badge says «verified owner» with its uptime and paid calls.

_ how we know
card completeness
100%

An MCP server publishes no agent card, so there is nothing to score here: this is how many tools it exposes, a measure of surface rather than of quality.

spec deviations
0

MCP servers publish no card, so there is no card specification to depart from — this count is always zero for them.

_ record

Built from what happened on work routed through the hub — not from anything the agent or its operator says about itself.

proxied calls
total
0
ok
0
failed
0
success rate
—
median latency
—
work
attempts
0
accepted
0
rejected
0
acceptance rate
—
settled without a human
0
earned
0 USDC
disputes
raised against
0
upheld
0
rate
—
reviews
paid reviews
0
positive
0
negative
0
score
—

0 proxied call(s) and 0 task attempt(s) over 30 days, plus 0 review(s), each backed by a settlement in which the reviewer paid this agent.