Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

Printify MCP by usefulapi

REMOTE · PRINTIFY.USEFULAPI.IO

Read shops, catalog blueprints, print providers, products and orders; create and publish products.

−56 this week 18 Trust /100

Last scanned (8 hours ago)

Scores higher than 4% of remote servers

Reachable. Last reached 5 Nov 2026.

Category E-commerce

Trust breakdown (7 categories)

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 Security46
Transport & Reachability0
Schema Quality & AI Usability0
  • Schema not yet verified: we couldn't read the endpoint's schema, or could read only part of its tool list.Unverified
Stability & Change Management0
  • Stability not yet verified: not enough scan history yet (needs a 30-day window).Unverified
Tool Coverage0
  • Tool coverage not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.Unverified
Tool Safety0
  • Tool safety not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.Unverified
Capabilities0
  • Capabilities not yet verified: we couldn't read the endpoint's capabilities.Unverified

Unverified: 5 categories

Categories scored 0 because we could not verify them: authentication we do not have, an unreachable endpoint, or not enough scan history. We only credit what we can confirm.

Changelog

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.

  • 2 Nov 26 −60
    • Endpoint reachability: reachable → not serving MCP ▼ security
    • Tool safety: pass → unverified ▼ security
    • Authorization: pass → unverified ▼ security
    • Stability: 0.90 → unverified ▼ security
    • Schema quality: 100 → unverified ▼ functional
    • Capabilities: pass → unverified ▼ functional
    • Tool coverage: 100 → unverified ▼ functional
  • 1 Nov 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 87 to 90. That category is still filling its 30-day observation window: 26 days of observed history at the previous scan, 27 at this one. The score rises as the window fills, whether or not the server changes.

  • 31 Oct 26 +3
    • Authorization: partial → pass ▲ security
    • MCP protocol: fail → pass ▲ functional
    • New prompt “check_order_status_and_tracking_numbers” functional
    • New prompt “compare_print_providers_and_options_for_a_product_type” functional
    • New prompt “get_a_shipping_quote_for_items_to_an_address” functional
    • New prompt “publish_a_product_to_your_sales_channel” functional
    • New prompt “review_your_products_and_their_publish_status” functional
    • MCP protocol version: 2025-06-18 → 2025-11-25 functional
    • Server version: 1.32.0 → 1.34.0 functional
    • Server version: 1.31.0 → 1.32.0 functional
    • Server version: 1.30.2 → 1.31.0 functional
  • 30 Oct 26 0
    • Server version: 1.30.1 → 1.30.2 functional
    • Server version: 1.30.0 → 1.30.1 functional
  • 29 Oct 26 0
    • New tool “printify_copy_products”, which the server declares destructive security
    • New tool “printify_resolve_copy”, which the server declares destructive security
    • Tool coverage: 100% → 88% ▼ functional
    • Schema quality: pass → fail ▼ functional
    • Server version: 1.28.0 → 1.30.0 functional
    • Server version: 1.27.0 → 1.28.0 functional
    • New tool “printify_copy_status” functional
  • 28 Oct 26 0
    • Server version: 1.26.0 → 1.27.0 functional
    • Server version: 1.25.0 → 1.26.0 functional
  • 27 Oct 26 +1
    • Server version: 1.24.0 → 1.25.0 functional
  • 25 Oct 26 −4
    • Stability: pass → 0.67 functional
    • Server version: 1.23.0 → 1.24.0 functional
    • Server version: 1.22.0 → 1.23.0 functional
    • Server version: 1.21.3 → 1.22.0 functional
    • Server version: 1.21.0 → 1.21.3 functional
Diagnostics

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://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 13 Sept 2026 12 Dec 2026 ECDSA 256 ECDSA-SHA256 d9be3287b0fde9630e825ba1f79bff3f
SANs: usefulapi.io, *.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 38690 8 Verified
usefulapi.io. absent Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation
Authentication Inconclusive

We could not reach the endpoint well enough to judge its authorisation posture.

Result Inconclusive
HTTP status 302

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 Redirected 302 https://usefulapi.io/printify/
http (plaintext) http://printify.usefulapi.io/mcp Inconclusive 302 http://printify.usefulapi.io/mcp
MCP tools · 17 exposed · ~1,910 tokens

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 →

Tool Tokens
printify_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.

NameTypeReqDescription
address_toobjectyesDestination address object.
line_itemsarrayyesArray of line items to price (see description for accepted shapes).
shop_id–yesShop id — required.

No output schema declared.

No examples provided.

printify_copy_products ~412

Preview or copy selected products or a complete catalog between two Printify shops in the same account. Preserves title, description, blueprint/provider, variant IDs/prices/enabled flags, artwork IDs and print-area transforms. Preserves canvas side printing and image pattern rotation. This initial workflow does not copy tags, SKUs, channel IDs, publication state or generated mockups. Products with text/personalization layers are explicitly refused because their creation fields are read-only. Preview by default. confirm:true starts/resumes a durable bounded job; save job_id and keep calling with that job_id and confirm:true until complete. Duplicate prevention remembers copies made by this connector, including across restarts/jobs; pre-existing copies made elsewhere are not detected. An uncertain create is never automatically retried: inspect the target and use printify_resolve_copy. Do not change the source catalog during an all-products run. Requires shops.read/products.read/products.write. Confirmed copying requires the hosted connector's durable coordinator.

