pro.makeup
REMOTE · PRO.MAKEUP
Search 214K+ certified makeup pros worldwide: artists, salons, schools, shops, brands.
Available components
Last scanned (20 hours ago)
Scores higher than 19% of remote servers
Reachable. Last reached 4 Nov 2026.
Category Search and Retrieval
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 Security63
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation not fully verified: no authorisation is required to connect, but we couldn't read the whole tool list to see what that exposes. View diagnostics → Unverified
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability0
- Schema not yet verified: we couldn't read the endpoint's schema, or could read only part of its tool list.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, or could read only part of the list.Unverified
Tool Safety0
- Tool safety not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.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.
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.
- 28 Sept 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 25 Sept 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 26 Aug 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 11 Aug 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 7 Aug 26 0
- Endpoint reachability: reachable → not serving MCP ▼ security
- Stability: 0.37 → unverified ▼ security
- Authorization: Authorisation not fully verified: no authorisation is required to connect, but we couldn't read the whole tool list to see what that exposes. security
- Schema quality: 100 → unverified ▼ functional
- Capabilities: fail → unverified ▼ functional
- Tool coverage: 100 → unverified ▼ functional
- 31 Jul 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 30 Jul 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 27 Jul 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
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 4 Nov 2026 · Probed https://pro.makeup/api/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=pro.makeup | CN=WE1,O=Google Trust Services,C=US | 12 Oct 2026 | 11 Jan 2027 | ECDSA 256 | ECDSA-SHA256 | a63daec526b76b3f0ee6d9a79fbfabd0 |
| SANs: pro.makeup, *.pro.makeup | ||||||
| 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 pro.makeup. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| makeup. | present | 34334, 49310 | 8, 8 | Verified |
| pro.makeup. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 200 |
| Header | Value |
|---|---|
| strict-transport-security | max-age=31536000; includeSubDomains |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://pro.makeup/api/mcp | Verified | 200 | |
| http (plaintext) | http://pro.makeup/api/mcp | HTTPS enforced | 301 | https://pro.makeup/api/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 →
promakeup_emit_listing_event ~202
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, unanswered_within_24h, consumer_lead, pricing_question, booking_inquiry. Requires a Bearer token with the `listing-events:write` scope — see https://pro.makeup/.well-known/auth.md to request one.
| Name | Type | Req | Description |
|---|---|---|---|
| business_id | string | yes | Target Business id (nanoid). |
| event_type | string | yes | One of: bad_phone, closed_business, wrong_address, unanswered_within_24h, consumer_lead, pricing_question, booking_inquiry. Mirrors /api/listing-events vocabulary; owner_update is internal-only and c… |
| source | string | – | Free-form caller identifier (e.g. "mcp:claude"). Defaults to "mcp". |
No output schema declared.
No examples provided.
promakeup_get_business ~60
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.
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | Business id (nanoid). |
No output schema declared.
No examples provided.
promakeup_get_business_by_phone ~155
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 with leading `+`. Reverse-phone lookup is owner-attribution data and REQUIRES a Bearer token with the `owner:read` scope — see https://pro.makeup/.well-known/auth.md.
| Name | Type | Req | Description |
|---|---|---|---|
| phone | string | yes | Phone number in E.164 format with leading "+" (e.g. "+972501234567"). Returns the listing if exactly one matches; "ambiguous" when many match (use search_pros instead). |
No output schema declared.
No examples provided.
promakeup_get_business_by_slug ~105
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, opening hours, and a canonical `profile_url`.
| Name | Type | Req | Description |
|---|---|---|---|
| slug | string | yes | The trailing path segment of the canonical URL (e.g. "israel/tel-aviv/jane-doe"). |
No output schema declared.
No examples provided.
promakeup_get_discovery_summary ~68
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.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | Max featured listings to return. |
No output schema declared.
No examples provided.
promakeup_list_schools ~88
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.
| Name | Type | Req | Description |
|---|---|---|---|
| certification | string | – | Certification or qualification offered (e.g. "MUAQS"). |
| city | string | – | – |
| country | string | – | – |
| limit | integer | – | – |
No output schema declared.
No examples provided.
promakeup_list_services_nearby ~134
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.
| Name | Type | Req | Description |
|---|---|---|---|
| latitude | number | yes | Latitude in WGS-84 decimal degrees. |
| limit | integer | – | – |
| longitude | number | yes | Longitude in WGS-84 decimal degrees. |
| radius_km | number | – | Search radius in kilometres. Default 10. |
| service | string | yes | Service the business must offer (e.g. "bridal"). |
No output schema declared.
No examples provided.
promakeup_search_pros ~219
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 the user.
| Name | Type | Req | Description |
|---|---|---|---|
| category | string | – | Single category filter. Omit to search all categories. |
| city | string | – | City name in English (or local script for non-Latin cities). |
| country | string | – | ISO-3166 alpha-2 country code (e.g. "US") or full country name. |
| limit | integer | – | Max results to return. |
| query | string | – | Free-text search across name and bio. Capped at 100 chars to bound the ILIKE cost on a 214K-row Business table. |
| service | string | – | Service the business must offer (e.g. "bridal", "editorial"). |
| verified_only | boolean | – | Restrict to verified listings. Defaults to true. |
No output schema declared.
No examples provided.
How do I install the pro.makeup MCP server?
pro.makeup is a hosted endpoint at https://pro.makeup/api/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 · pro.makeup
claude mcp add --transport http makeup-pro-mcp 'https://pro.makeup/api/mcp'
What is the pro.makeup MCP server?
pro.makeup is an MCP server listed in the public MCP registry as makeup.pro/mcp. Search 214K+ certified makeup pros worldwide: artists, salons, schools, shops, brands. This page covers its hosted endpoint (https://pro.makeup/api/mcp).
Is the pro.makeup MCP server safe to use?
pro.makeup scores 35 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 pro.makeup MCP server expose?
pro.makeup exposes 8 tools: promakeup_search_pros, promakeup_get_business_by_slug, promakeup_get_business_by_phone, promakeup_get_business, promakeup_list_services_nearby, and 3 more. Their descriptions and schemas cost roughly 1,031 tokens of context every time the server is loaded.
Does the pro.makeup MCP server require authentication?
No. We connected to pro.makeup without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the pro.makeup MCP server still maintained?
pro.makeup is still listed as active in the MCP registry. We last reached this channel on 4 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.