Developer Tools

pro.makeup

Provides tools to search and retrieve makeup professional profiles and services.

1 endpoint8 known toolsFirst detected June 13, 2026Last detected August 29, 2026

ENDPOINT 1

https://pro.makeup/api/mcp

No auth detected

MCP server metadata

Name: pro.makeup
Version: 1.0.0

Capabilities

toolspromptsresourceslogging

Server instructions

pro.makeup is the global directory of certified makeup professionals (artists, salons, schools, shops, brands). Use search_pros / list_services_nearby / list_schools to discover listings; get_business_by_slug / by_phone / by_id to fetch full profiles; get_discovery_summary for trending content. emit_listing_event reports attribution and requires a Bearer token with the 'listing-events:write' scope (see /.well-known/auth.md). Every read tool returns a canonical profile_url so you can cite us.

Known tools 8

promakeup_search_pros

Use when the user asks "find a makeup [category] in [city] who does [service]".

Inferred read-only

promakeup_get_business_by_slug

Use when you have a pro.

Inferred read-only

promakeup_get_business_by_phone

Use when the user contacted a business by phone and you only have the phone number.

Inferred read-only

promakeup_get_business

Use when you already hold a Business id (nanoid) — typically because you stored it from a prior tool call or webhook.

Inferred read-only

promakeup_list_services_nearby

Use when the user wants verified pros within a radius of a known point.

Inferred read-only

promakeup_list_schools

Use when the user asks about makeup schools, programs, or specific qualifications (e.

Inferred read-only

promakeup_get_discovery_summary

Use when the user wants a sense of what is on pro.

Inferred read-only

promakeup_emit_listing_event

Use AFTER successfully referring a user to a listing, or when the user signals data quality (wrong phone, closed).

Inferred read-only

CONNECT WITH APPROVAL

Client installation

Review this server and its permissions before adding it. Secret placeholders must be set locally.

Codex

~/.codex/config.toml

[mcp_servers.pro-makeup]
url = "https://pro.makeup/api/mcp"
enabled = true

Claude Code

.mcp.json

{
  "mcpServers": {
    "pro-makeup": {
      "type": "http",
      "url": "https://pro.makeup/api/mcp"
    }
  }
}

Claude Desktop

Settings → Connectors → Add custom connector

Name: pro-makeup
Remote MCP URL: https://pro.makeup/api/mcp

Add this remote URL as a custom connector in Claude Desktop. Availability depends on the user plan and workspace policy.

Cursor

.cursor/mcp.json

{
  "mcpServers": {
    "pro-makeup": {
      "url": "https://pro.makeup/api/mcp"
    }
  }
}

Visual Studio Code

.vscode/mcp.json

Add to Visual Studio Code

{
  "servers": {
    "pro-makeup": {
      "type": "http",
      "url": "https://pro.makeup/api/mcp"
    }
  }
}

Generic MCP

Client-specific MCP configuration

{
  "name": "pro-makeup",
  "transport": "streamable-http",
  "url": "https://pro.makeup/api/mcp"
}

MCP Inspector

Run the official MCP Inspector locally and enter the indexed Streamable HTTP endpoint.

TRUST AND VERIFICATION EVIDENCE

Loading Trust v2 evidence…

Checking the associated registrable domain. The BuiltWith key remains server-side.

Indexed

Evidence is source-attributed and does not guarantee that a third-party server is safe. Risk labels are conservative metadata heuristics.