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.

1211 - your picture on a shirt

REMOTE · 1211HOLDING.COM

Put any picture on a shirt, hoodie, cap, tumbler or tote; get the link where the person buys it.

Available components

+2 this week 86 Trust /100

Last scanned (9 hours ago)

Scores higher than 93% of remote servers

Reachable. Last reached 5 Nov 2026.

Category E-commerce

Trust breakdown (7 categories)

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 Security80
Transport & Reachability100
Schema Quality & AI Usability66
  • AI-judged instruction clarity (good).Pass
  • Context-footprint check failed: tool/resource definitions use about 936 tokens (~187/item across 5 items; 5 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management100
  • No destabilizing schema changes in the last 30 days.Pass
Tool Coverage98
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 95% 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 5 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 6 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
  • Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
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.

  • 1 Nov 26 +1
    • Stability: 0.97 → pass security
  • 30 Oct 26 +1

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

  • 28 Oct 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 83 to 87. That category is still filling its 30-day observation window: 25 days of observed history at the previous scan, 26 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 73 to 77. That category is still filling its 30-day observation window: 22 days of observed history at the previous scan, 23 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 67 to 70. That category is still filling its 30-day observation window: 20 days of observed history at the previous scan, 21 at this one. The score rises as the window fills, whether or not the server changes.

  • 21 Oct 26 +1

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

  • 19 Oct 26 +1

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

  • 17 Oct 26 +1

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

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 · Probed https://1211holding.com/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=mail.1211holding.com CN=YR1,O=Let's Encrypt,C=US 18 Sept 2026 17 Dec 2026 RSA 2048 SHA256-RSA 6c304089f961e5790117facc1b66d952a2c
SANs: 1211holding.com, mail.1211holding.com, www.1211holding.com
CN=YR1,O=Let's Encrypt,C=US (CA) CN=Root YR,O=ISRG,C=US 3 Sept 2025 2 Sept 2028 RSA 2048 SHA256-RSA a20253f15f2691c05dc1ce13b9bcca4e
CN=Root YR,O=ISRG,C=US (CA) CN=ISRG Root X1,O=Internet Security Research Group,C=US 13 May 2026 2 Sept 2032 RSA 4096 SHA256-RSA f24b6d17f9d9ad7cb1c9fea78782699f

Background: What to check on a remote MCP endpoint →

DNSSEC insecure

Validation of 1211holding.com. — Not signed

Zone DS Keys Algorithms Outcome
. trust_anchor 20326, 38696 8, 8 Verified
com. present 19718 13 Verified
1211holding.com. absent Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation
Authentication No authorisation required

The endpoint answered without asking for a token. Anyone who knows the URL can reach it.

Result No authorisation required
HTTP status 200
Header Value
strict-transport-security max-age=31536000; includeSubDomains; preload
content-security-policy frame-ancestors 'self'
x-content-type-options nosniff
x-frame-options SAMEORIGIN
referrer-policy strict-origin-when-cross-origin
permissions-policy interest-cohort=()

Background: How OAuth 2.1 works in the 2026 MCP spec →

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://1211holding.com/mcp Verified 200
http (plaintext) http://1211holding.com/mcp HTTPS enforced 301 https://1211holding.com/mcp
MCP tools · 5 exposed · ~805 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
check_art ~118

Fetches a picture from a public link, or takes an attached file, stores it for a design and reports its size in pixels and how big it prints well. PNG, JPG, WEBP, GIF, HEIC, PDF or SVG, up to 25 MB. Pictures that are never ordered are deleted after 30 days.

NameTypeReqDescription
fileobject–A file the person attached in the conversation, as an object with file_id and/or download_url.
image_urlstring–A public http(s) link to the picture.

No output schema declared.

No examples provided.

create_design ~467

Puts a picture (a public link, an upload id, an attached file or SVG markup) on an item and colour and returns the page where the person sees it, picks sizes and pays, with a picture of the result, how big each side prints, the price including US shipping, and any problems. With no picture, it returns the page where the person adds their own picture to the item. A shirt's front prints small on the left chest or big and centered; backs print large. No payment passes through this tool: the person pays on the returned page. Printing requires that the person owns the art or has permission to print it. Limit: 30 designs per address per hour.

NameTypeReqDescription
back_image_urlstring–A different picture for the back.
colorstring–One of the item's colours; left out, its default.
devstring–A developer's id, used with markup_usd.
fileobject–A file the person attached in the conversation, as an object with file_id and/or download_url.
frontstring–chest: small on the left chest (default). center: big and centered, on T-shirts, sweatshirts and hoodies.
image_urlstring–A public http(s) link to the picture.
itemstringyesThe item to print on.
markup_usdnumber–Dollars a developer adds to each item; the buyer sees the full price.
refstring–The name of the assistant or app, such as "claude".
sidestring–Where it prints (default front).
sizestring–A size to start with on the page, such as "L".
svgstring–SVG markup (lettering or simple shapes) with a viewBox; scripts and linked files are removed. Fonts available: Lato, DejaVu Sans, DejaVu Serif, Liberation Sans, Liberation Serif, Nimbus Sans, URW Got…
titlestring–A name for the design (80 characters).
uploadstring–An upload id, instead of image_url.

No output schema declared.

No examples provided.

get_design ~33

A saved design: its page link, pictures, print sizes and price.

NameTypeReqDescription
designstringyesThe design id.

No output schema declared.

No examples provided.

list_items ~63

Everything 1211 prints on: each item's colours, sizes, print sizes, the pixels a picture needs to print well, and its price including US shipping.

NameTypeReqDescription
itemstring–Optional: one item (for example "hoodie") to get just that one.

No output schema declared.

No examples provided.

report_problem ~124

Stores a report about something wrong with 1211's results (a picture refused that should have printed, a wrong price, a picture of the result that does not match, a link that does not open, a failed checkout, or a missing item) with the design it concerns and a short description. A person reads every report. Limit: 20 per address per hour.

NameTypeReqDescription
designstring–The design id, when it is about one design.
detailstring–What was wrong, in a sentence or two.
kindstringyes–

No output schema declared.

No examples provided.

Install

How do I install the 1211 - your picture on a shirt MCP server?

1211 - your picture on a shirt is a hosted endpoint at https://1211holding.com/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 · 1211holding.com

# add to Claude Code
claude mcp add --transport http com-1211holding-merch 'https://1211holding.com/mcp'
Common questions

What is the 1211 - your picture on a shirt MCP server?

1211 - your picture on a shirt is an MCP server listed in the public MCP registry as com.1211holding/merch. Put any picture on a shirt, hoodie, cap, tumbler or tote; get the link where the person buys it. This page covers its hosted endpoint (https://1211holding.com/mcp).

Is the 1211 - your picture on a shirt MCP server safe to use?

1211 - your picture on a shirt scores 86 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 1211 - your picture on a shirt MCP server expose?

1211 - your picture on a shirt exposes 5 tools: list_items, check_art, create_design, get_design, report_problem. Their descriptions and schemas cost roughly 805 tokens of context every time the server is loaded.

Does the 1211 - your picture on a shirt MCP server require authentication?

No. We connected to 1211 - your picture on a shirt without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

Is the 1211 - your picture on a shirt MCP server still maintained?

1211 - your picture on a shirt 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.