Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

Ink Studio AI

NPM · INKSTUDIOAI

Generate AI tattoo designs in 13 styles, search a public tattoo gallery, and check plans.

Available components

+6 this week 85 Trust /100

Last scanned (28 minutes ago)

Scores higher than 87% of npm servers

Category Design and Media

Trust breakdown (7 categories)

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. How we score → Why this is hard to score →

Supply Chain Security100
  • No malware found by supply-chain analysis.Pass
  • No known CVEs affecting this package version or its production dependencies.Pass
  • No install/post-install scripts declared.Pass
  • No production dependencies, so there is no dependency health to assess. View diagnostics → Pass
Provenance & Transparency100
  • Source repository is publicly reachable at the declared URL. View diagnostics → Pass
  • Cryptographically verified build provenance (signed, bound to ciroartz/inkstudioai-cli). View diagnostics → Pass
  • Clear OSI-approved license (MIT).Pass
  • Actively maintained (last published 11 days ago).Pass
  • Publishes a security disclosure policy (SECURITY.md).Pass
Schema Quality & AI Usability74
  • AI-judged instruction clarity (good).Pass
  • Tool/resource definitions use about 500 tokens (~71/item across 7 items; 7 tools + 0 resources), lean.Pass
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management40
  • Stability observed for 12 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage96
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 89% of tool parameters carry a description.Partial
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • We read all 7 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 8 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities60
  • Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28. See how to fix → Fail
Changelog

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 +6
    • Stability: unverified → 0.40 ▲ functional
  • 25 Oct 26 +26
    • Malware scan: unverified → pass ▲ security
    • Known CVEs: unverified → pass ▲ security
    • Dependency health: unverified → pass ▲ functional
  • 24 Oct 26 53

    First indexed and scored.

Diagnostics

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 · Analysed npm/inkstudioai@0.1.1

Provenance Verified

A signed build attestation was found and verified, binding this exact artifact to the source repository it claims to come from.

Result Verified
Ecosystem npm
Reason Verified
Discovered via Registry attestation endpoint
Source repo ciroartz/inkstudioai-cli
Certificate issuer https://token.actions.githubusercontent.com
Certificate SAN https://github.com/ciroartz/inkstudioai-cli/.github/workflows/release.yml@refs/tags/v0.1.1
Rekor log index 3440650065
Predicate type SLSA build provenance https://slsa.dev/provenance/v1
Subject digest sha512:588f4f0a5dabb5e3a07c31ae19c210a5394595edf5877aa256e01a85d60725ffcbeb0d54974a8425caeb71076434e92592eff43bca65ae82cff5d1c1a

Background: How many MCP packages publish verified provenance →

Dependencies 0 packages
Packages resolved 0
Tree resolution Complete

Background: SBOMs and build attestations, explained →

MCP tools · 7 exposed · ~385 tokens

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 →

Tool Tokens
create_checkout ~64

Create a Stripe checkout link for a plan or credit pack sku from get_pricing. Nothing is charged until the user opens the link and pays. Give the URL to the user.

NameTypeReqDescription
skustringyesA sku from get_pricing, for example 7-day-access.

No output schema declared.

No examples provided.

generate_tattoo ~123

Create a tattoo design from a text prompt. Takes 10 to 40 seconds. Returns the image and its URL. Uses one generation from the account. The design is saved privately to the user's account.

NameTypeReqDescription
backgroundstring–white (default) or skin to show the design on skin.
colorboolean–Color ink. Default: black ink.
negativePromptstring–Things to leave out.
promptstringyesWhat the tattoo shows.
stylestring–Style id from list_styles. Default: minimal.

No output schema declared.

No examples provided.

get_account ~24

Show the plan, free generations left, premium credits, and API usage today.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

get_pricing ~23

List the plans and credit packs with their sku and price in USD.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

list_styles ~19

List the style ids that generate_tattoo accepts.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

login ~72

Sign in without a terminal. The first call returns a link and a code: give both to the user, who approves the code in the browser (new accounts get one free design). After the user approves, call login again. It saves the API key on this computer, and the other tools then work without a restart.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

search_gallery ~60

Search public tattoo designs for ideas. Works without an API key.

NameTypeReqDescription
limitinteger–Default: 12.
pageinteger––
querystring–Words to search for, for example dragon. Empty for the newest designs.

No output schema declared.

No examples provided.

Install

How do I install the Ink Studio AI MCP server?

Ink Studio AI runs locally as an npm package, launched with npx -y inkstudioai. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

npm · inkstudioai

# add to Claude Code
claude mcp add ciroartz-inkstudioai -- npx -y inkstudioai
Common questions

What is the Ink Studio AI MCP server?

Ink Studio AI is an MCP server listed in the public MCP registry as io.github.ciroartz/inkstudioai. Generate AI tattoo designs in 13 styles, search a public tattoo gallery, and check plans. This page covers its npm package (inkstudioai).

Is the Ink Studio AI MCP server safe to use?

Ink Studio AI scores 85 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 5 November 2026. It declares no install or post-install scripts. Its build provenance is signed and verified. 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 Ink Studio AI MCP server expose?

Ink Studio AI exposes 7 tools: login, generate_tattoo, list_styles, get_account, search_gallery, and 2 more. Their descriptions and schemas cost roughly 385 tokens of context every time the server is loaded.

Is the Ink Studio AI MCP server still maintained?

Ink Studio AI is still listed as active in the MCP registry. We last reached this channel on 5 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

What licence is the Ink Studio AI MCP server under?

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