pro.makeup
REMOTE · PRO.MAKEUP · SCANNED AUG 3
Search 214K+ certified makeup pros worldwide: artists, salons, schools, shops, brands.
Available components
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 →
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 call this server, and 7 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe. See how to fix → 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 Usability82
- 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 1140 tokens (~142/item across 8 items; 8 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management27
- Stability observed for 8 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage94
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 83% of tool parameters carry a description.Partial
Capabilities20
- Spec-recency check failed: implements MCP spec 2025-11-05; the latest is 2026-07-28. See how to fix → Fail
Add this component to your MCP client. Where a client-specific snippet is available, pick your client below and copy it straight into your config; otherwise use the connection detail shown.
remote · pro.makeup
claude mcp add --transport http makeup-pro-mcp https://pro.makeup/api/mcp
[mcp_servers.makeup-pro-mcp] url = "https://pro.makeup/api/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"makeup-pro-mcp": {
"type": "remote",
"url": "https://pro.makeup/api/mcp",
"enabled": true
}
}
} openclaw mcp add makeup-pro-mcp --url https://pro.makeup/api/mcp --transport streamable-http
mcp_servers:
makeup-pro-mcp:
url: "https://pro.makeup/api/mcp" {
"mcpServers": {
"makeup-pro-mcp": {
"type": "http",
"url": "https://pro.makeup/api/mcp"
}
}
} The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.
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.
- 3 Aug 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 23 to 27. That category is still filling its 30-day observation window: 7 days of observed history at the previous scan, 8 at this one. The score rises as the window fills, whether or not the server changes.
- 31 Jul 26 +1
- 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 +1
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 28 Jul 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 3 to 7. That category is still filling its 30-day observation window: 1 days of observed history at the previous scan, 2 at this one. The score rises as the window fills, whether or not the server changes.
- 27 Jul 26 +1
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 26 Jul 26 61
First indexed and scored.
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 3 Aug 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 | 16 Jun 2026 | 14 Sept 2026 | ECDSA 256 | ECDSA-SHA256 | 5b2030c755b9970d13f2562553882325 |
| 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 |
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 |
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.
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.