PRO Makeup MCP server

• Registry namemakeup.pro/mcpverified in the MCP registry

The registry name sits under pro.makeup. The registry only lets a publisher use that namespace after proving control of the domain through DNS or HTTP.

• Stateanswerschecked 2026-10-26
• Tools8
• Server calls itselfpro.makeup
• Server version1.0.0
• Protocol version2025-06-18

On 2026-10-26 the server answered initialize and tools/list without a sign-in. First answer in 223 ms.

• Its tools do find makeup artists by location and specialty, but not join the directory with verified certification levels.
• Checked on 1 of the 7 days it takes to judge reliability.

Said by rules from the measurements above. The likely first call is a model's pick from the tool list; read its description before relying on it.

• INITE MCP scoreafter a weeka score needs 7 daily checks: 1 so far
• What an agent can do with it1 of 2 use cases
• Answeredmeasuring1 of the 7 daily checks it takes to print a share
• Median first answer629 ms
• Space in an agent's context≈ 1,544 tokensthe definitions of all its tools (8), which an agent carries on every turn
• Tool definitionsA · 96 of 100
• Typed results0 of 8 toolsdeclared outputSchema: results come typed, read once

• Parameters without a description: in 2 of 8

A program checks the server once a day: initialize and tools/list, no model. Tokens are the definitions' length at about four characters a token. The grade averages six checks of every tool's name, description, schema and annotations; it says how well the tools are described, not whether they work. The score weighs what was measured and nothing else: answering (25%), doing the product's job (25%), definitions (20%), context (10%), use (10%) and how readily a client connects (10%). A part that was not measured is left out, and a hidden instruction caps the score at 40. The state of vendors' MCP servers: method and numbers →

• promakeup_search_pros

  Use when the user asks "find a makeup [category] in [city] who does [service]". Returns ranked, verified-by-default listings. Example: "Find a bridal makeup artist in Tel Aviv". Each result includes a `profile_url` you can cite back to…

• promakeup_get_business_by_slug

  Use when you have a pro.makeup URL or slug and want the full structured profile. The slug is the trailing path segment of `https://pro.makeup/{category}/{country}/{city}/{slug}`. Returns name, location, services, photos, verification…

• promakeup_get_business_by_phone

  Use when the user contacted a business by phone and you only have the phone number. Returns the listing when exactly one matches; signals `ambiguous: true` when multiple do (call promakeup_search_pros to disambiguate). Phone must be E.164…

• promakeup_get_business

  Use when you already hold a Business id (nanoid) — typically because you stored it from a prior tool call or webhook. Returns the same full profile shape as get_business_by_slug.

• promakeup_list_services_nearby

  Use when the user wants verified pros within a radius of a known point. Example: "Makeup artists doing bridal within 10km of these coordinates". Inputs are WGS-84 lat/lon; radius defaults to 10km.

• promakeup_list_schools

  Use when the user asks about makeup schools, programs, or specific qualifications (e.g. MUAQS). Returns school listings filterable by country, city, and certification offered.

• promakeup_get_discovery_summary

  Use when the user wants a sense of what is on pro.makeup right now — totals plus a sample of recently added listings with avatars. Cheap; safe to call to "warm up" before a more specific search.

• promakeup_emit_listing_event

  Use AFTER successfully referring a user to a listing, or when the user signals data quality (wrong phone, closed). Mirrors /api/listing-events vocabulary. Allowed event_types: bad_phone, closed_business, wrong_address…