check.tattoo: tattoo size and placement guide
REMOTE · MCP.CHECK.TATTOO
Tattoo size minimums, body-area comparison, line-spacing check and a pre-booking checklist.
Available components
Last scanned (1 hour ago)
Scores higher than 40% of remote servers
Unreachable for 4 days in a row. Last reached 1 Nov 2026.
Degraded
One or more channels of this server are currently unreachable; their trust score is decaying and will reach 0 if they stay down.
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 Security0
- TLS not yet verified: we couldn't open a connection to check the certificate. View diagnostics → Unverified
- Authorisation not yet verified: we couldn't confirm whether this endpoint requires it. View diagnostics → Unverified
- HTTPS enforcement could not be verified: the plaintext port answered with HTTP 404, which proves neither a plaintext path nor enforcement. View diagnostics → Unverified
- HSTS not yet verified: we couldn't read the response headers to check for it. View diagnostics → Unverified
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability0
- Transport check failed: declared streamable-http, but we couldn't connect to verify it. See how to fix → View diagnostics → Fail
Schema Quality & AI Usability0
- Schema not yet verified: we couldn't read the endpoint's schema, or could read only part of its tool list.Unverified
Stability & Change Management0
- Stability not yet verified: not enough scan history yet (needs a 30-day window).Unverified
Tool Coverage0
- Tool coverage not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.Unverified
Tool Safety0
- Tool safety not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.Unverified
Capabilities0
- Capabilities not yet verified: we couldn't read the endpoint's capabilities.Unverified
Unverified: 5 categories
Categories scored 0 because we could not verify them: authentication we do not have, an unreachable endpoint, or not enough scan history. We only credit what we can confirm.
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.
- 5 Nov 26 −14
The score moved with no change recorded against any check. We would rather say so than guess.
- 4 Nov 26 −15
The score moved with no change recorded against any check. We would rather say so than guess.
- 2 Nov 26 0
- Endpoint reachability: reachable → unreachable ▼ security
- HSTS header: fail → unverified ▼ security
- Authorization: partial → unverified ▼ security
- Tool safety: pass → unverified ▼ security
- TLS certificate: pass → unverified ▼ security
- Stability: 0.50 → unverified ▼ security
- Transport: pass → fail ▼ security
- Capabilities: pass → unverified ▼ functional
- Tool coverage: 100 → unverified ▼ functional
- First check of Schema quality: unverified functional
- 31 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 43 to 47. That category is still filling its 30-day observation window: 13 days of observed history at the previous scan, 14 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 37 to 40. That category is still filling its 30-day observation window: 11 days of observed history at the previous scan, 12 at this one. The score rises as the window fills, whether or not the server changes.
- 27 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 30 to 33. That category is still filling its 30-day observation window: 9 days of observed history at the previous scan, 10 at this one. The score rises as the window fills, whether or not the server changes.
- 25 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 23 to 27. That category is still filling its 30-day observation window: 7 days of observed history at the previous scan, 8 at this one. The score rises as the window fills, whether or not the server changes.
- 23 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 17 to 20. That category is still filling its 30-day observation window: 5 days of observed history at the previous scan, 6 at this one. The score rises as the window fills, whether or not the server changes.
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://mcp.check.tattoo/mcp
TLS unreached
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of mcp.check.tattoo. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| tattoo. | present | 20907 | 13 | Verified |
| check.tattoo. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication Inconclusive
We could not reach the endpoint well enough to judge its authorisation posture.
| Result | Inconclusive |
|---|
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://mcp.check.tattoo/mcp | Unreachable | ||
| http (plaintext) | http://mcp.check.tattoo/mcp | Inconclusive | 404 |
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 →
assess_tattoo_idea Assess a tattoo idea's size, placement and style ~281
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.
| Name | Type | Req | Description |
|---|---|---|---|
| design_type | string | yes | 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 (t… |
| letter_height_mm | number | – | Height of a capital letter in millimetres. Use for block_capitals and script_lettering. |
| placement | string | – | Body area, if the user has one in mind. |
| size_cm | number | – | Longest side of the whole design in centimetres. Use for every design_type except block_capitals and script_lettering. |
| style | string | – | Tattoo style, if the user has one in mind. |
| Name | Type | Req | Description |
|---|---|---|---|
| design_type | string | – | – |
| note | string | – | – |
| placement_profile | object | – | – |
| questions_for_the_artist | array | – | – |
| size_check | object | – | – |
| sources | array | – | – |
| style_notes | object | – | – |
| things_to_look_at | array | – | – |
| touch_ups | string | – | – |
No examples provided.
check_line_spacing Check whether the gap between lines will stay open ~193
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.
| Name | Type | Req | Description |
|---|---|---|---|
| gap_mm | number | yes | Width of the space between the two lines or letters, in millimetres. |
| line_width_mm | number | yes | Width of the line in millimetres, as drawn today (for example 0.3 fine line, 1.5 bold outline). |
| years | number | – | Years to project. Defaults to 20. |
| Name | Type | Req | Description |
|---|---|---|---|
| after | object | – | – |
| assumptions | object | – | – |
| explanation | string | – | – |
| guide_gap_range_mm | object | – | – |
| note | string | – | – |
| source | string | – | – |
| sources | array | – | – |
| status | string | – | – |
| today | object | – | – |
| worked_example | object | – | – |
| years_until_gap_used_up | number | – | – |
No examples provided.
compare_tattoo_placements Compare body areas for a tattoo ~102
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.
| Name | Type | Req | Description |
|---|---|---|---|
| placements | array | – | Areas to compare. Omit for all ten. |
| sort_by | string | – | Order, lowest first. Defaults to fade. |
| Name | Type | Req | Description |
|---|---|---|---|
| areas | array | – | – |
| note | string | – | – |
| sorted_by | string | – | – |
| source | string | – | – |
No examples provided.
get_pre_booking_checklist Get a checklist to use before booking a tattoo ~73
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.
Input schema present but exposes no named parameters.
| Name | Type | Req | Description |
|---|---|---|---|
| ask_the_artist | string | – | – |
| note | string | – | – |
| red_flags | string | – | – |
| source | string | – | – |
| steps | array | – | – |
No examples provided.
get_tattoo_size_chart Get the tattoo size chart ~103
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.
| Name | Type | Req | Description |
|---|---|---|---|
| size_cm | number | – | Optional size in centimetres to look up what fits. |
| Name | Type | Req | Description |
|---|---|---|---|
| note | string | – | – |
| rows | array | – | – |
| scale | array | – | – |
| source | string | – | – |
| updated | string | – | – |
No examples provided.
How do I install the check.tattoo: tattoo size and placement guide MCP server?
check.tattoo: tattoo size and placement guide is a hosted endpoint at https://mcp.check.tattoo/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 · mcp.check.tattoo
claude mcp add --transport http tattoo-check-check-tattoo 'https://mcp.check.tattoo/mcp'
What is the check.tattoo: tattoo size and placement guide MCP server?
check.tattoo: tattoo size and placement guide is an MCP server listed in the public MCP registry as tattoo.check/check-tattoo. Tattoo size minimums, body-area comparison, line-spacing check and a pre-booking checklist. This page covers its hosted endpoint (https://mcp.check.tattoo/mcp).
Is the check.tattoo: tattoo size and placement guide MCP server safe to use?
check.tattoo: tattoo size and placement guide scores 44 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 check.tattoo: tattoo size and placement guide MCP server expose?
check.tattoo: tattoo size and placement guide exposes 5 tools: assess_tattoo_idea, check_line_spacing, get_tattoo_size_chart, compare_tattoo_placements, get_pre_booking_checklist. Their descriptions and schemas cost roughly 752 tokens of context every time the server is loaded.
Does the check.tattoo: tattoo size and placement guide MCP server require authentication?
Its publisher declares no required credentials for check.tattoo: tattoo size and placement guide. We have not been able to confirm that against the live endpoint, and a server can require authorisation without declaring it here.
Is the check.tattoo: tattoo size and placement guide MCP server still maintained?
check.tattoo: tattoo size and placement guide is still listed in the MCP registry, but we have not been able to reach this channel for several days and its score is decaying. We last reached this channel on 1 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.