Skip to content

Printify MCP by usefulapi

io.usefulapi/printifyusefulapi.iostreamable-httpv1.43.5Scanned

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

14 tools: 1 can delete or cancel things and 13 only read.

Tools: 1 delete, 0 irreversible, 0 write, 13 read.
  • Reads private data · 0
  • Reads text others write · 0
  • Can send data out · 1
  • No findings

The remote endpoint did not answer the last look. Remote posture

Anlyon alternative

1 of these tools change something. Run those as governed actions.

Declare what an action changes, and Anlyon puts it under a shared limit, binds every approval to the exact request, and grades the outcome. It works on any HTTPS API you can describe as an action.

Anlyon Radar does not run, proxy or govern this MCP server. A tool your own code calls directly is not routed through Anlyon and is not governed by it.

Import an OpenAPI spec →

What the Printify MCP by usefulapi can do

The Printify MCP by usefulapi is published by usefulapi.io, a domain the MCP Registry verified. It has 14 tools. It can delete or cancel things (1 tool: printify_publish_product). 13 tools only read.

1 tool can send data out of your system (printify_publish_product).

None of the fixed checks matched anything in its tool definitions. That is not a safety guarantee.

Last scanned Oct 25, 2026, version 1.43.5.

Tools

Grouped by what each tool does, most consequential first. Open one for its reasons and full description; descriptions are the publisher's own words.

14 tools

Deletes or cancels 1Claude Code: deny
  • printify_publish_productPublish a product to the shop's connected sales channel (e.g.Can send data outNo findings

    Why it is in this group

    • The name "printify_publish_product" says "publish": a word for a change that another call does not undo.
    • The server marks it destructive (destructiveHint: true).

    What it can reach

    • outboundThe name "printify_publish_product" says "publish": it sends or publishes something to other people.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • title: Publish product
    • destructiveHint: true
