PrintSanity
REMOTE · PRINTSANITY.COM
Checks AI-made flyers, cards and posters will print right. Fixes proportions and broken QR codes.
Available components
Last scanned (15 hours ago)
Scores higher than 60% of remote servers
Reachable. Last reached 23 Oct 2026.
Category Design and Media
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 Security63
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- No authorisation is required to call this server. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one. See how to fix → View diagnostics → Partial
- HTTPS enforcement could not be verified: the plaintext port answered with HTTP 406, which proves neither a plaintext path nor enforcement. View diagnostics → Unverified
- HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability66
- AI-judged instruction clarity (good).Pass
- Context-footprint check failed: tool/resource definitions use about 721 tokens (~180/item across 4 items; 4 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 Management53
- Stability observed for 16 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage71
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 0% of tool parameters carry a description.Fail
- Structured output schemas are declared (25% of tools); any adoption earns full credit.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 4 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 5 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a current MCP spec version (2026-07-28).Pass
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.
- 22 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.
- 20 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 40 to 43. That category is still filling its 30-day observation window: 12 days of observed history at the previous scan, 13 at this one. The score rises as the window fills, whether or not the server changes.
- 18 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 33 to 37. That category is still filling its 30-day observation window: 10 days of observed history at the previous scan, 11 at this one. The score rises as the window fills, whether or not the server changes.
- 15 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.
- 13 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.
- 12 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 10 to 17. That category is still filling its 30-day observation window: 3 days of observed history at the previous scan, 5 at this one. The score rises as the window fills, whether or not the server changes.
- 10 Oct 26 +1
- Stability: unverified → 0.10 ▲ functional
- 7 Oct 26 63
First indexed and scored.
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 23 Oct 2026 · Probed https://printsanity.com/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=printsanity.com | CN=WE1,O=Google Trust Services,C=US | 18 Sept 2026 | 17 Dec 2026 | ECDSA 256 | ECDSA-SHA256 | 90c4cfdb48b5cc6e131a4de351449a3b |
| SANs: printsanity.com, www.printsanity.com, *.www.printsanity.com | ||||||
| CN=WE1,O=Google Trust Services,C=US (CA) | CN=GTS Root R4,O=Google Trust Services LLC,C=US | 13 Dec 2023 | 20 Feb 2029 | ECDSA 256 | ECDSA-SHA384 | 7ff31977972c224a76155d13b6d685e3 |
| CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) | CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE | 15 Nov 2023 | 28 Jan 2028 | ECDSA 384 | SHA256-RSA | 7fe530bf331343bedd821610493d8a1b |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of printsanity.com. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| com. | present | 19718 | 13 | Verified |
| printsanity.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 |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://printsanity.com/mcp | Verified | 200 | |
| http (plaintext) | http://printsanity.com/mcp | Inconclusive | 406 |
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 →
check_print_file Check a file will print ~101
Check whether artwork will print correctly at the given size. Give the artwork as file_url (public https link) or file_base64. `size` is required for images. Returns the verdict, what is wrong, whether repair reaches a printable file, and the prompt to regenerate with when it cannot.
| Name | Type | Req | Description |
|---|---|---|---|
| expect_qr | – | – | – |
| file_base64 | – | – | – |
| file_url | – | – | – |
| filename | – | – | – |
| size | – | – | – |
No output schema declared.
No examples provided.
fix_print_file Fix a file for printing ~214
Repair what can be repaired and return download links for the print-ready file. Rebuilds QR codes so they scan, fixes proportions by adding paper rather than cropping, and returns a PDF the size of the paper (inside a border a home printer can reach, where the paper is one a home printer takes) plus a PNG and, where it differs, an edge-to-edge PDF for print shops. For small pieces such as business cards and invitations it also returns letter and A4 sheets with several copies and cut marks. Links last 30 minutes. Resolution is never faked: when that is the problem the result carries the prompt to regenerate with. `qr_url` is the link a QR code should carry when the one on the artwork was drawn by an image model and decodes to nothing.
| Name | Type | Req | Description |
|---|---|---|---|
| enlarge_qr | boolean | – | – |
| file_base64 | – | – | – |
| file_url | – | – | – |
| filename | – | – | – |
| qr_url | – | – | – |
| size | – | – | – |
No output schema declared.
No examples provided.
list_print_sizes List print sizes ~22
The named print sizes `size` accepts, with their dimensions.
Input schema present but exposes no named parameters.
| Name | Type | Req | Description |
|---|---|---|---|
| result | array | yes | – |
No examples provided.
plan_artwork Plan artwork for a print size ~76
What to ask an image model for, before generating artwork for this print size. Returns the pixel dimensions to generate at, the floor below which it will look soft, the proportions, the smallest QR code that scans from where this piece is read, and a line to paste into the image prompt.
| Name | Type | Req | Description |
|---|---|---|---|
| size | string | yes | – |
No output schema declared.
No examples provided.
How do I install the PrintSanity MCP server?
PrintSanity is a hosted endpoint at https://printsanity.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 · printsanity.com
claude mcp add --transport http chartsmartdev-printsanity 'https://printsanity.com/mcp'
What is the PrintSanity MCP server?
PrintSanity is an MCP server listed in the public MCP registry as io.github.chartsmartdev/printsanity. Checks AI-made flyers, cards and posters will print right. Fixes proportions and broken QR codes. This page covers its hosted endpoint (https://printsanity.com/mcp).
Is the PrintSanity MCP server safe to use?
PrintSanity scores 70 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 PrintSanity MCP server expose?
PrintSanity exposes 4 tools: list_print_sizes, plan_artwork, check_print_file, fix_print_file. Their descriptions and schemas cost roughly 413 tokens of context every time the server is loaded.
Does the PrintSanity MCP server require authentication?
No. We connected to PrintSanity without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the PrintSanity MCP server still maintained?
PrintSanity is still listed as active in the MCP registry. We last reached this channel on 23 October 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.