Remote MCP · Endpoint

pro.makeup MCP server

No. pro.makeup answered an MCP handshake 1 hour ago.

UpLast checked 1 hour ago

Server URL

https://pro.makeup/api/mcp

The last check completed an MCP handshake.

Registry name
makeup.pro/mcp
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
285 ms
Tools exposed
8 tools
Uptime, last 30 days
100% from 17 checks
Described by its publisher as
Search 214K+ certified makeup pros worldwide: artists, salons, schools, shops, brands.
Listing
From the official MCP registry (active).
Recent checks of pro.makeup
CheckedResultHandshake
1 hour agoHandshake completed285 ms
2 days agoHandshake completed803 ms
4 days agoHandshake completed857 ms
5 days agoHandshake completed429 ms
7 days agoHandshake completed840 ms
8 days agoHandshake completed328 ms
9 days agoHandshake completed524 ms
12 days agoHandshake completed279 ms
13 days agoHandshake completed818 ms
15 days agoHandshake completed818 ms
17 days agoHandshake completed290 ms
18 days agoHandshake completed282 ms
19 days agoHandshake completed784 ms
20 days agoHandshake completed795 ms
21 days agoHandshake completed307 ms
21 days agoHandshake completed315 ms
23 days agoHandshake completed308 ms

The last 17 checks. Full history is kept for 30 days; the all-time counter stands at 17 responding of 17.

How to read this

  • ·Handshake latency is one measurement from one probe, from our infrastructure. It is a smoke signal about the endpoint, not a benchmark of your own connection to it.
  • ·An authentication challenge counts as responding. A hosted server that refuses an anonymous prober is behaving correctly.
  • ·A tool count of “behind credentials” means the handshake worked but listing tools needed a token we do not hold.
  • ·Uptime covers the last 30 days of our own checks, at most one an hour, and says how many checks it is drawn from.

Listing data comes from the official MCP registry. Glide is not affiliated with pro.makeup and makes no claim about it beyond what these checks measured.