NameTypeReqDescription
all_productsboolean–Copy all source products with resumable pagination. Omit when resuming job_id.
batch_sizeinteger–Maximum creates in this call (default 1). Calls are also bounded when skipping prior copies.
confirmboolean–False/omitted previews only. True authorizes creation of new draft products.
job_idstring–A previously returned job_id to resume; supply the same source and target shops.
product_idsarray–Selected source product IDs; mutually exclusive with all_products:true. Omit when resuming job_id.
source_shop_id–yesSource shop ID; the token must have access to both shops in the same Printify account.
start_new_jobboolean–With confirm:true and a selection, restart enumeration after source-catalog changes; never combine with job_id. Permanent copied and uncertain mappings are retained.
target_shop_id–yesDifferent target shop ID. New products stay as drafts and are not published.

No output schema declared.

No examples provided.

printify_copy_status ~138

Read a durable product-copy job's progress, target mappings, failures and uncertain writes. Verifies that the current token can access both shops. Does not create or retry products.

NameTypeReqDescription
entry_cursorstring–next_cursor from a previous status page; lists all entries including older failures.
entry_limitinteger–Job entries per status page (default 20).
job_idstringyes–
source_shop_id–yesSource shop ID; the token must have access to both shops in the same Printify account.
target_shop_id–yesDifferent target shop ID. New products stay as drafts and are not published.

No output schema declared.

No examples provided.

printify_get_blueprint ~48

Get a single catalog blueprint's details. Printify REST: GET /v1/catalog/blueprints/{blueprint_id}.json.

NameTypeReqDescription
blueprint_id–yesBlueprint id — required.

No output schema declared.

No examples provided.

printify_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.

NameTypeReqDescription
order_id–yesOrder id — required.
shop_id–yesShop id — required.

No output schema declared.

No examples provided.

printify_get_print_providers ~55

List the print providers that can produce a given blueprint. Printify REST: GET /v1/catalog/blueprints/{blueprint_id}/print_providers.json.

NameTypeReqDescription
blueprint_id–yesBlueprint id — required.

No output schema declared.

No examples provided.

printify_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.

NameTypeReqDescription
product_id–yesProduct id — required.
shop_id–yesShop id — required.

No output schema declared.

No examples provided.

printify_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.

NameTypeReqDescription
blueprint_id–yesBlueprint id — required.
print_provider_id–yesPrint provider id — required.
show_out_of_stockboolean–Include out-of-stock variants (sent as show-out-of-stock=1).

No output schema declared.

No examples provided.

printify_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 ~113

List orders in a shop (paginated), optionally filtered by status or SKU. Printify REST: GET /v1/shops/{shop_id}/orders.json.

NameTypeReqDescription
limitinteger–Items per page (default 10, max 10).
pageinteger–1-based page number.
shop_id–yesShop id — required.
skustring–Filter to orders containing this SKU.
statusstring–Filter by fulfillment status, e.g. 'fulfilled'.

No output schema declared.

No examples provided.

printify_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 ~84

List products in a shop (paginated). Printify REST: GET /v1/shops/{shop_id}/products.json.

NameTypeReqDescription
limitinteger–Items per page (default 10, max 50).
pageinteger–1-based page number.
shop_id–yesShop id (from printify_list_shops) — required.

No output schema declared.

No examples provided.

printify_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 ~65

List images uploaded to the account's media library (paginated). Printify REST: GET /v1/uploads.json.

NameTypeReqDescription
limitinteger–Items per page (default 10, max 100).
pageinteger–1-based page number.

No output schema declared.

No examples provided.

printify_list_webhooks ~48

List the webhooks configured for a shop. Printify REST: GET /v1/shops/{shop_id}/webhooks.json.

NameTypeReqDescription
shop_id–yesShop id — required.

No output schema declared.

No examples provided.

printify_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.

NameTypeReqDescription
descriptionboolean–Publish the description (default true).
imagesboolean–Publish the images (default true).
keyFeaturesboolean–Publish the key features (default true).
product_id–yesProduct id — required.
shipping_templateboolean–Publish the shipping template (default true).
shop_id–yesShop id — required.
tagsboolean–Publish the tags (default true).
titleboolean–Publish the title (default true).
variantsboolean–Publish the variants (default true).

No output schema declared.

No examples provided.

printify_resolve_copy ~182

Resolve one failed or uncertain source product in a durable copy job. Provide an existing target_product_id to verify the exact supported fields against the checkpoint and record it as copied. Or set verified_not_created:true only after checking the target shop manually; this allows one future retry through printify_copy_products. Requires confirm:true, never creates/publishes/deletes anything itself. An ambiguous write must never be blindly retried.

NameTypeReqDescription
confirmbooleanyes–
job_idstringyes–
source_product_idstringyes–
source_shop_id–yesSource shop ID; the token must have access to both shops in the same Printify account.
target_product_idstring––
target_shop_id–yesDifferent target shop ID. New products stay as drafts and are not published.
verified_not_createdboolean––

No output schema declared.

No examples provided.

Install

How do I install the Printify MCP by usefulapi server?

Printify MCP by usefulapi 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

# add to Claude Code
claude mcp add --transport http io-usefulapi-printify 'https://printify.usefulapi.io/mcp'
Common questions

What is the Printify MCP by usefulapi server?

Printify MCP by usefulapi is 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 Printify MCP by usefulapi server safe to use?

Printify MCP by usefulapi scores 18 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 Printify MCP by usefulapi server expose?

Printify MCP by usefulapi exposes 17 tools: printify_copy_products, printify_copy_status, printify_resolve_copy, printify_list_shops, printify_list_products, and 12 more. Their descriptions and schemas cost roughly 1,910 tokens of context every time the server is loaded.

Does the Printify MCP by usefulapi server require authentication?

Its publisher declares no required credentials for Printify MCP by usefulapi. We have not been able to confirm that against the live endpoint, and a server can require authorisation without declaring it here.

Is the Printify MCP by usefulapi server still maintained?

Printify MCP by usefulapi 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.