Remote MCP · Endpoint

BrickYourFace: photo to brick mosaic MCP server

No. BrickYourFace: photo to brick mosaic answered an MCP handshake 4 hours ago.

UpLast checked 4 hours ago

Server URL

https://brickyourface.com/api/mcp

The last check completed an MCP handshake.

Registry name
com.brickyourface/brick-mosaic
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
639 ms
Tools exposed
2 tools
Uptime, last 30 days
100% from 12 checks
Described by its publisher as
Turn a photo into a LEGO-compatible brick mosaic kit: watermarked preview, price and buy link.
Listing
From the official MCP registry (active).
Recent checks of BrickYourFace: photo to brick mosaic
CheckedResultHandshake
4 hours agoHandshake completed639 ms
3 days agoHandshake completed1.29 s
12 days agoHandshake completed736 ms
13 days agoHandshake completed316 ms
14 days agoHandshake completed549 ms
15 days agoHandshake completed600 ms
16 days agoHandshake completed397 ms
17 days agoHandshake completed541 ms
18 days agoHandshake completed222 ms
20 days agoHandshake completed350 ms
22 days agoHandshake completed416 ms
25 days agoHandshake completed262 ms

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

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 BrickYourFace: photo to brick mosaic and makes no claim about it beyond what these checks measured.