RushOrderTees
REMOTE · MCP.RUSHORDERTEES.COM
Custom t-shirts and apparel, printed and shipped in the US on your deadline.
Available components
Last scanned (11 hours ago)
Scores higher than 66% of remote servers
Reachable. Last reached 5 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 Security74
- 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
- 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 Usability79
- 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
- AI-judged instruction clarity (excellent).Pass
- 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. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management33
- Stability observed for 10 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
- Structured output schemas are declared (100% 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 12 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 14 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
- 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.
- 5 Nov 26 0
- 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 security
- Server version: 0.43.0 → 0.46.0 functional
- 3 Nov 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.
- 1 Nov 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.
- 30 Oct 26 +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.
- 29 Oct 26 0
- Server version: 0.42.0 → 0.43.0 functional
- 28 Oct 26 +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.
- 27 Oct 26 0
- Stability: unverified → 0.03 ▲ functional
- Server version: 0.41.0 → 0.42.0 functional
- 26 Oct 26 72
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 5 Nov 2026 · Probed https://mcp.rushordertees.com/mcp/print
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=mcp.rushordertees.com | CN=WE1,O=Google Trust Services,C=US | 6 Oct 2026 | 4 Jan 2027 | ECDSA 256 | ECDSA-SHA256 | 4dd2d0963c9fdd5313c57816c40bef68 |
| SANs: mcp.rushordertees.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 mcp.rushordertees.com. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | Trust anchor | 20326, 38696 | 8, 8 | Verified |
| com. | DS published | 19718 | 13 | Verified |
| rushordertees.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 |
|---|---|
| x-content-type-options | nosniff |
| x-frame-options | deny |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://mcp.rushordertees.com/mcp/print | Verified | 200 | |
| http (plaintext) | http://mcp.rushordertees.com/mcp/print | HTTPS enforced | 301 | https://mcp.rushordertees.com/mcp/print |
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 →
choose_option Choose an option ~91
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.
| Name | Type | Req | Description |
|---|---|---|---|
| option_id | string | yes | The id of the option the customer chose, exactly as returned by get_options. |
| order_id | string | yes | The order_id returned by start_print_order. |
| Name | Type | Req | Description |
|---|---|---|---|
| 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 | yes | What to call next, and why. |
| notes | array | yes | Relay these to the customer. |
| options | array|null | – | – |
| order_id | string | yes | – |
| saved | boolean | yes | Whether the order is saved to a customer account (save_progress). |
| spec | object | yes | 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 | yes | – |
| still_needed | array | yes | Fields the customer has not told us yet, and any go-ahead we are waiting on for something the order cannot carry. |
No examples provided.
choose_style Choose a garment ~170
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.
| Name | Type | Req | Description |
|---|---|---|---|
| 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 | yes | The order_id returned by start_print_order. |
| style_id | string | yes | The id of the alternative the customer chose, exactly as returned by describe_order, or the style_id of a preview_colors picture. |
| Name | Type | Req | Description |
|---|---|---|---|
| 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 | yes | What to call next, and why. |
| notes | array | yes | Relay these to the customer. |
| options | array|null | – | – |
| order_id | string | yes | – |
| saved | boolean | yes | Whether the order is saved to a customer account (save_progress). |
| spec | object | yes | 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 | yes | – |
| still_needed | array | yes | Fields the customer has not told us yet, and any go-ahead we are waiting on for something the order cannot carry. |
No examples provided.
create_checkout Get the payment link ~127
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.
| Name | Type | Req | Description |
|---|---|---|---|
| order_id | string | yes | The order_id returned by start_print_order. |
| Name | Type | Req | Description |
|---|---|---|---|
| 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 | yes | What to call next, and why. |
| notes | array | yes | Relay these to the customer. |
| options | array|null | – | – |
| order_id | string | yes | – |
| saved | boolean | yes | Whether the order is saved to a customer account (save_progress). |
| spec | object | yes | 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 | yes | – |
| still_needed | array | yes | Fields the customer has not told us yet, and any go-ahead we are waiting on for something the order cannot carry. |
No examples provided.
describe_order Describe the order ~217
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.
| Name | Type | Req | Description |
|---|---|---|---|
| context | string | yes | 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 | yes | The order_id returned by start_print_order. |
| Name | Type | Req | Description |
|---|---|---|---|
| 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 | yes | What to call next, and why. |
| notes | array | yes | Relay these to the customer. |
| options | array|null | – | – |
| order_id | string | yes | – |
| saved | boolean | yes | Whether the order is saved to a customer account (save_progress). |
| spec | object | yes | 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 | yes | – |
| still_needed | array | yes | Fields the customer has not told us yet, and any go-ahead we are waiting on for something the order cannot carry. |
No examples provided.
get_options Get priced options ~110
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.
| Name | Type | Req | Description |
|---|---|---|---|
| order_id | string | yes | The order_id returned by start_print_order. |
| Name | Type | Req | Description |
|---|---|---|---|
| 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 | yes | What to call next, and why. |
| notes | array | yes | Relay these to the customer. |
| options | array|null | – | – |
| order_id | string | yes | – |
| saved | boolean | yes | Whether the order is saved to a customer account (save_progress). |
| spec | object | yes | 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 | yes | – |
| still_needed | array | yes | Fields the customer has not told us yet, and any go-ahead we are waiting on for something the order cannot carry. |
No examples provided.
my_orders My orders ~98
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.
| Name | Type | Req | Description |
|---|---|---|---|
| include | string | – | Which orders to list: everything (the default), only open unpaid ones, or only paid ones. |
| Name | Type | Req | Description |
|---|---|---|---|
| next_call | string | yes | – |
| orders | array | yes | Every order on this account, open and paid, latest activity first. |
No examples provided.
pick_choice Pick a choice ~111
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.
| Name | Type | Req | Description |
|---|---|---|---|
| field | string | yes | The field of the choices set the customer answered, as the last reply named it. |
| option | string | yes | The option the customer picked, exactly as the last reply listed it. |
| order_id | string | yes | The order_id returned by start_print_order. |
| Name | Type | Req | Description |
|---|---|---|---|
| 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 | yes | What to call next, and why. |
| notes | array | yes | Relay these to the customer. |
| options | array|null | – | – |
| order_id | string | yes | – |
| saved | boolean | yes | Whether the order is saved to a customer account (save_progress). |
| spec | object | yes | 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 | yes | – |
| still_needed | array | yes | Fields the customer has not told us yet, and any go-ahead we are waiting on for something the order cannot carry. |
No examples provided.
preview_colors Preview colors ~172
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.
| Name | Type | Req | Description |
|---|---|---|---|
| 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 | yes | The order_id returned by start_print_order. |
| Name | Type | Req | Description |
|---|---|---|---|
| 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 | yes | 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 | yes | What to call next, and why. |
| notes | array | yes | Relay these to the customer. |
| options | array|null | – | – |
| order_id | string | yes | – |
| saved | boolean | yes | Whether the order is saved to a customer account (save_progress). |
| spec | object | yes | 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 | yes | – |
| still_needed | array | yes | Fields the customer has not told us yet, and any go-ahead we are waiting on for something the order cannot carry. |
No examples provided.
resume_order Resume an expired order ~105
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.
| Name | Type | Req | Description |
|---|---|---|---|
| order_id | string | yes | The order_id another tool refused as expired. |
| Name | Type | Req | Description |
|---|---|---|---|
| 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 | yes | What to call next, and why. |
| notes | array | yes | Relay these to the customer. |
| options | array|null | – | – |
| order_id | string | yes | – |
| saved | boolean | yes | Whether the order is saved to a customer account (save_progress). |
| spec | object | yes | 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 | yes | – |
| still_needed | array | yes | Fields the customer has not told us yet, and any go-ahead we are waiting on for something the order cannot carry. |
No examples provided.
save_progress Save the order to my account ~108
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.
| Name | Type | Req | Description |
|---|---|---|---|
| order_id | string | yes | The order_id returned by start_print_order. |
| Name | Type | Req | Description |
|---|---|---|---|
| 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 | yes | What to call next, and why. |
| notes | array | yes | Relay these to the customer. |
| options | array|null | – | – |
| order_id | string | yes | – |
| saved | boolean | yes | Whether the order is saved to a customer account (save_progress). |
| spec | object | yes | 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 | yes | – |
| still_needed | array | yes | Fields the customer has not told us yet, and any go-ahead we are waiting on for something the order cannot carry. |
No examples provided.
start_print_order Start a print order ~139
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.
| Name | Type | Req | Description |
|---|---|---|---|
| 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. |
| Name | Type | Req | Description |
|---|---|---|---|
| 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 | yes | What to call next, and why. |
| notes | array | yes | Relay these to the customer. |
| options | array|null | – | – |
| order_id | string | yes | – |
| saved | boolean | yes | Whether the order is saved to a customer account (save_progress). |
| spec | object | yes | 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 | yes | – |
| still_needed | array | yes | Fields the customer has not told us yet, and any go-ahead we are waiting on for something the order cannot carry. |
No examples provided.
submit_artwork Send the design ~225
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.
| Name | Type | Req | Description |
|---|---|---|---|
| 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 | yes | The order_id returned by start_print_order. |
| Name | Type | Req | Description |
|---|---|---|---|
| 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 | yes | What to call next, and why. |
| notes | array | yes | Relay these to the customer. |
| options | array|null | – | – |
| order_id | string | yes | – |
| saved | boolean | yes | Whether the order is saved to a customer account (save_progress). |
| spec | object | yes | 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 | yes | – |
| still_needed | array | yes | Fields the customer has not told us yet, and any go-ahead we are waiting on for something the order cannot carry. |
No examples provided.
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.
remote · mcp.rushordertees.com
claude mcp add --transport http com-rushordertees-rushordertees 'https://mcp.rushordertees.com/mcp/print'
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 76 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 5 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.