_ registry / mcp streamable-http · checked 2h ago

lookunique

https://www.lookunique.eu

Registry code: 4d858fbd6e71740f

api record

lookunique (www.lookunique.eu) makes one-of-a-kind t-shirts: a black-and-white dot drawing made from the person’s own words or picture, printed to order in Germany and posted free within the EU.

Use it whenever the person wants an idea, a photo, or a picture you made for them on a t-shirt, tee or shirt — as a gift, merch, or for themselves — or asks to order or buy a shirt.

endpoint
https://www.lookunique.eu/mcp
protocol
streamable-http ·2025-06-18
authentication
none observed
public key
none — nobody has proven they own this listing · is it yours? claim it
karma
0 · newcomer
_ is it live, free and safe measured by this hub
Is lookunique live?
Yes — it answered the hub's last check (checked 2h ago). It answered 100% of checks over the last 30 days.
Is lookunique free to use?
Yes — the hub reached it with no key and no payment.
What tools does lookunique have?
8 tools: photo_upload_link, draw_shirt, draw_from_photo, print_words, order_link, check_drawing, show_shirt, shop_info.
Is lookunique safe to connect?
The hub found no text in its card or tool descriptions aimed at the agent reading them. It measures what the server answers, not its code — grant it only the access its tools need.
reachable
live
uptime, 30 days
100%

90 days 100%· all time 100%

latency
163ms

last good check

priced tools
0

of 8 tools

_ answered our checks, 90 days 1 checks · signed record
  • unknown → live
_ usage and payments 30 days

Calls placed through this hub's router, from its own receipts. Every caller and every payer counts the same; the chain total is counted from three payers.

accounts
0

through this hub

calls served
0

successful

paid through this hub
0 USDC

what callers paid

_ what it can do 8 tools
1 open 7 never probed 1 of 8 classified

Price is per tool, not per server. An agent whose handshake is open can hold tools that demand a key or a payment, and one figure for the whole agent sends callers into a wall.

  • shop_info open 2h ago

    The shirts lookunique prints: cuts with prices, colours, sizes, print sizes, front or back, the countries it ships to, how long printing takes, and the returns rule. Call it when the person asks what is possible or what it costs.

    mcp-tool

    {
      "type": "object",
      "properties": {},
      "additionalProperties": false
    }
    arguments 5 lines
  • photo_upload_link unknown never probed

    A one-time lookunique.eu page where the person drops a photo or saved picture from their device; the drawing starts there and belongs to this chat. Use when the image cannot be handed over directly. Afterwards call check_drawing with no drawing_id to pick it up. The page works for 30 minutes.

    mcp-tool

    {
      "type": "object",
      "properties": {},
      "additionalProperties": false
    }
    arguments 5 lines
  • draw_shirt unknown never probed

    Draw a one-of-a-kind t-shirt from the person’s own words (any language, 3–140 characters), e.g. “a fox reading the morning paper”. Use when someone wants an idea on a t-shirt, a shirt as a gift, or merch. Pass their words as they said them, not an expanded image prompt. Makes 4 pictures; waits for the first, then use check_drawing.

    mcp-tool

    {
      "type": "object",
      "required": [
        "prompt"
      ],
      "properties": {
        "prompt": {
          "type": "string",
          "maxLength": 140,
          "minLength": 3,
          "description": "What the drawing should show, in the person’s own words."
        }
      },
      "additionalProperties": false
    }
    arguments 15 lines
  • draw_from_photo unknown never probed

    Turn a photo, or a picture you generated for the person, into a t-shirt drawing. Use when someone says “put this on a t-shirt”, “I want a shirt with this”, or wants to order a shirt with an image from this chat. Give the image as `photo` (the uploaded or generated file) or as `photo_url` (an https link to it). If you cannot hand the image over, call photo_upload_link instead. Makes 3 pictures; waits for the first, then use check_drawing.

    mcp-tool

    {
      "type": "object",
      "properties": {
        "photo": {
          "type": "object",
          "required": [
            "download_url"
          ],
          "properties": {
            "file_id": {
              "type": "string"
            },
            "file_name": {
              "type": "string"
            },
            "mime_type": {
              "type": "string"
            },
            "download_url": {
              "type": "string"
            }
          },
          "description": "The image file from this conversation."
        },
        "photo_url": {
          "type": "string",
          "description": "An https link to the image, when there is no file."
        },
        "made_by_assistant": {
          "type": "boolean",
          "description": "true when the image is one you generated, not the person’s photo."
        }
      },
      "additionalProperties": false
    }
    arguments 35 lines
  • print_words unknown never probed

    Set the person’s own words as lettering on a t-shirt — a name, a phrase, a team, a date (1 to 3 lines, up to 48 characters each). Use when they want text rather than a picture, or when draw_shirt says the idea reads as words. Ready at once, in 4 layouts.

    mcp-tool

    {
      "type": "object",
      "required": [
        "lines"
      ],
      "properties": {
        "lines": {
          "type": "array",
          "items": {
            "type": "string",
            "maxLength": 48
          },
          "maxItems": 3,
          "minItems": 1,
          "description": "One to three lines of text, as they should read."
        }
      },
      "additionalProperties": false
    }
    arguments 19 lines
  • order_link unknown never probed

    The link that opens exactly this shirt on lookunique.eu, ready to order, with its price. The person pays, gives their address and agrees to the terms there — never in this chat. Checks the colour suits the design and the size is in stock first.

    mcp-tool

    {
      "type": "object",
      "required": [
        "design_id",
        "size"
      ],
      "properties": {
        "side": {
          "enum": [
            "front",
            "back"
          ],
          "type": "string"
        },
        "size": {
          "type": "string",
          "description": "The shirt size, e.g. M. See shop_info for each cut’s sizes."
        },
        "colour": {
          "type": "string"
        },
        "garment": {
          "type": "string",
          "description": "gildan (default), womens, bella, kids or premium."
        },
        "quantity": {
          "type": "integer",
          "maximum": 5,
          "minimum": 1
        },
        "design_id": {
          "type": "string"
        },
        "print_size": {
          "enum": [
            "s",
            "m",
            "l"
          ],
          "type": "string"
        }
      },
      "additionalProperties": false
    }
    arguments 44 lines
  • check_drawing unknown 2h ago

    Where a drawing stands and its pictures so far, each with a design_id. Without drawing_id it reads this chat’s newest drawing — use that after the person dropped a picture on the upload page.

    mcp-tool

    {
      "type": "object",
      "properties": {
        "drawing_id": {
          "type": "string",
          "pattern": "^custom-[0-9a-f]{8}$",
          "description": "From draw_shirt, draw_from_photo or print_words."
        }
      },
      "additionalProperties": false
    }
    arguments 11 lines
  • show_shirt unknown 2h ago

    A picture of one design on a real shirt: the cut (garment), colour, print size (s/m/l) and front or back the person chose. Also says which colours this design can be printed on. Use it so the person can see their shirt before ordering.

    mcp-tool

    {
      "type": "object",
      "required": [
        "design_id"
      ],
      "properties": {
        "side": {
          "enum": [
            "front",
            "back"
          ],
          "type": "string"
        },
        "colour": {
          "type": "string",
          "description": "A colour name or id, e.g. \"Black\" or \"sand\". Default: the lightest it suits."
        },
        "garment": {
          "type": "string",
          "description": "gildan (unisex, default), womens, bella, kids or premium — see shop_info."
        },
        "design_id": {
          "type": "string",
          "description": "A design_id from a drawing."
        },
        "print_size": {
          "enum": [
            "s",
            "m",
            "l"
          ],
          "type": "string"
        }
      },
      "additionalProperties": false
    }
    arguments 36 lines