Only reads 13Show 13 read-only tools
  • printify_calculate_shippingGet a shipping price quote for a set of line items to a destination address.No findings

    Why it is in this group

    • The description's first verb is "get": a word for reading.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • title: Calculate shipping
    • readOnlyHint: true
  • printify_get_blueprintGet a single catalog blueprint's details.No findings

    Why it is in this group

    • The name "printify_get_blueprint" says "get": a word for reading.
    Description, as the server wrote it
    Get a single catalog blueprint's details. Printify REST: GET /v1/catalog/blueprints/{blueprint_id}.json.

    Annotations the server declares

    • title: Get blueprint
    • readOnlyHint: true
  • printify_get_orderGet a single order's full details, including `shipments` (carrier + tracking numbers).No findings

    Why it is in this group

    • The name "printify_get_order" says "get": a word for reading.
    Description, as the server wrote it
    Get a single order's full details, including `shipments` (carrier + tracking numbers). Printify REST: GET /v1/shops/{shop_id}/orders/{order_id}.json.

    Annotations the server declares

    • title: Get order
    • readOnlyHint: true
  • printify_get_print_providersList the print providers that can produce a given blueprint.No findings

    Why it is in this group

    • The name "printify_get_print_providers" says "get": a word for reading.
    Description, as the server wrote it
    List the print providers that can produce a given blueprint. Printify REST: GET /v1/catalog/blueprints/{blueprint_id}/print_providers.json.

    Annotations the server declares

    • title: Get blueprint print providers
    • readOnlyHint: true
  • printify_get_productGet a single product's full details (variants, images, print areas, publish status).No findings

    Why it is in this group

    • The name "printify_get_product" says "get": a word for reading.
    Description, as the server wrote it
    Get a single product's full details (variants, images, print areas, publish status). Printify REST: GET /v1/shops/{shop_id}/products/{product_id}.json.

    Annotations the server declares

    • title: Get product
    • readOnlyHint: true
  • printify_get_variantsList the variants (sizes, colors) a print provider offers for a blueprint.No findings

    Why it is in this group

    • The name "printify_get_variants" says "get": a word for reading.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • title: Get variants
    • readOnlyHint: true
  • printify_list_catalog_blueprintsList all blueprints (product types, e.g.No findings

    Why it is in this group

    • The name "printify_list_catalog_blueprints" says "list": a word for reading.
    Description, as the server wrote it
    List all blueprints (product types, e.g. 'Unisex T-Shirt') available in the Printify catalog. Printify REST: GET /v1/catalog/blueprints.json.

    Annotations the server declares

    • title: List catalog blueprints
    • readOnlyHint: true
  • printify_list_ordersList orders in a shop (paginated), optionally filtered by status or SKU.No findings

    Why it is in this group

    • The name "printify_list_orders" says "list": a word for reading.
    Description, as the server wrote it
    List orders in a shop (paginated), optionally filtered by status or SKU. Printify REST: GET /v1/shops/{shop_id}/orders.json.

    Annotations the server declares

    • title: List orders
    • readOnlyHint: true
  • printify_list_print_providersList all print providers in the Printify catalog.No findings

    Why it is in this group

    • The name "printify_list_print_providers" says "list": a word for reading.
    Description, as the server wrote it
    List all print providers in the Printify catalog. Printify REST: GET /v1/catalog/print_providers.json.

    Annotations the server declares

    • title: List print providers
    • readOnlyHint: true
  • printify_list_productsList products in a shop (paginated).No findings

    Why it is in this group

    • The name "printify_list_products" says "list": a word for reading.
    Description, as the server wrote it
    List products in a shop (paginated). Printify REST: GET /v1/shops/{shop_id}/products.json.

    Annotations the server declares

    • title: List products
    • readOnlyHint: true
  • printify_list_shopsList all shops connected to the Printify account.No findings

    Why it is in this group

    • The name "printify_list_shops" says "list": a word for reading.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • title: List shops
    • readOnlyHint: true
  • printify_list_uploadsList images uploaded to the account's media library (paginated).No findings

    Why it is in this group

    • The name "printify_list_uploads" says "list": a word for reading.
    Description, as the server wrote it
    List images uploaded to the account's media library (paginated). Printify REST: GET /v1/uploads.json.

    Annotations the server declares

    • title: List uploads
    • readOnlyHint: true
  • printify_list_webhooksList the webhooks configured for a shop.No findings

    Why it is in this group

    • The name "printify_list_webhooks" says "list": a word for reading.
    Description, as the server wrote it
    List the webhooks configured for a shop. Printify REST: GET /v1/shops/{shop_id}/webhooks.json.

    Annotations the server declares

    • title: List webhooks
    • readOnlyHint: true

This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.

Exfil surface

Which tools read private data, which read text someone else can write, and which can send data out. One of each is a path a prompt injection can use.

No private-data, untrusted-input, outbound path in this server alone: no tool is tagged private-data or untrusted-input.

Reads private data0
Reads files, mail, messages, databases, secrets, calendars or repositories.
Reads text others write0
Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
Can send data out1
Can carry data to people or systems: it sends, posts or publishes, or takes a recipient, channel or URL.

Other servers in the same agent add their own tools to these paths. Audit your whole setup to see them together.

Remote posture

What anyone on the internet sees at the remote endpoint: an anonymous initialize and tools/list, and the public OAuth metadata.

The remote endpoint did not answer the last look

Looked at Nov 20, 2026, 19:37 UTC, unchanged since Oct 29, 2026. No credentials were sent and no tool was called. What is looked at.

Reachable
no
HTTP status of an anonymous initialize
not observed
tools/list served without credentials
no
Tools that change things, listed without credentials
0
Protocol version
not observed
WWW-Authenticate on 401
not observed
resource_metadata in WWW-Authenticate
not observed
RFC 9728 protected resource metadata
not observed
Authorization servers
not observed
Legacy HTTP+SSE transport
no
Dynamic client registration
not observed
Client ID metadata documents
not observed

The probe stopped: The server redirected a POST to a different request.

Posture changes

  1. Oct 29, 2026
    • Reachable: yes to no
    • HTTP status of an anonymous initialize: 200 to none
    • tools/list served without credentials: yes to no
    • Tools that change things, listed without credentials: 1 to 0
    • Protocol version: 2025-06-18 to none
    • RFC 9728 protected resource metadata: https://printify.usefulapi.io/.well-known/oauth-protected-resource/mcp to none
    • Authorization servers: https://printify.usefulapi.io to none
    • Dynamic client registration: yes to not observed
    • Client ID metadata documents: no to not observed

Findings

Matches of fixed checks, with the text they matched.

No check matched anything in these tool definitions. That is not a safety guarantee.

History

Changes to its tool definitions and to its remote endpoint, newest first.

  1. PostureRemote posture changed. Reachable: yes -> no; HTTP status of an anonymous initialize: 200 -> none; tools/list served without credentials: yes -> no (and 6 more).View diff
    • Reachable: yes to no
    • HTTP status of an anonymous initialize: 200 to none
    • tools/list served without credentials: yes to no
    • Tools that change things, listed without credentials: 1 to 0
    • Protocol version: 2025-06-18 to none
    • RFC 9728 protected resource metadata: https://printify.usefulapi.io/.well-known/oauth-protected-resource/mcp to none
    • Authorization servers: https://printify.usefulapi.io to none
    • Dynamic client registration: yes to not observed
    • Client ID metadata documents: no to not observed

Install

Pinned to version 1.43.5. Values in angle brackets are yours to fill in.

claude mcp add --transport http printify https://printify.usefulapi.io/mcp
claude mcp add --transport http printify https://printify.usefulapi.io/mcp

Run in a terminal.

Claude Code permissions

Allow the reads, ask before a change or a way out, deny the deletes. Paste into .claude/settings.json.

.claude/settings.json
{
  "permissions": {
    "allow": [
      "mcp__printify__printify_list_shops",
      "mcp__printify__printify_list_products",
      "mcp__printify__printify_get_product",
      "mcp__printify__printify_list_orders",
      "mcp__printify__printify_get_order",
      "mcp__printify__printify_calculate_shipping",
      "mcp__printify__printify_list_catalog_blueprints",
      "mcp__printify__printify_get_blueprint",
      "mcp__printify__printify_get_print_providers",
      "mcp__printify__printify_get_variants",
      "mcp__printify__printify_list_print_providers",
      "mcp__printify__printify_list_webhooks",
      "mcp__printify__printify_list_uploads"
    ],
    "ask": [],
    "deny": [
      "mcp__printify__printify_publish_product"
    ]
  }
}

Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. A read that can send data out (it takes a URL, say) asks first too. It assumes the server is installed as printify. Review it before you use it.

Capability tags behind 1 rule
  • mcp__printify__printify_publish_product outbound

Pin

Keep the decision: fail CI when the tools change, follow every change, or show a badge.

Pin in CI

Fail a build when the tools you reviewed are not the tools the server serves today.

curl -s "https://radar.anlyon.com/api/v1/servers/io.usefulapi/printify/verify?hash=3f7e41b2e3a43df10bea88593d62f85e2e8c7ea75eda04bfc4aac8e550e70b28" | jq -e '.changed == false'

Pinned hash 3f7e41b2e3a4, from Oct 25, 2026, 23:19 UTC.

Watch

Get told when its tools change: a new tool, a new description, a new class.

https://radar.anlyon.com/servers/io.usefulapi/printify/changes.xml

An Atom feed. Works in any feed reader or Slack's RSS app.

Badge

Anlyon Radar badge for io.usefulapi/printify
[![Anlyon Radar](https://radar.anlyon.com/badge/io.usefulapi/printify.svg)](https://radar.anlyon.com/servers/io.usefulapi/printify)

Source: MCP Registry · repository. Synced Nov 20, 2026, 20:18 UTC.

Printify MCP by usefulapi: questions and answers

Answered from the scan above, not from the publisher's description.

Is the Printify MCP by usefulapi safe?

No scan can promise that. What its definitions show: 14 tools, 1 of which can change, send or delete something, and 0 findings from fixed checks. Allow the reads, ask before each change, and deny the deletes; the permissions block on this page does that.

Can the Printify MCP by usefulapi delete data?

Yes. 1 tool can delete, cancel or revoke something: printify_publish_product.

Can the Printify MCP by usefulapi do things that cannot be undone?

No tool is classed as irreversible: none of them sends, pays, publishes or merges, going by their definitions.

What tools does the Printify MCP by usefulapi have?

14 tools: 1 destructive, 13 read. printify_publish_product, printify_list_shops, printify_list_products, printify_get_product, printify_list_orders, printify_get_order, printify_calculate_shipping, printify_list_catalog_blueprints and 6 more.

Does the Printify MCP by usefulapi need sign-in or OAuth?

Its remote endpoint did not answer the last anonymous look.

Does the Printify MCP by usefulapi send data to outside services?

1 tool can carry data out (it sends, posts or publishes, or takes a recipient, channel or URL): printify_publish_product.

Has the Printify MCP by usefulapi changed its tools?

Not since Anlyon Radar started tracking it. Last scanned Oct 25, 2026.