Over MCP
The same face measurement the rest of the app makes, routed through the Model Context Protocol against YouCam’s servers instead of their REST API — with the transport shown for every step, and an automatic fall back to REST when a server does not answer.
Three servers, one product
A project that only does try-on talks to one server. A project that only analyses skin talks to another. This product uses all three — but not all three in the same request, so each one says where it runs and the trace below says which were actually reached.
beauty50 tools
measures the face — the colour the user cannot see
Runs in: this run.
creators37 tools
normalises the light, without which a measurement lies about itself
Runs in: this run.
fashion19 tools
renders the garment onto their body
Runs in: the try-on screen, not here.
All three servers are reached; one does production work. fashion renders every try-on in the app, MCP first with REST underneath. beauty and creators are exercised in this run and nowhere else, and that is a consequence of the rule above rather than an oversight: the tools we use from them — face colour, phototype, photo lighting, background removal, and the makeup render whose redness is measured before and after — all feed a measurement, and measurements go over REST. We would rather say that plainly than measure one face through two paths that disagree.
The same measurement the colour portrait makes, routed through MCP instead. Nothing from this run is saved.