BrickYourFace: photo to brick mosaic
REMOTE · BRICKYOURFACE.COM
Turn a photo into a LEGO-compatible brick mosaic kit: watermarked preview, price and buy link.
Available components
Last scanned (5 hours ago)
Scores higher than 76% of remote servers
Reachable. Last reached 5 Nov 2026.
Category Design and Media
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 → Why this is hard to score →
Endpoint Security80
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- No authorisation is required to call this server. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one. See how to fix → View diagnostics → Partial
- 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 Usability70
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 456 tokens (~228/item across 2 items; 2 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 Management40
- Stability observed for 12 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 2 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 3 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
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.
- 4 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 33 to 37. That category is still filling its 30-day observation window: 10 days of observed history at the previous scan, 11 at this one. The score rises as the window fills, whether or not the server changes.
- 2 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 27 to 30. That category is still filling its 30-day observation window: 8 days of observed history at the previous scan, 9 at this one. The score rises as the window fills, whether or not the server changes.
- 31 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 20 to 23. That category is still filling its 30-day observation window: 6 days of observed history at the previous scan, 7 at this one. The score rises as the window fills, whether or not the server changes.
- 29 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 13 to 17. That category is still filling its 30-day observation window: 4 days of observed history at the previous scan, 5 at this one. The score rises as the window fills, whether or not the server changes.
- 26 Oct 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.
- 25 Oct 26 0
- Stability: unverified → 0.03 ▲ functional
- 24 Oct 26 73
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 5 Nov 2026 · Probed https://brickyourface.com/api/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=brickyourface.com | CN=YE1,O=Let's Encrypt,C=US | 25 Oct 2026 | 23 Jan 2027 | ECDSA 256 | ECDSA-SHA384 | 6aa2ab2846c9f0b4f859c7adaa93db871f0 |
| SANs: brickyourface.com, www.brickyourface.com | ||||||
| CN=YE1,O=Let's Encrypt,C=US (CA) | CN=Root YE,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | ECDSA 384 | ECDSA-SHA384 | 5ddd70dd31f801c85c186a7a04b80afe |
| CN=Root YE,O=ISRG,C=US (CA) | CN=ISRG Root X2,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | ECDSA-SHA384 | 872165fc34b6e5fba8add5b3705fb53a |
| CN=ISRG Root X2,O=Internet Security Research Group,C=US (CA) | CN=ISRG Root X1,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | SHA256-RSA | 6c8f1dc727c7117f7baf853ac980f9cd |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of brickyourface.com. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| com. | present | 19718 | 13 | Verified |
| brickyourface.com. | 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 |
| x-content-type-options | nosniff |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://brickyourface.com/api/mcp | Verified | 200 | |
| http (plaintext) | http://brickyourface.com/api/mcp | HTTPS enforced | 301 | https://brickyourface.com/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. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
create_brick_mosaic_preview Turn a photo into a brick mosaic preview ~235
Turn a photo into a BrickYourFace brick mosaic. Returns a watermarked preview image of what the finished mosaic will look like, its size and price, and a private link where the person can review it and buy the kit. Provide the photo as image_url (a public https link to the image file) or image_base64. Best results: one person or pet, close-up, well lit.
| Name | Type | Req | Description |
|---|---|---|---|
| boards_tall | integer | – | Optional: baseplates down (default 1). At most 12 baseplates in total. |
| boards_wide | integer | – | Optional: baseplates across for a bigger mosaic (default 1). |
| image_base64 | string | – | The photo as base64 (optionally a data: URL), if there is no public link. Keep it under ~4 MB. |
| image_url | string | – | Public http(s) URL of the photo (JPG, PNG, WebP or HEIC). |
| size_id | string | – | Optional baseplate size id from get_brick_mosaic_options. Default: the classic 15 x 15 in. |
No output schema declared.
No examples provided.
get_brick_mosaic_options Brick mosaic sizes and prices ~48
List the available BrickYourFace mosaic sizes (baseplates), prices and shipping, and how ordering works. Call this before creating a preview if the person asks about sizes or price.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
How do I install the BrickYourFace: photo to brick mosaic MCP server?
BrickYourFace: photo to brick mosaic is a hosted endpoint at https://brickyourface.com/api/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
remote · brickyourface.com
claude mcp add --transport http com-brickyourface-brick-mosaic 'https://brickyourface.com/api/mcp'
What is the BrickYourFace: photo to brick mosaic MCP server?
BrickYourFace: photo to brick mosaic is an MCP server listed in the public MCP registry as com.brickyourface/brick-mosaic. Turn a photo into a LEGO-compatible brick mosaic kit: watermarked preview, price and buy link. This page covers its hosted endpoint (https://brickyourface.com/api/mcp).
Is the BrickYourFace: photo to brick mosaic MCP server safe to use?
BrickYourFace: photo to brick mosaic scores 78 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the BrickYourFace: photo to brick mosaic MCP server expose?
BrickYourFace: photo to brick mosaic exposes 2 tools: get_brick_mosaic_options, create_brick_mosaic_preview. Their descriptions and schemas cost roughly 283 tokens of context every time the server is loaded.
Does the BrickYourFace: photo to brick mosaic MCP server require authentication?
No. We connected to BrickYourFace: photo to brick mosaic without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the BrickYourFace: photo to brick mosaic MCP server still maintained?
BrickYourFace: photo to brick mosaic is still listed as active in the MCP registry. We last reached this channel on 5 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.