io.usefulapi/printify
REMOTE · PRINTIFY.USEFULAPI.IO · SCANNED SEP 21
Read shops, catalog blueprints, print providers, products and orders; create and publish products.
Available components
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 Security78
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation is enforced on tool calls, advertised via RFC 9728 protected-resource metadata. Discovery is public, which costs nothing: no tool can be invoked without a token. View diagnostics → Pass
- HTTPS enforcement could not be verified: the plaintext port answered with HTTP 401, which proves neither a plaintext path nor enforcement. View diagnostics → Unverified
- HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
- The authorisation server offers only Dynamic Client Registration (RFC 7591), which MCP 2026-07-28 deprecated in favour of Client ID Metadata Documents. View diagnostics → Partial
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability81
- AI-judged instruction clarity (excellent).Pass
- Tool/resource definitions use about 1178 tokens (~84/item across 14 items; 14 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management47
- Stability observed for 14 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
- All 1 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation.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
Capabilities60
- Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28. See how to fix → Fail
How do I install the io.usefulapi/printify MCP server?
io.usefulapi/printify is a hosted endpoint at https://printify.usefulapi.io/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 · printify.usefulapi.io
claude mcp add --transport http io-usefulapi-printify 'https://printify.usefulapi.io/mcp'
{
"mcpServers": {
"io-usefulapi-printify": {
"url": "https://printify.usefulapi.io/mcp"
}
}
} {
"servers": {
"io-usefulapi-printify": {
"type": "http",
"url": "https://printify.usefulapi.io/mcp"
}
}
} [mcp_servers.io-usefulapi-printify] url = "https://printify.usefulapi.io/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"io-usefulapi-printify": {
"type": "remote",
"url": "https://printify.usefulapi.io/mcp",
"enabled": true
}
}
} openclaw mcp add io-usefulapi-printify --url 'https://printify.usefulapi.io/mcp' --transport streamable-http
mcp_servers:
io-usefulapi-printify:
url: "https://printify.usefulapi.io/mcp" {
"McpServers": {
"io-usefulapi-printify": {
"Transport": "http",
"Url": "https://printify.usefulapi.io/mcp"
}
}
} assistant mcp add io-usefulapi-printify -t streamable-http -u 'https://printify.usefulapi.io/mcp'
{
"mcpServers": {
"io-usefulapi-printify": {
"type": "http",
"url": "https://printify.usefulapi.io/mcp"
}
}
} The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.
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.
- 21 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 43 to 47. That category is still filling its 30-day observation window: 13 days of observed history at the previous scan, 14 at this one. The score rises as the window fills, whether or not the server changes.
- 19 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 37 to 40. That category is still filling its 30-day observation window: 11 days of observed history at the previous scan, 12 at this one. The score rises as the window fills, whether or not the server changes.
- 18 Sept 26 −9
- Stability: pass → 0.37 functional
- 17 Sept 26 0
- Stability: 0.97 → pass security
- 16 Sept 26 0
- Stability: pass → 0.97 functional
- 15 Sept 26 +68
- Transport: unverified → pass ▲ security
- Authorization: unverified → pass ▲ security
- Injection markers: unverified → pass ▲ security
- Stability: unverified → pass ▲ security
- MCP protocol: unverified → fail ▼ functional
- Endpoint reachability: not serving MCP → reachable ▲ functional
- Tool coverage: unverified → 100 ▲ functional
- 14 Sept 26 −65
- Endpoint reachability: reachable → not serving MCP ▼ security
- Stability: pass → unverified ▼ security
- Tool safety: pass → unverified ▼ security
- Transport: pass → unverified ▼ security
- Authorization: fail → unverified ▼ security
- Capabilities: fail → unverified ▼ functional
- Tool coverage: 100 → unverified ▼ functional
- 13 Sept 26 +65
- Authorization: unverified → fail ▼ security
- Transport: unverified → pass ▲ security
- Injection markers: unverified → pass ▲ security
- Stability: unverified → pass ▲ security
- MCP protocol: unverified → fail ▼ functional
- Endpoint reachability: not serving MCP → reachable ▲ functional
- Tool coverage: unverified → 100 ▲ functional
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 Sept 2026 · Probed https://printify.usefulapi.io/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=usefulapi.io | CN=WE1,O=Google Trust Services,C=US | 1 Aug 2026 | 30 Oct 2026 | ECDSA 256 | ECDSA-SHA256 | b7077024ea693e640e5cbdcb39b24436 |
| SANs: usefulapi.io, printify.usefulapi.io, *.printify.usefulapi.io | ||||||
| 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 printify.usefulapi.io. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| io. | present | 57355 | 8 | Verified |
| usefulapi.io. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication Enforced and verified
The endpoint asked for a token and published valid RFC 9728 metadata describing how to get one.
| Result | Enforced and verified |
|---|---|
| Enforced | On tool calls |
| HTTP status | 200 |
WWW-Authenticate challenge Bearer realm="OAuth", resource_metadata="https://printify.usefulapi.io/.well-known/oauth-protected-resource/mcp", error="invalid_token", error_description="Missing or invalid access token"
Bearer realm="OAuth", resource_metadata="https://printify.usefulapi.io/.well-known/oauth-protected-resource/mcp", error="invalid_token", error_description="Missing or invalid access token"Protected resource metadata
| Document | https://printify.usefulapi.io/.well-known/oauth-protected-resource/mcp |
|---|---|
| Retrieved | Yes |
| Resource | https://printify.usefulapi.io/mcp |
| Authorisation server | https://printify.usefulapi.io |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://printify.usefulapi.io/mcp | Verified | 200 | |
| http (plaintext) | http://printify.usefulapi.io/mcp | Inconclusive | 401 |
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 →
printify_calculate_shipping Calculate shipping ~177
Get a shipping price quote for a set of line items to a destination address. Non-destructive — it only prices, it does NOT place an order. `line_items` is an array where each item is one of {product_id, variant_id, quantity}, {print_provider_id, blueprint_id, variant_id, quantity}, or {sku, quantity}. `address_to` is the destination (first_name, last_name, email, phone, country, region, address1, address2, city, zip, company). Printify REST: POST /v1/shops/{shop_id}/orders/shipping.json.
| Name | Type | Req | Description |
|---|---|---|---|
| address_to | object | yes | Destination address object. |
| line_items | array | yes | Array of line items to price (see description for accepted shapes). |
| shop_id | – | yes | Shop id — required. |
No output schema declared.
No examples provided.
printify_get_blueprint Get blueprint ~48
Get a single catalog blueprint's details. Printify REST: GET /v1/catalog/blueprints/{blueprint_id}.json.
| Name | Type | Req | Description |
|---|---|---|---|
| blueprint_id | – | yes | Blueprint id — required. |
No output schema declared.
No examples provided.
printify_get_order Get order ~70
Get a single order's full details, including `shipments` (carrier + tracking numbers). Printify REST: GET /v1/shops/{shop_id}/orders/{order_id}.json.
| Name | Type | Req | Description |
|---|---|---|---|
| order_id | – | yes | Order id — required. |
| shop_id | – | yes | Shop id — required. |
No output schema declared.
No examples provided.
printify_get_print_providers Get blueprint print providers ~55
List the print providers that can produce a given blueprint. Printify REST: GET /v1/catalog/blueprints/{blueprint_id}/print_providers.json.
| Name | Type | Req | Description |
|---|---|---|---|
| blueprint_id | – | yes | Blueprint id — required. |
No output schema declared.
No examples provided.
printify_get_product Get product ~69
Get a single product's full details (variants, images, print areas, publish status). Printify REST: GET /v1/shops/{shop_id}/products/{product_id}.json.
| Name | Type | Req | Description |
|---|---|---|---|
| product_id | – | yes | Product id — required. |
| shop_id | – | yes | Shop id — required. |
No output schema declared.
No examples provided.
printify_get_variants Get variants ~101
List the variants (sizes, colors) a print provider offers for a blueprint. Printify REST: GET /v1/catalog/blueprints/{blueprint_id}/print_providers/{print_provider_id}/variants.json.
| Name | Type | Req | Description |
|---|---|---|---|
| blueprint_id | – | yes | Blueprint id — required. |
| print_provider_id | – | yes | Print provider id — required. |
| show_out_of_stock | boolean | – | Include out-of-stock variants (sent as show-out-of-stock=1). |
No output schema declared.
No examples provided.
printify_list_catalog_blueprints List catalog blueprints ~50
List all blueprints (product types, e.g. 'Unisex T-Shirt') available in the Printify catalog. Printify REST: GET /v1/catalog/blueprints.json.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
printify_list_orders List orders ~113
List orders in a shop (paginated), optionally filtered by status or SKU. Printify REST: GET /v1/shops/{shop_id}/orders.json.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | Items per page (default 10, max 10). |
| page | integer | – | 1-based page number. |
| shop_id | – | yes | Shop id — required. |
| sku | string | – | Filter to orders containing this SKU. |
| status | string | – | Filter by fulfillment status, e.g. 'fulfilled'. |
No output schema declared.
No examples provided.
printify_list_print_providers List print providers ~37
List all print providers in the Printify catalog. Printify REST: GET /v1/catalog/print_providers.json.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
printify_list_products List products ~84
List products in a shop (paginated). Printify REST: GET /v1/shops/{shop_id}/products.json.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | Items per page (default 10, max 50). |
| page | integer | – | 1-based page number. |
| shop_id | – | yes | Shop id (from printify_list_shops) — required. |
No output schema declared.
No examples provided.
printify_list_shops List shops ~56
List all shops connected to the Printify account. This is the entry point — each shop's `id` is required by the product, order and webhook tools. Printify REST: GET /v1/shops.json.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
printify_list_uploads List uploads ~65
List images uploaded to the account's media library (paginated). Printify REST: GET /v1/uploads.json.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | Items per page (default 10, max 100). |
| page | integer | – | 1-based page number. |
No output schema declared.
No examples provided.
printify_list_webhooks List webhooks ~48
List the webhooks configured for a shop. Printify REST: GET /v1/shops/{shop_id}/webhooks.json.
| Name | Type | Req | Description |
|---|---|---|---|
| shop_id | – | yes | Shop id — required. |
No output schema declared.
No examples provided.
printify_publish_product Publish product ~205
Publish a product to the shop's connected sales channel (e.g. Shopify, Etsy). STATE-CHANGING: this locks the product and pushes the selected fields to the external store. The body is an object of booleans controlling which fields are published; all default to true. Printify REST: POST /v1/shops/{shop_id}/products/{product_id}/publish.json.
| Name | Type | Req | Description |
|---|---|---|---|
| description | boolean | – | Publish the description (default true). |
| images | boolean | – | Publish the images (default true). |
| keyFeatures | boolean | – | Publish the key features (default true). |
| product_id | – | yes | Product id — required. |
| shipping_template | boolean | – | Publish the shipping template (default true). |
| shop_id | – | yes | Shop id — required. |
| tags | boolean | – | Publish the tags (default true). |
| title | boolean | – | Publish the title (default true). |
| variants | boolean | – | Publish the variants (default true). |
No output schema declared.
No examples provided.
What is the io.usefulapi/printify MCP server?
io.usefulapi/printify is an MCP server listed in the public MCP registry as io.usefulapi/printify. Read shops, catalog blueprints, print providers, products and orders; create and publish products. This page covers its hosted endpoint (https://printify.usefulapi.io/mcp).
Is the io.usefulapi/printify MCP server safe to use?
io.usefulapi/printify scores 79 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 io.usefulapi/printify MCP server expose?
io.usefulapi/printify exposes 14 tools: printify_list_shops, printify_list_products, printify_get_product, printify_list_orders, printify_get_order, and 9 more. Their descriptions and schemas cost roughly 1,178 tokens of context every time the server is loaded.
Does the io.usefulapi/printify MCP server require authentication?
Yes. io.usefulapi/printify asked us for credentials when we connected, so you will need to authorise it in your MCP client before it can do anything.
Is the io.usefulapi/printify MCP server still maintained?
io.usefulapi/printify is still listed as active in the MCP registry. We last reached this channel on 21 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.