# RushOrderTees (remote · mcp.rushordertees.com) Custom t-shirts and apparel, printed and shipped in the US on your deadline. - Trust score: 77/100 (medium) - Change this week: +3 - Registry status: active - Liveness: live - Owner verified: no - Last scored: 2026-11-06 ## Components - remote · `mcp.rushordertees.com`: 77/100 (this document), [markdown](https://verifymcp.io/servers/com-rushordertees-rushordertees/mcp-print.md), [page](https://verifymcp.io/servers/com-rushordertees-rushordertees/mcp-print) ## Channel facts - Endpoint: `https://mcp.rushordertees.com/mcp/print` - Transports: `streamable-http` - Auth: `none` - Version: `0.40.7` ## Trust breakdown 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. 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-06. - **Endpoint Security**: 74/100 - The endpoint's TLS certificate is valid, in date, and uses a strong key. - 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. - HTTPS is enforced; there's no plaintext access path. - HSTS check failed: the Strict-Transport-Security header is absent. - DNSSEC check failed: this domain isn't protected by DNSSEC. - **Transport & Reachability**: 100/100 - Verified streamable-http transport via a live MCP handshake. - **Schema Quality & AI Usability**: 79/100 - 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name). - AI-judged instruction clarity (excellent). - Context-footprint check failed: tool/resource definitions use about 3256 tokens (~217/item across 15 items; 12 tools + 3 resources), over budget; trim descriptions and params. - 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**: 100/100 - 100% of tools have a non-trivial description (not blank, and not just the tool's name). - 100% of tool parameters carry a description. - Structured output schemas are declared (100% of tools); any adoption earns full credit. - **Tool Safety**: 100/100 - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured. - We read all 12 captured tool definition(s), and no name or description among them implies an irreversible operation. - An AI judge read all 14 captured unit(s) of tool text and found none that tries to manipulate the model reading it. - **Capabilities**: 100/100 - Implements a current MCP spec version (2026-07-28). - Supports UI / widget rendering. ## Install ### How do I install the RushOrderTees MCP server? RushOrderTees is a hosted endpoint at https://mcp.rushordertees.com/mcp/print, 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. ### Claude ```bash claude mcp add --transport http com-rushordertees-rushordertees 'https://mcp.rushordertees.com/mcp/print' ``` ### Cursor ```json { "mcpServers": { "com-rushordertees-rushordertees": { "url": "https://mcp.rushordertees.com/mcp/print" } } } ``` ### VS Code ```json { "servers": { "com-rushordertees-rushordertees": { "type": "http", "url": "https://mcp.rushordertees.com/mcp/print" } } } ``` ### Codex ```toml [mcp_servers.com-rushordertees-rushordertees] url = "https://mcp.rushordertees.com/mcp/print" ``` ### opencode ```json { "$schema": "https://opencode.ai/config.json", "mcp": { "com-rushordertees-rushordertees": { "type": "remote", "url": "https://mcp.rushordertees.com/mcp/print", "enabled": true } } } ``` ### OpenClaw ```bash openclaw mcp add com-rushordertees-rushordertees --url 'https://mcp.rushordertees.com/mcp/print' --transport streamable-http ``` ### Hermes ```yaml mcp_servers: com-rushordertees-rushordertees: url: "https://mcp.rushordertees.com/mcp/print" ``` ### Netclaw ```json { "McpServers": { "com-rushordertees-rushordertees": { "Transport": "http", "Url": "https://mcp.rushordertees.com/mcp/print" } } } ``` ### Vellum ```bash assistant mcp add com-rushordertees-rushordertees -t streamable-http -u 'https://mcp.rushordertees.com/mcp/print' ``` ### Other ```json { "mcpServers": { "com-rushordertees-rushordertees": { "type": "http", "url": "https://mcp.rushordertees.com/mcp/print" } } } ``` The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs. ## 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-06 (score 77, +1) - [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server ### 2026-11-05 (score 76, 0) - [security] The server rewrote its instructions, which are the text every model session reads - [security] Tool “choose_option” rewrote its description, which is the text the model reads - [security] Tool “get_options” rewrote its description, which is the text the model reads - [functional] Server version: 0.43.0 → 0.46.0 ### 2026-11-03 (score 76, +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-11-01 (score 75, +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-30 (score 74, +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-29 (score 73, 0) - [functional] Server version: 0.42.0 → 0.43.0 ### 2026-10-28 (score 73, +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-27 (score 72, 0) - [functional improvement] Stability: unverified → 0.03 - [functional] Server version: 0.41.0 → 0.42.0 ## MCP tools (12) ### `start_print_order` (~139 tokens) Start a print order Opens a print order. Use it when the customer wants a design printed on a garment. Call it before asking your own questions: our first reply asks for the design and the garment in words written for the customer. Pass what they have said about the order in context — a phrase or a paragraph is fine. Returns the order_id to use with every other tool, what is still needed, and the next question to ask. Input parameters: - `context` (string): What the customer has said so far, in their own words. Unstructured prose is fine; we parse it and ask for the rest one question at a time. Leave empty to start blank. Output parameters: - `alternatives` (array|null): Present from the moment several styles fit until the customer picks, beside whatever ask_next asks: show all of them with their summaries, prices and minimums, say the one marked is_provisional is wh… - `artwork` (object|null) - `artwork_upload_url` (string|null): Present until the design is accepted. Show it to the customer as one link labeled "Upload your design", not as a bare address: they drop their design file on that page and it is checked there. You ca… - `ask_next` (string|null): Ask the customer this, in your own words, and send the answer to describe_order. - `checkout_url` (string|null): Show it to the customer as one link labeled "Pay and enter shipping", not as a bare address: they see the artwork and total, confirm their email with a code we send them, then pay and enter their add… - `choices` (array|null): Answers the customer can pick from, one set per field ask_next asks about. Offer them as selectable options where your client can, otherwise as a short list. They are suggestions: colors are families… - `chosen_option` (object|null) - `expires_at` (string|null): When an unsaved order expires; null once it is saved to an account or paid. - `garment` (object|null): The garment on the order, and what mockup_url shows. Name it when you show the picture; when it is provisional, say so. - `mockup_url` (string|null): The garment on the order, in the customer's color, with their design on it once we have it. An image address: show it as a picture where your client can, never as text or as a link, and never describ… - `mockup_views` (array|null): Every side of the garment, the printed one first: mockup_url with the design, then the other sides plain. Where your client can show pictures, show them all, so the customer sees which sides stay bla… - `next_call` (string): What to call next, and why. - `notes` (array): Relay these to the customer. - `options` (array|null) - `order_id` (string) - `saved` (boolean): Whether the order is saved to a customer account (save_progress). - `spec` (object): The print as the customer has described it so far, beside garment. Null where they have not said; still_needed lists what is missing. - `status` (string) - `still_needed` (array): Fields the customer has not told us yet, and any go-ahead we are waiting on for something the order cannot carry. ### `describe_order` (~217 tokens) Describe the order Records more about what the customer wants — an answer to ask_next, a correction, or a whole paragraph — and reports what is still needed. Call it each time the customer gives a new detail. In clients that render our order card the customer sees the order so far and the question in ask_next with its choices as buttons; when several styles fit it shows them too. An answer or a pick made there arrives as a message; the question in ask_next is for the customer whether or not the card shows. Also records a decision about the order: a stop, an objection to the price or the date, or a request we do not offer. It belongs to the order's record, and the reply says what the order still needs. Input parameters: - `context` (string, required): What the customer said, in their own words. Garment, color, size, quantity, print width in inches, placement, deadline — whatever is new. Unstructured prose is fine. - `order_id` (string, required): The order_id returned by start_print_order. Output parameters: - `alternatives` (array|null): Present from the moment several styles fit until the customer picks, beside whatever ask_next asks: show all of them with their summaries, prices and minimums, say the one marked is_provisional is wh… - `artwork` (object|null) - `artwork_upload_url` (string|null): Present until the design is accepted. Show it to the customer as one link labeled "Upload your design", not as a bare address: they drop their design file on that page and it is checked there. You ca… - `ask_next` (string|null): Ask the customer this, in your own words, and send the answer to describe_order. - `checkout_url` (string|null): Show it to the customer as one link labeled "Pay and enter shipping", not as a bare address: they see the artwork and total, confirm their email with a code we send them, then pay and enter their add… - `choices` (array|null): Answers the customer can pick from, one set per field ask_next asks about. Offer them as selectable options where your client can, otherwise as a short list. They are suggestions: colors are families… - `chosen_option` (object|null) - `expires_at` (string|null): When an unsaved order expires; null once it is saved to an account or paid. - `garment` (object|null): The garment on the order, and what mockup_url shows. Name it when you show the picture; when it is provisional, say so. - `mockup_url` (string|null): The garment on the order, in the customer's color, with their design on it once we have it. An image address: show it as a picture where your client can, never as text or as a link, and never describ… - `mockup_views` (array|null): Every side of the garment, the printed one first: mockup_url with the design, then the other sides plain. Where your client can show pictures, show them all, so the customer sees which sides stay bla… - `next_call` (string): What to call next, and why. - `notes` (array): Relay these to the customer. - `options` (array|null) - `order_id` (string) - `saved` (boolean): Whether the order is saved to a customer account (save_progress). - `spec` (object): The print as the customer has described it so far, beside garment. Null where they have not said; still_needed lists what is missing. - `status` (string) - `still_needed` (array): Fields the customer has not told us yet, and any go-ahead we are waiting on for something the order cannot carry. ### `pick_choice` (~111 tokens) Pick a choice Lands one of the choices the last reply offered beside ask_next, by field and option, exactly as shown. Use it when the customer picks one of them; an answer in their own words goes to describe_order instead. Input parameters: - `field` (string, required): The field of the choices set the customer answered, as the last reply named it. - `option` (string, required): The option the customer picked, exactly as the last reply listed it. - `order_id` (string, required): The order_id returned by start_print_order. Output parameters: - `alternatives` (array|null): Present from the moment several styles fit until the customer picks, beside whatever ask_next asks: show all of them with their summaries, prices and minimums, say the one marked is_provisional is wh… - `artwork` (object|null) - `artwork_upload_url` (string|null): Present until the design is accepted. Show it to the customer as one link labeled "Upload your design", not as a bare address: they drop their design file on that page and it is checked there. You ca… - `ask_next` (string|null): Ask the customer this, in your own words, and send the answer to describe_order. - `checkout_url` (string|null): Show it to the customer as one link labeled "Pay and enter shipping", not as a bare address: they see the artwork and total, confirm their email with a code we send them, then pay and enter their add… - `choices` (array|null): Answers the customer can pick from, one set per field ask_next asks about. Offer them as selectable options where your client can, otherwise as a short list. They are suggestions: colors are families… - `chosen_option` (object|null) - `expires_at` (string|null): When an unsaved order expires; null once it is saved to an account or paid. - `garment` (object|null): The garment on the order, and what mockup_url shows. Name it when you show the picture; when it is provisional, say so. - `mockup_url` (string|null): The garment on the order, in the customer's color, with their design on it once we have it. An image address: show it as a picture where your client can, never as text or as a link, and never describ… - `mockup_views` (array|null): Every side of the garment, the printed one first: mockup_url with the design, then the other sides plain. Where your client can show pictures, show them all, so the customer sees which sides stay bla… - `next_call` (string): What to call next, and why. - `notes` (array): Relay these to the customer. - `options` (array|null) - `order_id` (string) - `saved` (boolean): Whether the order is saved to a customer account (save_progress). - `spec` (object): The print as the customer has described it so far, beside garment. Null where they have not said; still_needed lists what is missing. - `status` (string) - `still_needed` (array): Fields the customer has not told us yet, and any go-ahead we are waiting on for something the order cannot carry. ### `choose_style` (~170 tokens) Choose a garment Lands the order on one of the alternatives describe_order offered, by id, or on the style already chosen. Use it when the customer picks one of them; a pick in their own words can still go to describe_order. Pass color when they picked a picture from preview_colors or want the style in another shade: the style lands in that shade in one call. Input parameters: - `color` (string): The shade to land the style in, when the customer picked a picture from preview_colors or wants this style in another color. Left out, the order keeps its color. - `order_id` (string, required): The order_id returned by start_print_order. - `style_id` (string, required): The id of the alternative the customer chose, exactly as returned by describe_order, or the style_id of a preview_colors picture. Output parameters: - `alternatives` (array|null): Present from the moment several styles fit until the customer picks, beside whatever ask_next asks: show all of them with their summaries, prices and minimums, say the one marked is_provisional is wh… - `artwork` (object|null) - `artwork_upload_url` (string|null): Present until the design is accepted. Show it to the customer as one link labeled "Upload your design", not as a bare address: they drop their design file on that page and it is checked there. You ca… - `ask_next` (string|null): Ask the customer this, in your own words, and send the answer to describe_order. - `checkout_url` (string|null): Show it to the customer as one link labeled "Pay and enter shipping", not as a bare address: they see the artwork and total, confirm their email with a code we send them, then pay and enter their add… - `choices` (array|null): Answers the customer can pick from, one set per field ask_next asks about. Offer them as selectable options where your client can, otherwise as a short list. They are suggestions: colors are families… - `chosen_option` (object|null) - `expires_at` (string|null): When an unsaved order expires; null once it is saved to an account or paid. - `garment` (object|null): The garment on the order, and what mockup_url shows. Name it when you show the picture; when it is provisional, say so. - `mockup_url` (string|null): The garment on the order, in the customer's color, with their design on it once we have it. An image address: show it as a picture where your client can, never as text or as a link, and never describ… - `mockup_views` (array|null): Every side of the garment, the printed one first: mockup_url with the design, then the other sides plain. Where your client can show pictures, show them all, so the customer sees which sides stay bla… - `next_call` (string): What to call next, and why. - `notes` (array): Relay these to the customer. - `options` (array|null) - `order_id` (string) - `saved` (boolean): Whether the order is saved to a customer account (save_progress). - `spec` (object): The print as the customer has described it so far, beside garment. Null where they have not said; still_needed lists what is missing. - `status` (string) - `still_needed` (array): Fields the customer has not told us yet, and any go-ahead we are waiting on for something the order cannot carry. ### `preview_colors` (~172 tokens) Preview colors Shows the customer's design on the garment in other colors without changing the order: one picture per offered style per color named, up to four colors. Use it when the customer wants to compare colors or see one before deciding; `describe_order` with a new color changes the order, this compares without changing anything. In clients that render our color preview the customer can pick a picture there and their pick arrives as a message; otherwise, when they pick, call choose_style with the style_id and color. Input parameters: - `colors` (array): The colors to show, in the customer's words, one to 4 (e.g. ["natural", "heather navy"]). Left out, we show the shades the design suits among the styles on offer. - `order_id` (string, required): The order_id returned by start_print_order. Output parameters: - `alternatives` (array|null): Present from the moment several styles fit until the customer picks, beside whatever ask_next asks: show all of them with their summaries, prices and minimums, say the one marked is_provisional is wh… - `artwork` (object|null) - `artwork_upload_url` (string|null): Present until the design is accepted. Show it to the customer as one link labeled "Upload your design", not as a bare address: they drop their design file on that page and it is checked there. You ca… - `ask_next` (string|null): Ask the customer this, in your own words, and send the answer to describe_order. - `checkout_url` (string|null): Show it to the customer as one link labeled "Pay and enter shipping", not as a bare address: they see the artwork and total, confirm their email with a code we send them, then pay and enter their add… - `choices` (array|null): Answers the customer can pick from, one set per field ask_next asks about. Offer them as selectable options where your client can, otherwise as a short list. They are suggestions: colors are families… - `chosen_option` (object|null) - `color_previews` (array): One entry per offered style, each with a picture per color. Nothing on the order changed. - `expires_at` (string|null): When an unsaved order expires; null once it is saved to an account or paid. - `garment` (object|null): The garment on the order, and what mockup_url shows. Name it when you show the picture; when it is provisional, say so. - `mockup_url` (string|null): The garment on the order, in the customer's color, with their design on it once we have it. An image address: show it as a picture where your client can, never as text or as a link, and never describ… - `mockup_views` (array|null): Every side of the garment, the printed one first: mockup_url with the design, then the other sides plain. Where your client can show pictures, show them all, so the customer sees which sides stay bla… - `next_call` (string): What to call next, and why. - `notes` (array): Relay these to the customer. - `options` (array|null) - `order_id` (string) - `saved` (boolean): Whether the order is saved to a customer account (save_progress). - `spec` (object): The print as the customer has described it so far, beside garment. Null where they have not said; still_needed lists what is missing. - `status` (string) - `still_needed` (array): Fields the customer has not told us yet, and any go-ahead we are waiting on for something the order cannot carry. ### `submit_artwork` (~225 tokens) Send the design Sends the design to be printed when you already hold a public https link to the original file; never ask the customer for one, they upload through the artwork_upload_url from any reply. We check whether it will print well at the requested size and answer in inches, with what to fix if anything. A design you only saw in the chat is not one you hold: never transcribe, redraw or regenerate it; give the customer the artwork_upload_url instead. Artwork can be replaced later. Input parameters: - `filename` (string): The original file name, if known. - `image_base64` (string): The bytes of a file dropped on our order card, sent by the card itself (PNG, JPEG or WebP, no data: prefix). Not for a file the customer put in the chat; they upload through artwork_upload_url. - `image_url` (string): A public https link to the image (PNG, JPEG or WebP) that you already hold; it survives a new conversation. - `order_id` (string, required): The order_id returned by start_print_order. Output parameters: - `alternatives` (array|null): Present from the moment several styles fit until the customer picks, beside whatever ask_next asks: show all of them with their summaries, prices and minimums, say the one marked is_provisional is wh… - `artwork` (object|null) - `artwork_upload_url` (string|null): Present until the design is accepted. Show it to the customer as one link labeled "Upload your design", not as a bare address: they drop their design file on that page and it is checked there. You ca… - `ask_next` (string|null): Ask the customer this, in your own words, and send the answer to describe_order. - `checkout_url` (string|null): Show it to the customer as one link labeled "Pay and enter shipping", not as a bare address: they see the artwork and total, confirm their email with a code we send them, then pay and enter their add… - `choices` (array|null): Answers the customer can pick from, one set per field ask_next asks about. Offer them as selectable options where your client can, otherwise as a short list. They are suggestions: colors are families… - `chosen_option` (object|null) - `expires_at` (string|null): When an unsaved order expires; null once it is saved to an account or paid. - `garment` (object|null): The garment on the order, and what mockup_url shows. Name it when you show the picture; when it is provisional, say so. - `mockup_url` (string|null): The garment on the order, in the customer's color, with their design on it once we have it. An image address: show it as a picture where your client can, never as text or as a link, and never describ… - `mockup_views` (array|null): Every side of the garment, the printed one first: mockup_url with the design, then the other sides plain. Where your client can show pictures, show them all, so the customer sees which sides stay bla… - `next_call` (string): What to call next, and why. - `notes` (array): Relay these to the customer. - `options` (array|null) - `order_id` (string) - `saved` (boolean): Whether the order is saved to a customer account (save_progress). - `spec` (object): The print as the customer has described it so far, beside garment. Null where they have not said; still_needed lists what is missing. - `status` (string) - `still_needed` (array): Fields the customer has not told us yet, and any go-ahead we are waiting on for something the order cannot carry. ### `get_options` (~110 tokens) Get priced options Returns priced options with delivery dates once the order is fully described and the artwork has passed the print check. Present them to the customer; each has an id for choose_option. In clients that render our option picker the customer can pick there, and you will see the choice as a message. Call it again whenever the customer asks to see or reconsider the options; it costs nothing. Prices come from us and cannot be passed in. Input parameters: - `order_id` (string, required): The order_id returned by start_print_order. Output parameters: - `alternatives` (array|null): Present from the moment several styles fit until the customer picks, beside whatever ask_next asks: show all of them with their summaries, prices and minimums, say the one marked is_provisional is wh… - `artwork` (object|null) - `artwork_upload_url` (string|null): Present until the design is accepted. Show it to the customer as one link labeled "Upload your design", not as a bare address: they drop their design file on that page and it is checked there. You ca… - `ask_next` (string|null): Ask the customer this, in your own words, and send the answer to describe_order. - `checkout_url` (string|null): Show it to the customer as one link labeled "Pay and enter shipping", not as a bare address: they see the artwork and total, confirm their email with a code we send them, then pay and enter their add… - `choices` (array|null): Answers the customer can pick from, one set per field ask_next asks about. Offer them as selectable options where your client can, otherwise as a short list. They are suggestions: colors are families… - `chosen_option` (object|null) - `expires_at` (string|null): When an unsaved order expires; null once it is saved to an account or paid. - `garment` (object|null): The garment on the order, and what mockup_url shows. Name it when you show the picture; when it is provisional, say so. - `mockup_url` (string|null): The garment on the order, in the customer's color, with their design on it once we have it. An image address: show it as a picture where your client can, never as text or as a link, and never describ… - `mockup_views` (array|null): Every side of the garment, the printed one first: mockup_url with the design, then the other sides plain. Where your client can show pictures, show them all, so the customer sees which sides stay bla… - `next_call` (string): What to call next, and why. - `notes` (array): Relay these to the customer. - `options` (array|null) - `order_id` (string) - `saved` (boolean): Whether the order is saved to a customer account (save_progress). - `spec` (object): The print as the customer has described it so far, beside garment. Null where they have not said; still_needed lists what is missing. - `status` (string) - `still_needed` (array): Fields the customer has not told us yet, and any go-ahead we are waiting on for something the order cannot carry. ### `choose_option` (~91 tokens) Choose an option Locks in the option the customer picked from get_options, and its price. Pass the option id exactly as returned. There is no way to pass a price. Free or rush delivery is chosen at checkout, not here. Input parameters: - `option_id` (string, required): The id of the option the customer chose, exactly as returned by get_options. - `order_id` (string, required): The order_id returned by start_print_order. Output parameters: - `alternatives` (array|null): Present from the moment several styles fit until the customer picks, beside whatever ask_next asks: show all of them with their summaries, prices and minimums, say the one marked is_provisional is wh… - `artwork` (object|null) - `artwork_upload_url` (string|null): Present until the design is accepted. Show it to the customer as one link labeled "Upload your design", not as a bare address: they drop their design file on that page and it is checked there. You ca… - `ask_next` (string|null): Ask the customer this, in your own words, and send the answer to describe_order. - `checkout_url` (string|null): Show it to the customer as one link labeled "Pay and enter shipping", not as a bare address: they see the artwork and total, confirm their email with a code we send them, then pay and enter their add… - `choices` (array|null): Answers the customer can pick from, one set per field ask_next asks about. Offer them as selectable options where your client can, otherwise as a short list. They are suggestions: colors are families… - `chosen_option` (object|null) - `expires_at` (string|null): When an unsaved order expires; null once it is saved to an account or paid. - `garment` (object|null): The garment on the order, and what mockup_url shows. Name it when you show the picture; when it is provisional, say so. - `mockup_url` (string|null): The garment on the order, in the customer's color, with their design on it once we have it. An image address: show it as a picture where your client can, never as text or as a link, and never describ… - `mockup_views` (array|null): Every side of the garment, the printed one first: mockup_url with the design, then the other sides plain. Where your client can show pictures, show them all, so the customer sees which sides stay bla… - `next_call` (string): What to call next, and why. - `notes` (array): Relay these to the customer. - `options` (array|null) - `order_id` (string) - `saved` (boolean): Whether the order is saved to a customer account (save_progress). - `spec` (object): The print as the customer has described it so far, beside garment. Null where they have not said; still_needed lists what is missing. - `status` (string) - `still_needed` (array): Fields the customer has not told us yet, and any go-ahead we are waiting on for something the order cannot carry. ### `create_checkout` (~127 tokens) Get the payment link Returns the payment link for a fully specified order with a chosen option. Show checkout_url to the customer as a link labeled "Pay and enter shipping": they see their artwork and total, confirm their email address with a code we send them, then pay and enter their shipping address. Nothing is ordered until they pay. Refuses, and says what is missing, if the order is not ready. When the customer is signed in, asking to pay also saves the order to their account, so it stops expiring. Input parameters: - `order_id` (string, required): The order_id returned by start_print_order. Output parameters: - `alternatives` (array|null): Present from the moment several styles fit until the customer picks, beside whatever ask_next asks: show all of them with their summaries, prices and minimums, say the one marked is_provisional is wh… - `artwork` (object|null) - `artwork_upload_url` (string|null): Present until the design is accepted. Show it to the customer as one link labeled "Upload your design", not as a bare address: they drop their design file on that page and it is checked there. You ca… - `ask_next` (string|null): Ask the customer this, in your own words, and send the answer to describe_order. - `checkout_url` (string|null): Show it to the customer as one link labeled "Pay and enter shipping", not as a bare address: they see the artwork and total, confirm their email with a code we send them, then pay and enter their add… - `choices` (array|null): Answers the customer can pick from, one set per field ask_next asks about. Offer them as selectable options where your client can, otherwise as a short list. They are suggestions: colors are families… - `chosen_option` (object|null) - `expires_at` (string|null): When an unsaved order expires; null once it is saved to an account or paid. - `garment` (object|null): The garment on the order, and what mockup_url shows. Name it when you show the picture; when it is provisional, say so. - `mockup_url` (string|null): The garment on the order, in the customer's color, with their design on it once we have it. An image address: show it as a picture where your client can, never as text or as a link, and never describ… - `mockup_views` (array|null): Every side of the garment, the printed one first: mockup_url with the design, then the other sides plain. Where your client can show pictures, show them all, so the customer sees which sides stay bla… - `next_call` (string): What to call next, and why. - `notes` (array): Relay these to the customer. - `options` (array|null) - `order_id` (string) - `saved` (boolean): Whether the order is saved to a customer account (save_progress). - `spec` (object): The print as the customer has described it so far, beside garment. Null where they have not said; still_needed lists what is missing. - `status` (string) - `still_needed` (array): Fields the customer has not told us yet, and any go-ahead we are waiting on for something the order cannot carry. ### `resume_order` (~105 tokens) Resume an expired order Picks up an order that another tool refused as expired. Applies only after that refusal, with the same order_id, when the customer wants to continue that order rather than start over: it gives the order a fresh window and fresh links and returns where things stand, so you can carry on with the call next_call names. Without a refusal there is nothing to resume; start_print_order opens a new order. Input parameters: - `order_id` (string, required): The order_id another tool refused as expired. Output parameters: - `alternatives` (array|null): Present from the moment several styles fit until the customer picks, beside whatever ask_next asks: show all of them with their summaries, prices and minimums, say the one marked is_provisional is wh… - `artwork` (object|null) - `artwork_upload_url` (string|null): Present until the design is accepted. Show it to the customer as one link labeled "Upload your design", not as a bare address: they drop their design file on that page and it is checked there. You ca… - `ask_next` (string|null): Ask the customer this, in your own words, and send the answer to describe_order. - `checkout_url` (string|null): Show it to the customer as one link labeled "Pay and enter shipping", not as a bare address: they see the artwork and total, confirm their email with a code we send them, then pay and enter their add… - `choices` (array|null): Answers the customer can pick from, one set per field ask_next asks about. Offer them as selectable options where your client can, otherwise as a short list. They are suggestions: colors are families… - `chosen_option` (object|null) - `expires_at` (string|null): When an unsaved order expires; null once it is saved to an account or paid. - `garment` (object|null): The garment on the order, and what mockup_url shows. Name it when you show the picture; when it is provisional, say so. - `mockup_url` (string|null): The garment on the order, in the customer's color, with their design on it once we have it. An image address: show it as a picture where your client can, never as text or as a link, and never describ… - `mockup_views` (array|null): Every side of the garment, the printed one first: mockup_url with the design, then the other sides plain. Where your client can show pictures, show them all, so the customer sees which sides stay bla… - `next_call` (string): What to call next, and why. - `notes` (array): Relay these to the customer. - `options` (array|null) - `order_id` (string) - `saved` (boolean): Whether the order is saved to a customer account (save_progress). - `spec` (object): The print as the customer has described it so far, beside garment. Null where they have not said; still_needed lists what is missing. - `status` (string) - `still_needed` (array): Fields the customer has not told us yet, and any go-ahead we are waiting on for something the order cannot carry. ### `save_progress` (~108 tokens) Save the order to my account Saves the customer's order to their account so they can pick it up from any conversation; a saved order never expires. Needs the customer to be signed in: if they are not, your client will ask them to sign in or create an account with us, then call this again. Applies when a response's notes offer saving, or when the customer asks to save, to come back later, or to keep their order. Input parameters: - `order_id` (string, required): The order_id returned by start_print_order. Output parameters: - `alternatives` (array|null): Present from the moment several styles fit until the customer picks, beside whatever ask_next asks: show all of them with their summaries, prices and minimums, say the one marked is_provisional is wh… - `artwork` (object|null) - `artwork_upload_url` (string|null): Present until the design is accepted. Show it to the customer as one link labeled "Upload your design", not as a bare address: they drop their design file on that page and it is checked there. You ca… - `ask_next` (string|null): Ask the customer this, in your own words, and send the answer to describe_order. - `checkout_url` (string|null): Show it to the customer as one link labeled "Pay and enter shipping", not as a bare address: they see the artwork and total, confirm their email with a code we send them, then pay and enter their add… - `choices` (array|null): Answers the customer can pick from, one set per field ask_next asks about. Offer them as selectable options where your client can, otherwise as a short list. They are suggestions: colors are families… - `chosen_option` (object|null) - `expires_at` (string|null): When an unsaved order expires; null once it is saved to an account or paid. - `garment` (object|null): The garment on the order, and what mockup_url shows. Name it when you show the picture; when it is provisional, say so. - `mockup_url` (string|null): The garment on the order, in the customer's color, with their design on it once we have it. An image address: show it as a picture where your client can, never as text or as a link, and never describ… - `mockup_views` (array|null): Every side of the garment, the printed one first: mockup_url with the design, then the other sides plain. Where your client can show pictures, show them all, so the customer sees which sides stay bla… - `next_call` (string): What to call next, and why. - `notes` (array): Relay these to the customer. - `options` (array|null) - `order_id` (string) - `saved` (boolean): Whether the order is saved to a customer account (save_progress). - `spec` (object): The print as the customer has described it so far, beside garment. Null where they have not said; still_needed lists what is missing. - `status` (string) - `still_needed` (array): Fields the customer has not told us yet, and any go-ahead we are waiting on for something the order cannot carry. ### `my_orders` (~98 tokens) My orders Lists the signed-in customer's orders with us, open and paid, each with its status. Needs the customer to be signed in; if they are not, your client will ask them to. Applies when the customer asks what they have with us, wants to pick up a saved order, or asks where an order is. Input parameters: - `include` (string): Which orders to list: everything (the default), only open unpaid ones, or only paid ones. Output parameters: - `next_call` (string) - `orders` (array): Every order on this account, open and paid, latest activity first. ## Diagnostics Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/com-rushordertees-rushordertees/mcp-print#diagnostics ## Score history - 2026-11-06: 77 - 2026-11-05: 76 - 2026-11-04: 76 - 2026-11-03: 76 - 2026-11-02: 75 - 2026-11-01: 75 - 2026-10-31: 74 - 2026-10-30: 74 - 2026-10-29: 73 - 2026-10-28: 73 - 2026-10-27: 72 - 2026-10-26: 72 ## Common questions ### What is the RushOrderTees MCP server? RushOrderTees is an MCP server listed in the public MCP registry as com.rushordertees/rushordertees. Custom t-shirts and apparel, printed and shipped in the US on your deadline. This page covers its hosted endpoint (https://mcp.rushordertees.com/mcp/print). ### Is the RushOrderTees MCP server safe to use? RushOrderTees scores 77 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 RushOrderTees MCP server expose? RushOrderTees exposes 12 tools: start_print_order, describe_order, pick_choice, choose_style, preview_colors, and 7 more. Their descriptions and schemas cost roughly 1,673 tokens of context every time the server is loaded. ### Does the RushOrderTees MCP server require authentication? No. We connected to RushOrderTees without credentials and it answered, so anything it exposes is reachable by anyone who knows the address. ### Is the RushOrderTees MCP server still maintained? RushOrderTees is still listed as active in the MCP registry. We last reached this channel on 6 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 RushOrderTees MCP server? VerifyMCP ran 14 checks on RushOrderTees, 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. ## Links - Remote endpoint: https://mcp.rushordertees.com/mcp/print - Website: https://mcp.rushordertees.com/ - Changelog RSS feed: https://verifymcp.io/servers/com-rushordertees-rushordertees/mcp-print.xml - Changelog JSON feed: https://verifymcp.io/servers/com-rushordertees-rushordertees/mcp-print/changelog.json - Trust report (JSON): https://verifymcp.io/servers/com-rushordertees-rushordertees/mcp-print.json - HTML version of this page: https://verifymcp.io/servers/com-rushordertees-rushordertees/mcp-print