Designprint
REMOTE · THEDESIGNPRINT.COM
Print shop for AI agents: business cards, flyers, posters. Returns a proof, a price and a pay link.
Available components
Last scanned (22 hours ago)
Scores higher than 53% of remote servers
Reachable. Last reached 21 Nov 2026.
Category E-commerce
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
- 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. Nothing on it is marked destructive, but we can't show that an anonymous caller can only read: full credit needs the server to list at least one tool and every tool to be verifiably read-only. We use a best-effort check of tool names and descriptions to tell read-only tools from tools that change things, so some genuinely read-only tools may not get full credit. Names that start with a read verb (get, list, read, search and similar) and accurate readOnlyHint annotations help. Meet that to earn full credit, or require authorisation. See how to fix → View diagnostics → Partial
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
- 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 Usability34
- 0% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Fail
- AI-judged instruction clarity (good).Pass
- Context-footprint check failed: tool/resource definitions use about 3452 tokens (~493/item across 7 items; 6 tools + 1 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 Management20
- Stability observed for 6 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 6 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 7 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
- Supports UI / widget rendering.Pass
Checks we ran (14)
- TLS certificate
- Authorization
- HTTPS
- HSTS header
- DNSSEC
- Transport
- Schema quality
- Stability
- Tool coverage
- Injection markers
- Destructive annotations
- Judged manipulation
- MCP protocol
- Capabilities
Does not apply to this hosted endpoint (2)
- Supply Chain SecurityScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
- Provenance & TransparencyScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
The score does not measure everything. What the score does not measure →
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.
- 20 Nov 26 +1
- Tool “create_business_card” rewrote its description, which is the text the model reads security
- Tool “update_business_card” rewrote its description, which is the text the model reads security
- 18 Nov 26 +1
- Tool “show_card_designs” rewrote its description, which is the text the model reads security
- Tool “update_business_card” rewrote its description, which is the text the model reads security
- Schema quality: 426 → 491 ▼ functional
- “show_card_designs” added an optional parameter “look” cosmetic
- “show_card_designs” added an optional parameter “page” cosmetic
- “create_business_card” reworded the description of “style” cosmetic
- “update_business_card” reworded the description of “style” cosmetic
- 16 Nov 26 +1
- Stability: unverified → 0.03 ▲ functional
- 15 Nov 26 66
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 21 Nov 2026 · Probed https://thedesignprint.com/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=thedesignprint.com | CN=YE2,O=Let's Encrypt,C=US | 27 Oct 2026 | 25 Jan 2027 | ECDSA 256 | ECDSA-SHA384 | 5a0e1911b0d9f531422a4a268bdbe446178 |
| SANs: *.thedesignprint.com, thedesignprint.com | ||||||
| CN=YE2,O=Let's Encrypt,C=US (CA) | CN=Root YE,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | ECDSA 384 | ECDSA-SHA384 | 4df3b15dd6c0784c507cd37b58e6f115 |
| CN=Root YE,O=ISRG,C=US (CA) | CN=ISRG Root X2,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | ECDSA-SHA384 | 872165fc34b6e5fba8add5b3705fb53a |
| CN=ISRG Root X2,O=Internet Security Research Group,C=US (CA) | CN=ISRG Root X1,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | SHA256-RSA | 6c8f1dc727c7117f7baf853ac980f9cd |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of thedesignprint.com. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | Trust anchor | 20326, 38696 | 8, 8 | Verified |
| com. | DS published | 19718 | 13 | Verified |
| thedesignprint.com. | No DS | 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=63072000 |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://thedesignprint.com/mcp | Verified | 200 | |
| http (plaintext) | http://thedesignprint.com/mcp | HTTPS enforced | 308 | https://thedesignprint.com/mcp |
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_order Check whether an order was paid ~188
Check the state of an order from the link returned by create_business_card, update_business_card or print_design. Use it after the user says they have paid, or when they ask whether their order went through. The result's state is one of: none (the user has not started checkout), started (checkout was opened but nothing is paid yet), paid (paid and in production), refunded (paid and later refunded), canceled (canceled before it was paid), failed (the payment did not go through), or unknown (the link does not match any proof). The order is complete only when the state is paid. Once an order exists the result also gives statusUrl, the user's own page for following that order, which you can pass on to them.
| Name | Type | Req | Description |
|---|---|---|---|
| order | string | yes | The order link returned by create_business_card, update_business_card or print_design, or the id inside it. |
No output schema declared.
No examples provided.
create_business_card Design and print business cards ~859
Make print-ready business cards from a person's details and get a link to order them. Designprint fills one of its own card designs (front and back, 3.5 x 2 in). Before calling, ask the user for their name and how to reach them (phone, email or website); title, company, tagline, address and a logo are optional. Returns a preview of both sides, the price (with shipping options and an estimated total when you pass a quantity) and one link where the user approves the card, picks a quantity and pays as a guest (no account). Call it once per card. To change a detail, the design or the color afterwards, call update_business_card with the link: the card keeps its link. Calling create_business_card again makes a second card with a different link. The job is finished only when the user has paid: after they say they have, call check_order to confirm. Use this when the user has named a design or asked for one card. If they have not chosen a design, call show_card_designs instead: it shows every design with their details, to choose from.
| Name | Type | Req | Description |
|---|---|---|---|
| accent_color | string | – | Hex color that replaces the design's accent, e.g. '#0E7C66'. Use the brand color if the user has one. |
| address | string | – | Street address on one line. |
| channel | string | – | Where the request comes from, e.g. 'claude', 'chatgpt', 'cursor', 'terminal'. |
| company | string | – | Business or organization name. |
| string | – | Email address. | |
| logo_url | string | – | https link to a logo image (PNG, JPG or SVG). Shown on the back and small on the front. If it cannot be loaded the card is made without it and the warnings say so. |
| name | string | yes | Full name as it should appear on the card. |
| phone | string | – | Phone number, written the way it should print. |
| quantity | integer | – | How many cards the user wants, if they said. There is a minimum order; a smaller number is raised to the minimum and the change is reported in the warnings. With a quantity, the result also gives the… |
| style | string | – | Card design. Defaults to classic. The designs by look (a design can have two): minimal: classic, frame, line, soft, center, dots, badge, mono, grove, lagoon, summit, studio, sage, sprout; classic: cl… |
| tagline | string | – | Short line shown under the company name on the back of the card. |
| title | string | – | Job title or role, e.g. 'Owner'. |
| website | string | – | Website address. |
No output schema declared.
No examples provided.
get_business_card Look at a business card ~116
Look at a business card as it is right now: its details, both sides as pictures, a description of each side in words, whether it can still be changed, and its order link. Use it before answering a question about a card you made earlier, because the user can change the card themselves on the site before paying. It changes nothing. Pass the order link returned by create_business_card, or the id in it.
| Name | Type | Req | Description |
|---|---|---|---|
| order | string | yes | The order link returned by create_business_card, or the id inside it. |
No output schema declared.
No examples provided.
print_design Print & ship this design ~539
Print something the user already designed in this chat as a flat, single-sided print: a poster, flyer, sign, invitation, menu or similar. Send exactly one of design_html (the design as a complete HTML document) or image_url (a public link to an image); a call with neither is refused. Give the finished size with width_in and height_in, each from 1 to 60 inches. The design is printed edge to edge at exactly that size: no bleed or margin is added, so author it at the true print size and keep text away from the edges. Only the first page is printed, and anything that does not fit on it is left off. An image is fitted inside the size without stretching or cropping, and any space left over stays white. If the size is left out, an image is sized from its pixels at 300 per inch and HTML is sized from how it lays out in a desktop browser window (at least 13.3 x 7.5 in), so always give the size for HTML. It is priced by printed area. The result states the size it will print at, the price per print at that size, a link to a preview image and one order link; on the order page the user picks a quantity and shipping, sees the final amount and pays as a guest (no account). Nothing is printed until they pay: after they say they have, call check_order to confirm. For business cards made from a person's name and contact details use create_business_card instead, which also prints both sides.
| Name | Type | Req | Description |
|---|---|---|---|
| channel | string | – | Where the request comes from, e.g. 'claude', 'chatgpt', 'cursor'. Defaults to 'claude'. |
| design_html | string | – | The design as one complete HTML document, with its styles inside it. Send this or image_url, not both. Fonts and images it links to must be public web addresses; they are loaded when the proof is mad… |
| height_in | number | – | Finished height in inches, 1 to 60. Give it together with width_in. |
| image_url | string | – | Public web address of the image to print (PNG, JPG, WebP or SVG), when there is no HTML. |
| title | string | – | A short name for the order, shown on the order page, e.g. 'Baby shower invite'. |
| width_in | number | – | Finished width in inches, 1 to 60. Give it together with height_in. A value outside the range is moved to the nearest limit and the result says so. |
No output schema declared.
No examples provided.
show_card_designs Show business card designs to choose from ~783
Show the user Designprint business card designs with their own details on them, so they can choose by looking. Use this first whenever the user asks for business cards and has not chosen a design. Ask for missing details beforehand only if you do not have their name; every other field is optional. It makes one real card per design, a set of designs at a time (front and back, 3.5 x 2 in): pass look to show only designs of one look, and page 2, 3 and so on for the next sets. It returns, for each design, its name, a one-line description, the front and back pictures and its own order link, plus a page that shows all of them and the same gallery as one self-contained HTML document. Present the result as a scrollable gallery: where the in-chat gallery is showing, point the user to it; if you can show HTML (an artifact), show the gallery document as it is; otherwise list every design with its own link and give the gallery page. Never join the designs into one picture and do not choose for the user. Then ask the user which design they like, by its name. Every change after that goes on the chosen design only, with update_business_card and that design's link; do not call show_card_designs again to add or change a detail. Once they choose, and after every change, end with "Want to change anything, or print it?"; when they say print, give that design's link: it opens the checkout page with that design, where they pick a quantity and pay as a guest. Use check_order to confirm the payment. The result also carries one link to a page with every design and the user's details already on each: give it to a user who wants to browse them all. If the user already named a design, use create_business_card instead.
| Name | Type | Req | Description |
|---|---|---|---|
| accent_color | string | – | Hex color that replaces the design's accent, e.g. '#0E7C66'. Use the brand color if the user has one. |
| address | string | – | Street address on one line. |
| channel | string | – | Where the request comes from, e.g. 'claude', 'chatgpt', 'cursor', 'terminal'. |
| company | string | – | Business or organization name. |
| string | – | Email address. | |
| logo_url | string | – | https link to a logo image (PNG, JPG or SVG). Shown on the back and small on the front. If it cannot be loaded the card is made without it and the warnings say so. |
| look | string | – | Show only designs of one look: minimal, classic, elegant, modern, bold, friendly, dark, technical. Use it when the user has said what they are after ("something dark", "keep it minimal"). Leave it ou… |
| name | string | yes | Full name as it should appear on the card. |
| page | integer | – | Which set of designs to show. 1 (the default) is the first set; pass 2, then 3 and so on when the user wants to see more. |
| phone | string | – | Phone number, written the way it should print. |
| quantity | integer | – | How many cards the user wants, if they said. There is a minimum order; a smaller number is raised to the minimum and the change is reported in the warnings. With a quantity, the result also gives the… |
| tagline | string | – | Short line shown under the company name on the back of the card. |
| title | string | – | Job title or role, e.g. 'Owner'. |
| website | string | – | Website address. |
No output schema declared.
No examples provided.
update_business_card Change a business card ~958
Change a business card that create_business_card already made: a detail, the design, the color or the quantity. Pass the order link (or the id in it) as order, plus only the fields that change. A field you leave out keeps its current value; a field sent as an empty string is taken off the card, and can be put back with another update. Nothing is deleted: every change can be undone the same way. The card keeps the same order link, so the user does not need a new one. Returns the new preview of both sides, the price and the same link, exactly like create_business_card. It works until the card is paid for; after that the card is fixed, and a different card needs a new create_business_card call. Use this for every change the user asks for after the first proof, and after they chose a design from show_card_designs. End each reply with "Want to change anything, or print it?", and give the link when they say print.
| Name | Type | Req | Description |
|---|---|---|---|
| accent_color | string | – | New hex accent color, e.g. '#0E7C66'. Leave it out to keep the current one; send an empty string to go back to the design's own color. |
| address | string | – | New address. Leave it out to keep the current one; send an empty string to take it off the card. |
| company | string | – | New company name. Leave it out to keep the current one; send an empty string to take it off the card. |
| string | – | New email address. Leave it out to keep the current one; send an empty string to take it off the card. | |
| logo_url | string | – | New https link to a logo image. Leave it out to keep the current one; send an empty string to remove the logo. |
| name | string | – | New name. Leave it out to keep the current one. |
| order | string | yes | The order link returned by create_business_card, or the id inside it. |
| phone | string | – | New phone number. Leave it out to keep the current one; send an empty string to take it off the card. |
| quantity | integer | – | New quantity. Leave it out to keep the one already asked for. How many cards the user wants, if they said. There is a minimum order; a smaller number is raised to the minimum and the change is report… |
| style | string | – | New card design. Leave it out to keep the current one. The designs by look (a design can have two): minimal: classic, frame, line, soft, center, dots, badge, mono, grove, lagoon, summit, studio, sage… |
| tagline | string | – | New line for the back of the card. Leave it out to keep the current one; send an empty string to take it off. |
| title | string | – | New job title. Leave it out to keep the current one; send an empty string to take it off the card. |
| website | string | – | New website. Leave it out to keep the current one; send an empty string to take it off the card. |
No output schema declared.
No examples provided.
How do I install the Designprint MCP server?
Designprint is a hosted endpoint at https://thedesignprint.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 · thedesignprint.com
claude mcp add --transport http com-thedesignprint-designprint 'https://thedesignprint.com/mcp'
What is the Designprint MCP server?
Designprint is an MCP server listed in the public MCP registry as com.thedesignprint/designprint. Print shop for AI agents: business cards, flyers, posters. Returns a proof, a price and a pay link. This page covers its hosted endpoint (https://thedesignprint.com/mcp).
Is the Designprint MCP server safe to use?
Designprint scores 69 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 Designprint MCP server expose?
Designprint exposes 6 tools: print_design, create_business_card, update_business_card, get_business_card, show_card_designs, check_order. Their descriptions and schemas cost roughly 3,443 tokens of context every time the server is loaded.
Does the Designprint MCP server require authentication?
No. We connected to Designprint without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the Designprint MCP server still maintained?
Designprint is still listed as active in the MCP registry. We last reached this channel on 21 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.
What did VerifyMCP test on the Designprint MCP server?
VerifyMCP ran 14 checks on Designprint, covering TLS certificate, Authorization, HTTPS, HSTS header and 10 more. Supply Chain Security and Provenance & Transparency do not apply to a hosted endpoint, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.