check.tattoo: tattoo size and placement guide MCP server
tattoo.check/check-tattoocheck.tattoostreamable-httpv1.2.0Scanned
Tattoo size minimums, body-area comparison, line-spacing check and a pre-booking checklist.
5 tools: 2 change things and 3 only read.
- Reads private data · 0
- Reads text others write · 0
- Can send data out · 0
- No findings
Tools listed without sign-in. Remote posture
With Anlyon
2 tools here change things. Govern them.
- Anlyon lists the tools and adopts none.
- Each tool you adopt gets approvals and receipts.
- Your agent never holds the key.
A tool your agent calls directly is not routed through Anlyon and is not governed by it. Anlyon Radar only lists and labels, and these labels are the same either way.
What the check.tattoo: tattoo size and placement guide MCP server can do
The check.tattoo: tattoo size and placement guide MCP server is published by check.tattoo, a domain the MCP Registry verified. It has 5 tools. It can create or change data (2 tools: assess_tattoo_idea and check_line_spacing), but cannot delete data. 3 tools only read.
None of its tools reads private data, brings in text other people write, or sends data out.
None of the fixed checks matched anything in its tool definitions. That is not a safety guarantee.
Its remote endpoint lists its tools without sign-in.
Last scanned Nov 19, 2026, version 1.2.0.
Tools
Grouped by what each tool does, most consequential first. Open one for its reasons and full description; descriptions are the publisher's own words.
5 tools
Changes things 2Claude Code: ask
assess_tattoo_ideaUse when the user describes a specific tattoo idea and asks whether it will hold up at a given size and body placement.No findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
- The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
Description, as the server wrote it 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.
Annotations the server declares
- readOnlyHint: true
- destructiveHint: false
- openWorldHint: false
- idempotentHint: true
- title: Assess a tattoo idea's size, placement and style
check_line_spacingUse 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.No findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
- The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
Description, as the server wrote it 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.
Annotations the server declares
- readOnlyHint: true
- destructiveHint: false
- openWorldHint: false
- idempotentHint: true
- title: Check whether the gap between lines will stay open
Only reads 3Show 3 read-only tools
compare_tattoo_placementsUse when the user asks how body areas compare for pain, fading, sun, friction, stretch or curvature, or which areas hold ink longest.No findings
Why it is in this group
- The name "compare_tattoo_placements" says "compare": a word for reading.
Description, as the server wrote it 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.
Annotations the server declares
- readOnlyHint: true
- destructiveHint: false
- openWorldHint: false
- idempotentHint: true
- title: Compare body areas for a tattoo
get_pre_booking_checklistUse 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.No findings
Why it is in this group
- The name "get_pre_booking_checklist" says "get": a word for reading.
Description, as the server wrote it 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.
Annotations the server declares
- readOnlyHint: true
- destructiveHint: false
- openWorldHint: false
- idempotentHint: true
- title: Get a checklist to use before booking a tattoo
get_tattoo_size_chartUse when the user asks how big or how small a kind of tattoo can be, or what fits at a given size.No findings
Why it is in this group
- The name "get_tattoo_size_chart" says "get": a word for reading.
Description, as the server wrote it 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.
Annotations the server declares
- readOnlyHint: true
- destructiveHint: false
- openWorldHint: false
- idempotentHint: true
- title: Get the tattoo size chart
This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.
Exfil surface
Which tools read private data, which read text someone else can write, and which can send data out. One of each is a path a prompt injection can use.
No private-data, untrusted-input, outbound path in this server alone: no tool is tagged private-data or untrusted-input or outbound.
- Reads private data0
- Reads files, mail, messages, databases, secrets, calendars or repositories.
- Reads text others write0
- Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
- Can send data out0
- Can carry data to people or systems: it sends, posts or publishes, or takes a recipient, channel or URL.
Other servers in the same agent add their own tools to these paths. Audit your whole setup to see them together.
Remote posture
What anyone on the internet sees at the remote endpoint: an anonymous initialize and tools/list, and the public OAuth metadata.
Looked at Nov 20, 2026, 19:19 UTC, unchanged since Nov 13, 2026. No credentials were sent and no tool was called. What is looked at.
- Reachable
- yes
- HTTP status of an anonymous initialize
- 200
- tools/list served without credentials
- yes
- Tools that change things, listed without credentials
- 2
- Protocol version
- 2025-06-18
- WWW-Authenticate on 401
- not observed
- resource_metadata in WWW-Authenticate
- not observed
- RFC 9728 protected resource metadata
- not observed
- Authorization servers
- not observed
- Legacy HTTP+SSE transport
- no
- Dynamic client registration
- not observed
- Client ID metadata documents
- not observed
- WarnThe whole server
The endpoint served tools/list without credentials, and the list has 2 tools that change things (2 write). Whether a call also works without credentials was not tested: tools are never called.
What this check looks forMatched text
https://mcp.check.tattoo/mcp: tools/list returned 5 tools to an anonymous client, including assess_tattoo_idea (write), check_line_spacing (write)
Posture changes
- Nov 13, 2026
- Reachable: no to yes
- HTTP status of an anonymous initialize: none to 200
- tools/list served without credentials: no to yes
- Tools that change things, listed without credentials: 0 to 2
- Protocol version: none to 2025-06-18
- Nov 6, 2026
- Reachable: yes to no
- HTTP status of an anonymous initialize: 200 to none
- tools/list served without credentials: yes to no
- Tools that change things, listed without credentials: 2 to 0
- Protocol version: 2025-06-18 to none
Findings
Matches of fixed checks, with the text they matched.
No check matched anything in these tool definitions. That is not a safety guarantee.
History
Changes to its tool definitions and to its remote endpoint, newest first.
PostureRemote posture changed. Reachable: no -> yes; HTTP status of an anonymous initialize: none -> 200; tools/list served without credentials: no -> yes (and 2 more).View diff
- Reachable: no to yes
- HTTP status of an anonymous initialize: none to 200
- tools/list served without credentials: no to yes
- Tools that change things, listed without credentials: 0 to 2
- Protocol version: none to 2025-06-18
PostureRemote posture changed. Reachable: yes -> no; HTTP status of an anonymous initialize: 200 -> none; tools/list served without credentials: yes -> no (and 2 more).View diff
- Reachable: yes to no
- HTTP status of an anonymous initialize: 200 to none
- tools/list served without credentials: yes to no
- Tools that change things, listed without credentials: 2 to 0
- Protocol version: 2025-06-18 to none
Install
Pinned to version 1.2.0. Values in angle brackets are yours to fill in.
claude mcp add --transport http check-tattoo https://mcp.check.tattoo/mcpclaude mcp add --transport http check-tattoo https://mcp.check.tattoo/mcpRun in a terminal.
Claude Code permissions
Allow the reads, ask before a change or a way out, deny the deletes. Paste into .claude/settings.json.
{
"permissions": {
"allow": [
"mcp__check-tattoo__get_tattoo_size_chart",
"mcp__check-tattoo__compare_tattoo_placements",
"mcp__check-tattoo__get_pre_booking_checklist"
],
"ask": [
"mcp__check-tattoo__assess_tattoo_idea",
"mcp__check-tattoo__check_line_spacing"
],
"deny": []
}
}Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. A read that can send data out (it takes a URL, say) asks first too. It assumes the server is installed as check-tattoo. Review it before you use it.
Pin
Keep the decision: fail CI when the tools change, follow every change, or show a badge.
Pin in CI
Fail a build when the tools you reviewed are not the tools the server serves today.
curl -s "https://radar.anlyon.com/api/v1/servers/tattoo.check/check-tattoo/verify?hash=5612fbb64cab99c8759cc1749f509ce327db58ce874f165def8ad950d1b004ad" | jq -e '.changed == false'Pinned hash 5612fbb64cab, from Nov 19, 2026, 06:17 UTC.
Watch
Get told when its tools change: a new tool, a new description, a new class.
https://radar.anlyon.com/servers/tattoo.check/check-tattoo/changes.xmlAn Atom feed. Works in any feed reader or Slack's RSS app.
Badge
[](https://radar.anlyon.com/servers/tattoo.check/check-tattoo)Source: MCP Registry. Synced Oct 21, 2026, 18:55 UTC.
check.tattoo: tattoo size and placement guide MCP server: questions and answers
Answered from the scan above, not from the publisher's description.
Is the check.tattoo: tattoo size and placement guide MCP server safe?
- No scan can promise that. What its definitions show: 5 tools, 2 of which can change, send or delete something, and 0 findings from fixed checks. Allow the reads, ask before each change, and deny the deletes; the permissions block on this page does that.
Can the check.tattoo: tattoo size and placement guide MCP server delete data?
- No tool is classed as destructive: going by their definitions, none of them deletes, cancels or revokes anything.
Can the check.tattoo: tattoo size and placement guide MCP server do things that cannot be undone?
- No tool is classed as irreversible: none of them sends, pays, publishes or merges, going by their definitions.
What tools does the check.tattoo: tattoo size and placement guide MCP server have?
- 5 tools: 2 write, 3 read. assess_tattoo_idea, check_line_spacing, get_tattoo_size_chart, compare_tattoo_placements and get_pre_booking_checklist.
Does the check.tattoo: tattoo size and placement guide MCP server need sign-in or OAuth?
- Its remote endpoint listed its tools to an anonymous client, without sign-in.
Does the check.tattoo: tattoo size and placement guide MCP server send data to outside services?
- None of its tools sends, posts or publishes, or takes a recipient, channel or URL.
Has the check.tattoo: tattoo size and placement guide MCP server changed its tools?
- Not since Anlyon Radar started tracking it. Last scanned Nov 19, 2026.