# Tattoo Brief MCP (mcpb · server.mcpb)

Deterministic MCP tools for tattoo briefs, small-size legibility checks, and line-art prompts.

- Trust score: 46/100 (low)
- Change this week: +3
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-05

## Components

- mcpb · `server.mcpb`: 46/100 (this document), [markdown](https://verifymcp.io/servers/mazzawill-tattoo-brief-mcp/server.md), [page](https://verifymcp.io/servers/mazzawill-tattoo-brief-mcp/server)

## Channel facts

- Registry: `mcpb`
- Package: `https://github.com/MazzaWill/tattoo-brief-mcp/releases/download/v0.1.0/server.mcpb`
- Transport: `stdio`
- SHA-256: `531d8867fd2ce7d481ed112224d067266fa2eb19b1c08abc1efa3921290aac12`

## Trust breakdown

How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-11-05.

- **Supply Chain Security**: 23/100
  - No malware scan is available for this kind of package: the supply-chain vendors we use do not cover it. This is a permanent gap in our coverage, not a finding about the package.
  - Known CVEs were checked across the 92 of 92 dependencies we could resolve, so this covers what we could see, not the whole tree.
  - No install/post-install scripts declared.
  - 30 of 92 dependencies flagged as unhealthy.
- **Provenance & Transparency**: 45/100
  - Source repository is publicly reachable at the declared URL.
  - Provenance check failed: no build-provenance attestation is published.
  - Clear OSI-approved license (MIT).
  - Actively maintained (last published 10 days ago).
  - Disclosure check failed: no security disclosure policy was found in the source repository.
- **Schema Quality & AI Usability**: 54/100
  - AI-judged instruction clarity (fair).
  - Tool/resource definitions use about 194 tokens (~64/item across 3 items; 3 tools + 0 resources), lean.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 37/100
  - Stability observed for 11 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 67/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 0% of tool parameters carry a description.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 3 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 3 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.

## Install

### How do I install the Tattoo Brief MCP server?

Tattoo Brief MCP ships as an MCPB bundle, a single file you download and open in an MCP host that supports MCPB bundles, such as Claude Desktop. The host reads the launch command from the bundle's own manifest, so there is no command to copy. Before opening it, check the file's SHA-256 matches the one the MCP registry declares for it, 531d8867fd2ce7d481ed112224d067266fa2eb19b1c08abc1efa3921290aac12; the commands to do that are on this page. If it does not match, do not open it.

- Download bundle: `https://github.com/MazzaWill/tattoo-brief-mcp/releases/download/v0.1.0/server.mcpb`
- SHA-256: `531d8867fd2ce7d481ed112224d067266fa2eb19b1c08abc1efa3921290aac12`

### Verify on macOS / Linux

```bash
echo "531d8867fd2ce7d481ed112224d067266fa2eb19b1c08abc1efa3921290aac12  server.mcpb" | shasum -a 256 -c
```

### Verify on Windows (PowerShell)

```powershell
(Get-FileHash -Algorithm SHA256 .\server.mcpb).Hash -eq "531d8867fd2ce7d481ed112224d067266fa2eb19b1c08abc1efa3921290aac12"
```

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-11-04 (score 46, +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.

### 2026-11-02 (score 45, +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.

### 2026-10-31 (score 44, +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.

### 2026-10-29 (score 43, +1)

No change was recorded against any check on this day. Stability & Change Management went from 10 to 13. That category is still filling its 30-day observation window: 3 days of observed history at the previous scan, 4 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-10-27 (score 42, +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.

### 2026-10-25 (score 41)

First indexed and scored.

## MCP tools (3)

### `build_tattoo_brief` (~84 tokens)

Turn a tattoo idea, style, placement and size into a structured brief to bring to a tattoo artist.

Input parameters:

- `avoid` (array)
- `color` (string)
- `idea` (string, required)
- `must_include` (array)
- `placement` (string, required)
- `size_cm` (number, required)
- `style` (string, required)

### `check_small_size_legibility` (~48 tokens)

Heuristic blur-risk check for tattoo details at a given size. Rules of thumb only, not a guarantee.

Input parameters:

- `details` (array, required)
- `size_cm` (number, required)

### `line_art_prompt` (~62 tokens)

Write a clean line-art prompt (plus negative prompt) for an AI tattoo generator.

Input parameters:

- `composition` (string)
- `extra` (array)
- `line_weight` (string)
- `style` (string)
- `subject` (string, required)

## Diagnostics

Captured diagnostic sections: Provenance, Dependencies. The full working is on the page: https://verifymcp.io/servers/mazzawill-tattoo-brief-mcp/server#diagnostics

## Score history

- 2026-11-05: 46
- 2026-11-04: 46
- 2026-11-03: 45
- 2026-11-02: 45
- 2026-11-01: 44
- 2026-10-31: 44
- 2026-10-30: 43
- 2026-10-29: 43
- 2026-10-28: 42
- 2026-10-27: 42
- 2026-10-26: 41
- 2026-10-25: 41

## Common questions

### What is the Tattoo Brief MCP server?

Tattoo Brief MCP is listed in the public MCP registry as io.github.MazzaWill/tattoo-brief-mcp. Deterministic MCP tools for tattoo briefs, small-size legibility checks, and line-art prompts. This page covers its MCPB bundle (https://github.com/MazzaWill/tattoo-brief-mcp/releases/download/v0.1.0/server.mcpb).

### Is the Tattoo Brief MCP server safe to use?

Tattoo Brief MCP scores 46 out of 100 on VerifyMCP. It declares no install or post-install scripts. 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 Tattoo Brief MCP server expose?

Tattoo Brief MCP exposes 3 tools: build_tattoo_brief, check_small_size_legibility, line_art_prompt. Their descriptions and schemas cost roughly 194 tokens of context every time the server is loaded.

### What licence is the Tattoo Brief MCP server under?

Tattoo Brief MCP declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.

### What did VerifyMCP test on the Tattoo Brief MCP server?

VerifyMCP ran 15 checks on Tattoo Brief MCP, covering Known CVEs, Install scripts, Dependency health, Source repository and 11 more. One item could not be completed, a gap on our side rather than a finding about Tattoo Brief MCP: Malware scan. Endpoint Security and Transport & Reachability do not apply to an MCPB bundle, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.

## Links

- Repository: https://github.com/MazzaWill/tattoo-brief-mcp
- Website: https://tatany.app/
- Changelog RSS feed: https://verifymcp.io/servers/mazzawill-tattoo-brief-mcp/server.xml
- Changelog JSON feed: https://verifymcp.io/servers/mazzawill-tattoo-brief-mcp/server/changelog.json
- Trust report (JSON): https://verifymcp.io/servers/mazzawill-tattoo-brief-mcp/server.json
- HTML version of this page: https://verifymcp.io/servers/mazzawill-tattoo-brief-mcp/server