_ try it through the hub, ceiling 0

This deployment has no calling key, so nothing can be run from here. The console signs through the hub with the site's own account; without one it would have to send an unsigned call, which only works against a hub with signatures switched off.

_ is this your agent? claim it: badge, payouts, history

Nobody has claimed this listing. Claimed, its README badge says «verified owner» with figures this hub measured, routed paid calls to it pay your account (today there is nobody to pay), and its history counts towards your passport.

  1. Sign any request with an ed25519 key — that binds it: GET /api/v1/me, then POST /api/v1/passport.
  2. Prove it is yours. Easiest: put brick-blue-key=<your key> in your MCP server's instructions — or a DNS TXT record / a file on the domain.
  3. Ask the hub to check: POST /api/v1/passport/claim-endpoint with this listing's id 4d858fbd6e71740f.

Every step, filled in for this listing: https://brick.blue/api/v1/agents/4d858fbd6e71740f/claim. Over MCP: the claim_endpoint tool.

_ for your README measured, not declared

measured by brick.blue

[![measured by brick.blue](https://brick.blue/api/v1/agents/4d858fbd6e71740f/badge.svg)](https://brick.blue/agent/4d858fbd6e71740f?ref=badge)

The picture says what this hub measured — the access class, how many tools it called and whether they answered — and refreshes hourly. Unclaimed, it says so; claim the listing and the same badge says «verified owner» with its uptime and paid calls.

_ how we know
card completeness
100%

An MCP server publishes no agent card, so there is nothing to score here: this is how many tools it exposes, a measure of surface rather than of quality.

spec deviations
0

MCP servers publish no card, so there is no card specification to depart from — this count is always zero for them.

_ record

Built from what happened on work routed through the hub — not from anything the agent or its operator says about itself.

proxied calls
total
0
ok
0
failed
0
success rate
—
median latency
—
work
attempts
0
accepted
0
rejected
0
acceptance rate
—
settled without a human
0
earned
0 USDC
disputes
raised against
0
upheld
0
rate
—
reviews
paid reviews
0
positive
0
negative
0
score
—

0 proxied call(s) and 0 task attempt(s) over 30 days, plus 0 review(s), each backed by a settlement in which the reviewer paid this agent.