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

check-tattoo

https://mcp.check.tattoo

Registry code: 891486d87635cfdd

api record

Reference tools for people planning a tattoo: minimum sizes by kind of design, how body areas compare, and a pre-booking checklist. Answers are general guidance from published tables at check.tattoo, not a prediction for one design or one person's skin, and not medical advice. The app does not generate designs or read images, and it does not store what it receives.

endpoint
https://mcp.check.tattoo/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 check-tattoo live?
Yes — it answered the hub's last check (checked 2h ago). It answered 100% of checks over the last 30 days.
Is check-tattoo free to use?
Yes — the hub reached it with no key and no payment.
What tools does check-tattoo have?
5 tools: check_line_spacing, get_pre_booking_checklist, assess_tattoo_idea, compare_tattoo_placements, get_tattoo_size_chart.
Is check-tattoo 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
83ms

last good check

priced tools
0

of 5 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 5 tools
2 open 3 never probed 2 of 5 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.

  • compare_tattoo_placements open 2h ago

    Use when the user asks how body areas compare for pain, fading, sun, friction, stretch or curvature, or which areas hold ink longest. Returns the ten common areas (or the ones requested), ordered by fade by default. Estimates are coarse 0-100 comparisons, not measurements.

    mcp-tool

    {
      "type": "object",
      "properties": {
        "sort_by": {
          "enum": [
            "fade",
            "pain",
            "sun",
            "friction"
          ],
          "type": "string",
          "description": "Order, lowest first. Defaults to fade."
        },
        "placements": {
          "type": "array",
          "items": {
            "enum": [
              "upper-arm",
              "forearm",
              "back",
              "shoulder",
              "leg",
              "hand",
              "neck",
              "chest",
              "ribs",
              "wrist"
            ],
            "type": "string"
          },
          "description": "Areas to compare. Omit for all ten."
        }
      },
      "additionalProperties": false
    }
    arguments 35 lines
  • get_tattoo_size_chart open 2h ago

    Use when the user asks how big or how small a kind of tattoo can be, or what fits at a given size. Returns the smallest and better size for eight kinds of design (letters by height, other designs by longest side), real-world size comparisons and the small/medium/large ranges. Optional size_cm marks which designs meet their minimum at that size.

    mcp-tool

    {
      "type": "object",
      "properties": {
        "size_cm": {
          "type": "number",
          "maximum": 500,
          "description": "Optional size in centimetres to look up what fits.",
          "exclusiveMinimum": 0
        }
      },
      "additionalProperties": false
    }
    arguments 12 lines
  • check_line_spacing unknown never probed

    Use when the user gives a line width and the gap between two lines or letters in millimetres and asks whether the gap will stay open as the tattoo ages. Applies the published rule of thumb that a line widens by about 0.1 mm per decade: returns the line width and gap after the given number of years (default 20), whether the gap meets the guides' 'at least as wide as the line' rule, and what the guide's worked example would do to it. Illustrative arithmetic, not a measurement.

    mcp-tool

    {
      "type": "object",
      "required": [
        "line_width_mm",
        "gap_mm"
      ],
      "properties": {
        "years": {
          "type": "number",
          "maximum": 60,
          "minimum": 1,
          "description": "Years to project. Defaults to 20."
        },
        "gap_mm": {
          "type": "number",
          "maximum": 50,
          "description": "Width of the space between the two lines or letters, in millimetres.",
          "exclusiveMinimum": 0
        },
        "line_width_mm": {
          "type": "number",
          "maximum": 10,
          "description": "Width of the line in millimetres, as drawn today (for example 0.3 fine line, 1.5 bold outline).",
          "exclusiveMinimum": 0
        }
      },
      "additionalProperties": false
    }
    arguments 28 lines
  • get_pre_booking_checklist unknown never probed

    Use when the user asks how to decide whether they are ready to book a tattoo, what to ask an artist, or what red flags to watch for in a consultation. Returns a short ordered checklist, the one question to ask when an artist pushes back, how to judge healed work, and consultation red flags.

    mcp-tool

    {
      "type": "object",
      "properties": {},
      "additionalProperties": false
    }
    arguments 5 lines
  • assess_tattoo_idea unknown 2h ago

    Use when the user describes a specific tattoo idea and asks whether it will hold up at a given size and body placement. Compares the design with published minimum sizes for its kind of design and returns the placement's fade, sun, friction, stretch and curvature estimates, style notes, things to look at and questions for the artist. Lettering is sized by capital letter height (letter_height_mm); everything else by the longest side (size_cm). It does not generate designs, look at images, or give medical advice.

    mcp-tool

    {
      "type": "object",
      "required": [
        "design_type"
      ],
      "properties": {
        "style": {
          "enum": [
            "fine-line",
            "watercolor",
            "realism",
            "blackwork",
            "minimalist"
          ],
          "type": "string",
          "description": "Tattoo style, if the user has one in mind."
        },
        "size_cm": {
          "type": "number",
          "maximum": 500,
          "description": "Longest side of the whole design in centimetres. Use for every design_type except block_capitals and script_lettering.",
          "exclusiveMinimum": 0
        },
        "placement": {
          "enum": [
            "upper-arm",
            "forearm",
            "back",
            "shoulder",
            "leg",
            "hand",
            "neck",
            "chest",
            "ribs",
            "wrist"
          ],
          "type": "string",
          "description": "Body area, if the user has one in mind."
        },
        "design_type": {
          "enum": [
            "block_capitals",
            "script_lettering",
            "eye",
            "bold_symbol_or_short_word",
            "fine_botanical",
            "moderate_detail",
            "realistic_face",
            "realism_japanese_or_dense_floral"
          ],
          "type": "string",
          "description": "Kind of design: block_capitals (capital letters), script_lettering, eye, bold_symbol_or_short_word (silhouette, simple symbol), fine_botanical (flower or plant with veins/stamens), moderate_detail (two line weights, simple shading), realistic_face, realism_japanese_or_dense_floral."
        },
        "letter_height_mm": {
          "type": "number",
          "maximum": 500,
          "description": "Height of a capital letter in millimetres. Use for block_capitals and script_lettering.",
          "exclusiveMinimum": 0
        }
      },
      "additionalProperties": false
    }
    arguments 62 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 891486d87635cfdd.

Every step, filled in for this listing: https://brick.blue/api/v1/agents/891486d87635cfdd/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/891486d87635cfdd/badge.svg)](https://brick.blue/agent/891486d87635cfdd?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
90%

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.