Skip to content

MCP servers › io.printdash › printdash

MCP server · registry snapshot 2026-10-30 · last tested 2026-10-30

printdash MCP server

Registry name io.printdash/printdash

by printdash.io · domain (the registry's namespace rule)Website ↗

Online printing for Australia: products, exact prices, quotes, artwork checks and orders. — the publisher's description

1 of 2 record checks metRead-only · tools listed 2026-10-30version 0.6.0streamable HTTP58 tools

Summary

io.printdash/printdash is a remote MCP server listed in the official MCP registry at version 0.6.0, under the namespace of the domain printdash.io. On 2026-10-30 ProtocolProbe connected to it in read-only mode and read its inventory: 58 tools, 15 resources and 3 prompts.

Record checks

1 of 2 record checks met · 7 do not apply

  • met: Registry entry is active and says how to run it
  • not met: Source repository link opens
  • not applicable: Repository is not archived
  • not applicable: Code pushed to the repository in the 90 days before our check
  • not applicable: Repository publishes a security policy (SECURITY.md)
  • not applicable: Package names its licence with a standard (SPDX) identifier
  • not applicable: The version the registry lists can be installed and is not withdrawn
  • not applicable: npm package carries build provenance (attestation)
  • not applicable: No known critical or high advisory in the package or its dependencies
  • Not ranked by downloads: a remote server publishes no download figure
  • Not ranked by stars: no public GitHub repository

From public records, not a safety rating. Each check with its reason

Operate this server? Correct a fact · README badge · Run the checks yourself

Key facts

Runs
remote (hosted by the publisher)
Transport
streamable HTTP
Your own values
none declared (not a guarantee)
Sign-in
none needed to open a session
Tools
58
Last tested
2026-10-30

Tool list size

27,391 tokens on Claude Opus 5.5

Added to every request that loads this server's tools (58 tools). Counted with Anthropic's token counter on 2026-10-30, from the tool list we read on 2026-10-30. Median across 25,738 counted servers: 2,858 tokens. How it is counted

How a client gets in

Connects without signing in

Read from the server's public metadata on 2026-10-30 (api.printdash.io), in our read-only connection; no tool was called. It may have changed since. How it is read

Tool list at the three APIs

Not sent yet for this version (0.6.0).

Add to your client

Observed fact

This server accepted a session without any credential and lists 28 tools whose name or declaration suggests they change data (set_context, create_address, update_address, set_default_address, delete_address and 23 more). That is our reading of the names; we did not call them. Source: our connection, 2026-10-30.

How fresh this is

Live-tested
yes, a real session (not a text-only review)
Last tested
2026-10-30
Mode
read-only (no tool calls)
Latest version
0.6.0, published 2026-10-29 (registry, as of the 2026-10-30 snapshot)
First listed version
2026-10-29 (earliest version still in the registry; older removed versions would be earlier)
Registry data
snapshot 2026-10-30
Package and repository
checked 2026-10-30
Engine
mcp-runtime-engine@0.1.0 · sdk@1.32.0

Dead or stale signals

None found in the records we hold

Looked for and not found: deprecated in the registry. Does not apply: listed version cannot be installed or is withdrawn; repository link does not open; repository archived; no push in over 365 days. Each line is a dated fact from a public record. It does not say whether the server still works, and a record can change after the date shown.

Changes since the last refresh

New in the registry: not in the list of 2026-10-29, listed on 2026-10-30 with version 0.6.0 (published 2026-10-29).

Source: the official MCP Registry list on 2026-10-29 and on 2026-10-30.

What it is

What does this server offer?

Observed inventory
58tools
15resources
3prompts

None of its 58 tools are described as changing anything. For 58 the reading was uncertain, so no mark is shown.

  • “Checks that Printdash is reachable and says whether you are signed in.”

    Publisher declares: read-only yes · destructive no · idempotent yes · open-world no

    Takes no inputs.

  • “Every product Printdash sells (business cards, flyers, stickers, labels, booklets, signs, banners and more), with its id, a one-line description, its page and from_price: the starting price the site …”

    Publisher declares: read-only yes · destructive no · idempotent yes · open-world no

    Takes no inputs.

  • search_productson 290 other servers

    “Finds the Printdash products that match the customer's words ("A5 flyers", "round stickers", "pull up banner"), best first.”

    Publisher declares: read-only yes · destructive no · idempotent yes · open-world no

    1 input, 1 required
    • querystringrequired“The customer's words for what they want printed.”
  • “The whole option form for one Printdash product, as its product page offers it: every field in the order to ask, whether it is required, each option's id and label, defaults, quantity and custom size…”

    Publisher declares: read-only yes · destructive no · idempotent yes · open-world no

    1 input, 1 required
    • product_idstringrequired“A product id from list_products or search_products.”
  • match_options

    “Turns the customer's words ("velvet", "A5", "double sided", "500", "90 x 55mm", "round corners") into option ids for one product, given what is already chosen.”

    Publisher declares: read-only yes · destructive no · idempotent yes · open-world no

    3 inputs, 2 required
    • product_idstringrequired
    • phrasesarrayrequired“The customer's words, one option each: ["velvet", "A5", "double sided", "500"].”
    • chosenobject“What is already chosen, so options are filtered by it (finishes the chosen stock does not offer, combinations the supplier cannot make).”
  • get_artwork_guide

    “Printdash's artwork setup guides as Markdown (bleed and safe zone, print-ready PDFs, colour, double-sided, cut lines, spot finishes, lamination, stocks, white ink, booklets, folding, wide format, Ill…”

    Publisher declares: read-only yes · destructive no · idempotent yes · open-world no

    3 inputs
    • topicstring“A guide id (bleed, pdf-export, colour, double-sided, dieline, spot-finishes, lamination, stock-finishes, white-ink, booklets, folding, wide-format, export-illu…”
    • product_idstring“A product, for what its page says on the topic.”
    • configurationobject“The job, to size the product's lead (page size with bleed, pages, plate names).”
  • get_artwork_requirements

    “What a print-ready file must be for a product and configuration: finished size, bleed, safe zone, the PDF page size including bleed, pages or sides expected, the spot plate names a spot finish needs,…”

    Publisher declares: read-only yes · destructive no · idempotent yes · open-world no

    2 inputs, 1 required
    • product_idstringrequired
    • configurationobject“The job, as option ids from get_product.”
  • price_job

    “Prices one exact job with Printdash's pricing engine: a product id and a configuration of option ids (from get_product or match_options).”

    Publisher declares: read-only yes · destructive no · idempotent yes · open-world no

    4 inputs, 2 required
    • product_idstringrequired
    • configurationobjectrequired“The job, as option ids from get_product.”
    • postcodestring“An Australian postcode (four digits) for the delivered price.”
    • address_idstring“Signed in: a saved address id from list_addresses, instead of a postcode.”
  • price_quantities

    “The same job priced at up to 8 quantities (the price ladder), each from Printdash's pricing engine, with the delivered price when an Australian postcode is given.”

    Publisher declares: read-only yes · destructive no · idempotent yes · open-world no

    5 inputs, 3 required
    • product_idstringrequired
    • configurationobjectrequired“The job without its quantity (any quantity given is replaced).”
    • quantitiesarrayrequired“Up to 8 quantities, for example [250, 500, 1000, 2000].”
    • postcodestring“An Australian postcode (four digits) for the delivered price.”
    • address_idstring“Signed in: a saved address id from list_addresses, instead of a postcode.”
  • estimate_deliveryon 3 other servers

    “Whether Printdash delivers to an Australian postcode (or, signed in, a saved address) and, given the jobs being ordered, the delivery fee and the delivered total, priced the way checkout prices it.”

    Publisher declares: read-only yes · destructive no · idempotent yes · open-world no

    3 inputs
    • postcodestring“An Australian postcode (four digits) for the delivered price.”
    • address_idstring“Signed in: a saved address id from list_addresses, instead of a postcode.”
    • jobsarray“The jobs being ordered together; the fee depends on the order's value.”
  • “Who the signed-in customer is: name, company, pricing tier and its discount in percent (discount_percent 5 means 5% off, already in every price the pricing tools return), whether they are buying pers…”

    Publisher declares: read-only yes · destructive no · idempotent yes · open-world no

    Takes no inputs.

  • set_context

    “Switches the account between buying personally and buying as one of its Teams, as the account menu's Viewing as does on printdash.io.”

    Publisher declares: read-only no · destructive yes · idempotent yes · open-world no

    1 input, 1 required
    • team_idstring or nullrequired“A team_id from get_account's contexts, or null for personal.”
Show 46 more tools
  • list_addresseson 6 other servers

    “The saved delivery addresses in the current buying context, the default first, with the ids price_job and estimate_delivery take.”

    Publisher declares: read-only yes · destructive no · idempotent yes · open-world no

    Takes no inputs.

  • “The most recent orders in the current buying context, each with its status as the order page shows it, payment, total, tracking and items.”

    Publisher declares: read-only yes · destructive no · idempotent yes · open-world no

    1 input
    • limitinteger“How many, newest first (default 10).”
  • “One order by its order number: status and payment as the order page shows them, every item with its job status, tracking, dispatch, delivery address, whether it can still be cancelled, whether the in…”

    Publisher declares: read-only yes · destructive no · idempotent yes · open-world no

    1 input, 1 required
    • orderstringrequired“The order number (or the order id from its link).”
  • “The most recent saved quotes in the current buying context, each with its status as the Quotes list shows it, total (with delivery, as the Quotes list shows it), expiry and link.”

    Publisher declares: read-only yes · destructive no · idempotent yes · open-world no

    1 input
    • limitinteger“How many, newest first (default 10).”
  • “One saved quote by its quote number: status, lines with their quoted quantities, the lines' subtotal, delivery and the total with delivery as the quote page shows it, expiry, the public share link if…”

    Publisher declares: read-only yes · destructive no · idempotent yes · open-world no

    1 input, 1 required
    • quotestringrequired“The quote number (or the quote id from its link).”
  • create_address

    “Saves an Australian delivery address to the address book in the current buying context (names, street, suburb, state code, four-digit postcode, optional company, mobile and type), optionally as the d…”

    Publisher declares: read-only no · destructive no · idempotent no · open-world no

    11 inputs, 6 required
    • first_namestringrequired
    • last_namestringrequired
    • company_namestring
    • address_line1stringrequired“Street address.”
    • address_line2string
    • citystringrequired“Suburb or town.”
    • statestringrequired“NSW, VIC, QLD, SA, WA, TAS, NT or ACT.”
    • postal_codestringrequired“Four-digit Australian postcode.”
    • mobilestring
    • typestring
    • set_as_defaultboolean“Make it the default address for this buying context.”
  • update_addresson 1 other server

    “Changes the fields given on one saved address (from list_addresses); the rest stay.”

    Publisher declares: read-only no · destructive yes · idempotent yes · open-world no

    11 inputs, 1 required
    • address_idstringrequired“An address id from list_addresses.”
    • first_namestring
    • last_namestring
    • company_namestring
    • address_line1string“Street address.”
    • address_line2string
    • citystring“Suburb or town.”
    • statestring“NSW, VIC, QLD, SA, WA, TAS, NT or ACT.”
    • postal_codestring“Four-digit Australian postcode.”
    • mobilestring
    • typestring
  • set_default_address

    “Makes one saved address the default for the current buying context; checkout and new quotes start from it.”

    Publisher declares: read-only no · destructive yes · idempotent yes · open-world no

    1 input, 1 required
    • address_idstringrequired
  • delete_addresson 1 other server

    “Prepares deleting one saved address: returns the summary to show the customer and a confirmation_token.”

    Publisher declares: read-only no · destructive yes · idempotent no · open-world no

    1 input, 1 required
    • address_idstringrequired
  • “The cart in the current buying context: each line with its line_id, job summary, price inc GST and whether it has artwork, the total before delivery, and the checkout link.”

    Publisher declares: read-only yes · destructive no · idempotent yes · open-world no

    Takes no inputs.

  • “Prices one job with Printdash's pricing engine (product id and a configuration of option ids, as price_job takes them) and puts it in the cart exactly as the product page's Add to cart does.”

    Publisher declares: read-only no · destructive no · idempotent no · open-world no

    2 inputs, 2 required
    • product_idstringrequired
    • configurationobjectrequired“The job, as option ids from get_product.”
  • update_cart_line

    “Changes one cart line's options (only what is given: a new quantity, stock, finish or size) and re-prices it with the pricing engine.”

    Publisher declares: read-only no · destructive yes · idempotent yes · open-world no

    2 inputs, 2 required
    • line_idstringrequired“A line_id from get_cart.”
    • configurationobjectrequired“Only the options that change, as option ids: a new quantity, stock, finishing ids or size.”
  • remove_cart_line

    “Removes one line from the cart by its line_id.”

    Publisher declares: read-only no · destructive yes · idempotent yes · open-world no

    1 input, 1 required
    • line_idstringrequired
  • “Removes every line from the cart in the current buying context.”

    Publisher declares: read-only no · destructive yes · idempotent yes · open-world no

    Takes no inputs.

  • “Saves a new quote with a quote number from up to 20 jobs (each a product id and configuration, priced by the engine first), with an optional saved address for delivery, pickup where the account has i…”

    Publisher declares: read-only no · destructive no · idempotent no · open-world no

    5 inputs, 1 required
    • linesarrayrequired“The jobs, each priced by the engine before anything is saved.”
    • address_idstring“A saved address id for delivery (list_addresses).”
    • fulfilmentstring“pickup only where the account has pickup (estimate_delivery says pickup_available).”
    • referencestring“The customer's order reference or job name.”
    • notesstring
  • update_quoteon 2 other servers

    “Changes a saved quote in place: lines to change (line_id plus only the options that change) or add (product_id and configuration), lines to remove, the reference, notes or delivery address.”

    Publisher declares: read-only no · destructive yes · idempotent yes · open-world no

    6 inputs, 1 required
    • quotestringrequired“The quote number (or the quote id from its link).”
    • linesarray
    • remove_line_idsarray
    • referencestring or null
    • notesstring or null
    • address_idstring or null“A saved address id, or null to clear it.”
  • duplicate_quote

    “Saves a copy of a quote as a new quote with its own number, every line re-priced today (artwork is not copied).”

    Publisher declares: read-only no · destructive no · idempotent no · open-world no

    1 input, 1 required
    • quotestringrequired“The quote number (or the quote id from its link).”
  • delete_quote

    “Prepares deleting a saved quote for good: returns the summary to show the customer and a confirmation_token.”

    Publisher declares: read-only no · destructive yes · idempotent no · open-world no

    1 input, 1 required
    • quotestringrequired“The quote number (or the quote id from its link).”
  • share_quote

    “Makes, or returns the existing, public link for a saved quote: the page where the customer's client can view and approve it, and pay online when allow_payment is on.”

    Publisher declares: read-only no · destructive yes · idempotent yes · open-world no

    2 inputs, 1 required
    • quotestringrequired“The quote number (or the quote id from its link).”
    • allow_paymentboolean“Let the recipient pay online from the link.”
  • email_quote

    “Prepares emailing a saved quote's public link to someone (usually the customer's client): returns the summary to show the customer and a confirmation_token.”

    Publisher declares: read-only no · destructive yes · idempotent no · open-world yes

    5 inputs, 2 required
    • quotestringrequired“The quote number (or the quote id from its link).”
    • recipient_emailstringrequired“Who to send it to (not the customer's own address).”
    • recipient_namestring
    • recipient_businessstring
    • include_brandingboolean“Show the customer's own branding on the public page (default true).”
  • convert_quote_to_order

    “Puts a saved quote's lines in the cart, as the quote page's Convert to order does, and returns the checkout link.”

    Publisher declares: read-only no · destructive yes · idempotent yes · open-world no

    1 input, 1 required
    • quotestringrequired“The quote number (or the quote id from its link).”
  • request_custom_quoteon 1 other server

    “Prepares a custom quote request for a job the catalogue does not cover (description, quantities, size, sides, stock, finishing, deadline, similar product, delivery address): returns the summary to sh…”

    Publisher declares: read-only no · destructive yes · idempotent no · open-world yes

    9 inputs, 2 required
    • descriptionstringrequired“The job in the customer's words: what it is, size, material, finish.”
    • quantitiesarrayrequired
    • sizestring“Finished size, for example 90 x 55mm or A5.”
    • sidesinteger
    • stockstring
    • finishingstring
    • deadlinestring“Date needed, YYYY-MM-DD.”
    • similar_product_idstring“The closest catalogue product, if any.”
    • address_idstring“A saved address id for delivery.”
  • list_quote_requestson 1 other server

    “The customer's custom quote requests in the current buying context, newest first, each with its status as /quotes shows it and the quote it became, if any.”

    Publisher declares: read-only yes · destructive no · idempotent yes · open-world no

    Takes no inputs.

  • get_quote_request

    “One custom quote request by its request number: what was asked for, its status, whether it can still be cancelled, and the quote it became.”

    Publisher declares: read-only yes · destructive no · idempotent yes · open-world no

    1 input, 1 required
    • requeststringrequired“The request number (or the request id from its link).”
  • cancel_quote_request

    “Cancels a custom quote request that is still pending review.”

    Publisher declares: read-only no · destructive yes · idempotent yes · open-world no

    1 input, 1 required
    • requeststringrequired“The request number (or the request id from its link).”
  • get_referral_summary

    “The customer's referral code and link, how many customers and orders they have referred, their credit balance and commission.”

    Publisher declares: read-only yes · destructive no · idempotent yes · open-world no

    Takes no inputs.

  • “Prepares emailing someone an invitation with the customer's referral link: returns the summary to show the customer and a confirmation_token.”

    Publisher declares: read-only no · destructive yes · idempotent no · open-world yes

    1 input, 1 required
    • emailstringrequired“Who to invite (not the customer's own address).”
  • “Carries out an action prepared by delete_address, delete_quote, email_quote, request_custom_quote, send_invite, prepare_checkout (placing the order), cancel_order, request_reorder, approve_order or r…”

    Publisher declares: read-only no · destructive yes · idempotent yes · open-world yes

    2 inputs, 2 required
    • confirmation_tokenstringrequired“The confirmation_token a prepare tool returned.”
    • idempotency_keystringrequired“A UUID you generate for this confirmation; reuse it only to retry the same one.”
  • request_artwork_upload

    “For a client that holds the file (Claude Code, Cursor, a script): returns a signed upload_url to PUT the file's bytes to, and an upload_id for attach_artwork.”

    Publisher declares: read-only no · destructive no · idempotent no · open-world no

    4 inputs, 3 required
    • targetobjectrequired“Where the artwork goes.”
    • file_namestringrequired“The file's name with its extension: business-card.pdf.”
    • size_bytesintegerrequired“The file's size in bytes (up to 700 MB).”
    • content_typestring“Optional; the type is decided by the extension, as the site's uploaders do.”
  • attach_artwork

    “After the file has been PUT to request_artwork_upload's upload_url: puts it on the line (in the design and side chosen then, replacing a file already in that slot), makes the page 1 and page 2 previe…”

    Publisher declares: read-only no · destructive yes · idempotent no · open-world no

    1 input, 1 required
    • upload_idstringrequired“The upload_id request_artwork_upload returned.”
  • attach_artwork_from_url

    “Fetches the file at an https link (a Canva, Figma or design tool export, Dropbox or Drive download link, a signed storage URL) up to 700 MB and attaches it like attach_artwork: target (cart_line, quo…”

    Publisher declares: read-only no · destructive yes · idempotent no · open-world yes

    3 inputs, 2 required
    • targetobjectrequired“Where the artwork goes.”
    • urlstringrequired“An https link that downloads the file itself (not a page showing it).”
    • file_namestring“The name to store it under, with its extension, when the link's own name has none.”
  • attach_artwork_inline

    “For programmatic clients only: attaches a file sent as base64 in data_base64, up to 10 MB, like attach_artwork (target, file_name with its extension).”

    Publisher declares: read-only no · destructive yes · idempotent no · open-world no

    3 inputs, 3 required
    • targetobjectrequired“Where the artwork goes.”
    • file_namestringrequired“The file's name with its extension.”
    • data_base64stringrequired“The file's bytes, base64-encoded, up to 10 MB decoded.”
  • get_artwork_uploader_link

    “The printdash.io page whose own uploader takes artwork for this line: checkout for a cart line, the quote page for a saved quote's line, the order page for an order job.”

    Publisher declares: read-only yes · destructive no · idempotent yes · open-world no

    1 input, 1 required
    • targetobjectrequired“Where the artwork goes.”
  • check_artwork

    “Runs Printdash's file checks on a line's artwork, the same ones the product page and checkout show: page size against the ordered size, pages against sides or booklet pages, ink to the edge for bleed…”

    Publisher declares: read-only yes · destructive no · idempotent yes · open-world no

    1 input, 1 required
    • targetobjectrequired“Where the artwork goes.”
  • get_mockup

    “The 3D mockup of a line's artwork on the product, as an image.”

    Publisher declares: read-only yes · destructive no · idempotent yes · open-world no

    1 input, 1 required
    • targetobjectrequired“Where the artwork goes.”
  • list_artwork

    “The files on a cart line, quote line or order job, in order, with which file and page is each design's front and back (as the site resolves them), how many designs are ready, whether the artwork can …”

    Publisher declares: read-only yes · destructive no · idempotent yes · open-world no

    1 input, 1 required
    • targetobjectrequired“Where the artwork goes.”
  • remove_artwork

    “Takes artwork off a line: one design's file (design, and side for one face only), or on a one-design job the front, the back, or (no side) every file.”

    Publisher declares: read-only no · destructive yes · idempotent yes · open-world no

    1 input, 1 required
    • targetobjectrequired“The line, and the design (and side, for one face only) to remove.”
  • prepare_checkouton 5 other servers

    “Checkout's review of the whole cart in the current buying context, as printdash.io's checkout shows it: every line with its artwork state and Printdash's file notices, delivery to a saved address (ad…”

    Publisher declares: read-only yes · destructive no · idempotent yes · open-world no

    7 inputs
    • address_idstring“A saved address id for delivery (list_addresses).”
    • fulfilmentstring“pickup only where the account has it (pickup_available).”
    • referencestring“The order reference, required as at checkout: a name for this order.”
    • notesstring“Notes for Printdash's team about this order.”
    • po_numberstring“A Team on account: the purchase order number (required when the Team says so).”
    • is_whitelabelboolean“Remove Printdash Branding, as the checkout switch.”
    • payment_methodstring“A request: a Team with approved terms orders on account unless card is asked for; Printdash decides.”
  • “Places the order prepare_checkout summarised, after the customer has seen that summary and said yes.”

    Publisher declares: read-only no · destructive yes · idempotent yes · open-world yes

    2 inputs, 2 required
    • confirmation_tokenstringrequired“The confirmation_token prepare_checkout returned.”
    • idempotency_keystringrequired“A UUID you generate for this order; reuse it only to retry the same one.”
  • “Prepares cancelling one order: returns the summary to show the customer and a confirmation_token.”

    Publisher declares: read-only no · destructive yes · idempotent no · open-world yes

    1 input, 1 required
    • orderstringrequired“The order number (or the order id from its link).”
  • “Turns one job from a past order (item_id from get_order, where can_reorder is true) back into a configuration and prices it at today's price, optionally at another quantity, exactly as price_job does.”

    Publisher declares: read-only yes · destructive no · idempotent yes · open-world no

    3 inputs, 1 required
    • orderstringrequired“The order number (or the order id from its link).”
    • item_idstring“The job's item_id from get_order (optional on a one-job order).”
    • quantityinteger“Another quantity; omit for the same.”
  • request_reorder

    “For a job on a past order that Printdash's team priced (reorder_by_request in get_order): prepares the order page's reorder request, at the same or another quantity with optional notes, and returns t…”

    Publisher declares: read-only no · destructive no · idempotent no · open-world yes

    4 inputs, 1 required
    • orderstringrequired“The order number (or the order id from its link).”
    • item_idstring“The job's item_id from get_order (optional on a one-job order).”
    • quantityinteger
    • notesstring“Any change to the specs, in the customer's words.”
  • “The tax invoice for one order as a PDF attached to the result, once the order is invoiced (paid, or on a Team's account once approved).”

    Publisher declares: read-only yes · destructive no · idempotent yes · open-world no

    1 input, 1 required
    • orderstringrequired“The order number (or the order id from its link).”
  • list_pending_approvalson 8 other servers

    “For a Team owner: every held order of each Team they own, oldest first, with who placed it, the total, whether it is on account, its items and its page.”

    Publisher declares: read-only yes · destructive no · idempotent yes · open-world no

    Takes no inputs.

  • approve_orderon 1 other server

    “For a Team owner: prepares approving one held order (from list_pending_approvals) and returns the summary to show the customer and a confirmation_token.”

    Publisher declares: read-only no · destructive yes · idempotent no · open-world yes

    1 input, 1 required
    • orderstringrequired“The order number (or the order id from its link).”
  • reject_order

    “For a Team owner: prepares rejecting one held order, with an optional reason the member who placed it is told, and returns the summary to show the customer and a confirmation_token.”

    Publisher declares: read-only no · destructive yes · idempotent no · open-world yes

    2 inputs, 1 required
    • orderstringrequired“The order number (or the order id from its link).”
    • reasonstring“Why, in the owner's words; the member who placed it is told.”

Each quoted sentence is the first sentence of the publisher’s own description. The kind of tool and the “changes data” mark are our AI model’s reading of that description, not something we tested: two differently worded runs had to agree, otherwise no label is shown, and nobody has checked them by hand. A tool without the “changes data” mark is described as only reading, searching or calculating, or the two runs did not agree. No tool was called. Read the publisher’s full description before relying on it. “Publisher declares” lists the hints the server itself sends with the tool (MCP annotations: read-only, destructive, idempotent, open-world); they are the publisher's claims, not checked by us. Inputs are the parameters in the tool's own input schema: name, declared type, whether it is required, and the first sentence of its description. Read 2026-10-30.

How well are its tools described?

Features #4 and #5

How clearly this server's own tool descriptions say what a tool does, and how consistent its tool list is. The first part is an AI model's yes/no reading of each description; the second part is counted. We do not turn it into a grade.

Descriptions

AI reading of each description

No AI reading was available for this server's tools (the two runs did not agree, or the listing was not reviewed).

Counted from the listing

Parameters with a description
75% of 128
Tools with a description
100% of 58
Typical description length
420 characters

The tool set

Counted from the listing

Tools
58
Size of the list
about 40,465 tokens for an agent to load (characters ÷ 4)
Naming
55 of 58 names use snake_case

AI reading: easy to mix up

No pair found.

The AI items cover 0 of 58 tools: for a tool where two differently worded runs disagreed, that item is left out. They were not checked by hand, and no tool was called. “Easy to mix up” means two tools whose names or descriptions overlap without saying how they differ; the AI found none, comparing tools within groups of 40. We do not rate whether the tool set is complete or whether side effects are spelled out, because our AI reading of those was not reliable enough.

How do I add it to my client?

Config from the registry entry

From the remote endpoint (Streamable HTTP)

We connected to this URL on 2026-10-30 (a read-only session: no tool was called).

Add to CursorAn install link in the format Cursor documents, holding the Cursor config below.

Claude Desktop or claude.ai
Settings → Connectors → Add custom connector, then paste:
https://api.printdash.io/functions/v1/mcp
Cursor · .cursor/mcp.json in a project, or ~/.cursor/mcp.json
{
  "mcpServers": {
    "printdash": {
      "url": "https://api.printdash.io/functions/v1/mcp"
    }
  }
}
VS Code · .vscode/mcp.json
{
  "servers": {
    "printdash": {
      "type": "http",
      "url": "https://api.printdash.io/functions/v1/mcp"
    }
  }
}
VS Code (command line) · Bash or zsh terminal (macOS, Linux)
code --add-mcp '{"name":"printdash","type":"http","url":"https://api.printdash.io/functions/v1/mcp"}'
Claude Code
claude mcp add --transport http printdash https://api.printdash.io/functions/v1/mcp
Cline · cline_mcp_settings.json (Cline CLI: ~/.cline/data/settings/; in the editor: MCP Servers → Configure → Configure MCP Servers)
{
  "mcpServers": {
    "printdash": {
      "type": "streamableHttp",
      "url": "https://api.printdash.io/functions/v1/mcp",
      "disabled": false,
      "autoApprove": []
    }
  }
}
Gemini CLI · ~/.gemini/settings.json, or .gemini/settings.json in a project
{
  "mcpServers": {
    "printdash": {
      "httpUrl": "https://api.printdash.io/functions/v1/mcp"
    }
  }
}
OpenAI Codex · ~/.codex/config.toml, or .codex/config.toml in a trusted project
[mcp_servers.printdash]
url = "https://api.printdash.io/functions/v1/mcp"
Zed · Zed settings file (command: zed: open settings file)
{
  "context_servers": {
    "printdash": {
      "url": "https://api.printdash.io/functions/v1/mcp"
    }
  }
}
Try it in the MCP Inspector · runs on your machine, opens in your browser · Node 22.19+
npx @modelcontextprotocol/inspector@2.11.0 --server-url https://api.printdash.io/functions/v1/mcp --transport http
  • The server runs on the operator's infrastructure; it may ask you to sign in when you first connect.
  • Zed's docs we read on 2026-10-26 describe remote servers by URL and do not name the transport.
  • The MCP Inspector lists the server's tools, resources and prompts; a tool you call there runs for real.

Built from the server's registry entry with each client's documented format (checked 2026-10-14; the Cursor link and the VS Code command 2026-10-19; the MCP Inspector command 2026-10-21; Cline, Gemini CLI, OpenAI Codex and Zed 2026-10-26). Values in < > are yours to fill in; this page never contains a key. Where the server needs a setting the entry does not declare, it can still fail to start.

Does the registry listing match what we found?

Feature #6

The registry checks an entry when it is published (each new version), and nothing re-checks it on a schedule. A difference below is about the listing, not a judgement of the publisher.

Registry saysWe foundResultSource · date
Remote endpoint api.printdash.io/functions/v1/mcpSession openedmatchesour test · 2026-10-30
No credential declared as requiredOpened a session without any credentialmatchesour test · 2026-10-30

Choosing

Record checks

Public records · not a safety rating

1 of 2 record checks met · 7 do not apply

  • Not ranked by downloads: a remote server publishes no download figure
  • Not ranked by stars: no public GitHub repository
  • MetRegistry entry is active and says how to run itActive, with a package or a remote address.
  • Not metSource repository link opensThe registry entry gives no repository link.What changes this check: This check opens the repository link in the registry entry. GitHub's documentation describes changing a repository's visibility in its Settings, under Danger Zone, Change visibility. GitHub: setting repository visibility
  • Does not applyRepository is not archivedNo public GitHub repository to read.
  • Does not applyCode pushed to the repository in the 90 days before our checkNo public GitHub repository to read.
  • Does not applyRepository publishes a security policy (SECURITY.md)No public GitHub repository to read.
  • Does not applyPackage names its licence with a standard (SPDX) identifierRemote server: it ships no package.
  • Does not applyThe version the registry lists can be installed and is not withdrawnRemote server: it ships no package.
  • Does not applynpm package carries build provenance (attestation)Remote server: it ships no package.
  • Does not applyNo known critical or high advisory in the package or its dependenciesRemote server: it ships no package.

Read from public records only: the registry entry, npm/PyPI, GitHub and advisory databases, checked 2026-10-30. No tool was called. Only “met” and “not met” are counted, so the total differs between servers; a check that does not apply or that we could not run is listed, never counted against it. It is not a safety rating, and the same rules apply to every server. How each check works · Leaderboards · How we stay neutral

Common questions about io.printdash/printdash

Answered from the data above

Who publishes io.printdash/printdash?

The registry ties the namespace io.printdash to the domain printdash.io; only its owner can publish under it. These are facts from the registry and GitHub, not a rating.

Does io.printdash/printdash need an API key or sign-in?

It opened a session without any credential on 2026-10-30. The registry entry declares no required credential; no declaration is not a guarantee.

Has io.printdash/printdash been security tested?

Partly. 4 of the 15 checks that apply to it were exercised. It accepted a session without any credential and lists tools whose names suggest they change data. We did not call them. ProtocolProbe publishes no security verdict for a named server.

Found this page useful?

Anonymous · no sign-in

A quick, anonymous reaction — no account, no email. One per kind from your browser. The tally updates when the page is next refreshed, and it is only a rough count, never a safety rating or a measured number of people.

Compare with another server

Side by side: registry entry, our read-only session, the tools and the 18 classification fields. Same values as each page; no score.

Security testing

What did we test, and what did we leave out?

18 checks · features #1, #2

Open without sign-in

It accepted a session without any credential and lists tools whose names suggest they change data. We did not call them. No security score is given; a check we did not run is never counted as passed.

The 18 checks at a glanceour test · 2026-10-30
  1. Inventory: exercised
  2. Hidden instructions: exercised
  3. Real execution: not run · our policy
  4. Secret leak: not run · nothing to check it against
  5. Internal addresses: not run · our policy
  6. Unconfirmed changes: not run · our policy
  7. Bad input: not run · our policy
  8. Model requests: not run · nothing to check it against
  9. Sensitive questions: not run · nothing to check it against
  10. Folder boundary: not run · our policy
  11. Log leaks: not run · nothing to check it against
  12. Hidden content: exercised
  13. Fake assistant turns: exercised
  14. Token passthrough: not applicable
  15. Token audience: not applicable
  16. Sign-in redirect: not run · our policy
  17. Consent handling: not testable from outside
  18. Sign-in metadata: not applicable

4 exercised11 not run (reason given)3 not applicable

Each check ends in exactly one state: exercised, not run (with the reason), or not applicable (with the reason). 4 of the 15 checks that apply to it were exercised. We do not publish security-check outcomes for named servers.

Exercised · 4
  • 1Inventory
    tool-list
    Reads the declared tools, resources and prompts.exercised
  • 2Hidden instructions
    description-poisoning
    Looks for hidden instructions in tool descriptions.exercised
  • 12Hidden content
    audience-hiding
    Checks resources that hide content from the user.exercised
  • 13Fake assistant turns
    fake-assistant-turn
    Checks prompts that pose as the assistant's own words.exercised
Not run, with the reason · 11
  • 3Real execution
    real-execution
    Calls a tool and checks what really happens.This check calls the server's tools. ProtocolProbe calls no server's tools for anything it publishes; an operator can run this check on their own server with our self-test command.not run · our policy
  • 4Secret leak
    canary-leak
    Plants a fake secret and checks whether it leaks.This check needs at least one successful tool call to have something to check, and no tool was called.not run · nothing to check it against
  • 5Internal addresses
    ssrf
    Checks whether a tool can be steered to internal addresses.This check calls the server's tools. ProtocolProbe calls no server's tools for anything it publishes; an operator can run this check on their own server with our self-test command.not run · our policy
  • 6Unconfirmed changes
    write-without-confirmation
    Checks whether tools that change data act without asking.This check calls the server's tools. ProtocolProbe calls no server's tools for anything it publishes; an operator can run this check on their own server with our self-test command.not run · our policy
  • 7Bad input
    error-handling
    Sends bad input and watches how the server answers.This check calls the server's tools. ProtocolProbe calls no server's tools for anything it publishes; an operator can run this check on their own server with our self-test command.not run · our policy
  • 8Model requests
    sampling
    Checks whether the server asks the client's model to act for it.This check needs at least one successful tool call to have something to check, and no tool was called.not run · nothing to check it against
  • 9Sensitive questions
    elicitation-sensitive-data
    Checks whether the server asks users for sensitive data.This check needs at least one successful tool call to have something to check, and no tool was called.not run · nothing to check it against
  • 10Folder boundary
    root-boundary
    Checks whether the server reaches outside the folders it was given.This check calls the server's tools. ProtocolProbe calls no server's tools for anything it publishes; an operator can run this check on their own server with our self-test command.not run · our policy
  • 11Log leaks
    logging-side-channel
    Checks whether log messages carry data they should not.This check needs at least one successful tool call to have something to check, and no tool was called.not run · nothing to check it against
  • 16Sign-in redirect
    open-redirect
    Checks the sign-in redirect for abuse.Testing the sign-in redirect means sending probes to the operator's sign-in service, which we do not do.not run · our policy
  • 17Consent handling
    confused-deputy
    Checks consent handling when one service acts for another.Depends on the operator's own consent screen, which differs per server and cannot be tested from outside.not testable from outside
Does not apply to this server · 3
  • 14Token passthrough
    token-passthrough
    Checks whether the server forwards a user's token to other services.The server opened a session without sign-in, so there is no token flow to check.not applicable
  • 15Token audience
    token-audience-validation
    Checks whether tokens meant for another service are accepted.The server opened a session without sign-in, so there is no token flow to check.not applicable
  • 18Sign-in metadata
    oauth-url-scheme
    Checks the published sign-in metadata for unsafe URLs.No sign-in (OAuth) metadata is published, so there are no sign-in addresses to check.not applicable

Source: our own test, 2026-10-30, mcp-runtime-engine@0.1.0. Which checks count and why follows our published scoring model.

What happened during the test?

Feature #8

The steps in order, as the test record holds them.

  1. 0 msStarted a read-only session with the server's remote endpoint
  2. 4,778 msConnected after 0 redirects. No credential was sent or needed.
  3. Read the inventory: 58 tools, 15 resources, 3 prompts.
  4. 43,797 msFinished: 4 checks exercised.

Reference

How is it classified?

18 fields

One value per field, each with its source. Fields written by AI models are marked. A field with no value says why.

TopicAI-classified
pending: added in a later update
listed 2026-10-30; not classified yet
Pricing modelAI-classified
pending: added in a later update
the website is not read yet
Programming language
does not apply
no existing GitHub repository (server declares no repository link, so there is nothing to fetch)
Hosting type
registry · 2026-10-30
MCP capability
prompts, resources, tools
our test · 2026-10-30
Transport
streamable HTTP
registry · 2026-10-30
Required credentials
none declared
registry · 2026-10-30 · no declaration is not a guarantee
Package registry
does not apply
remote-only server: no package is shipped, so there is no package registry
Freshness
0–30 days
registry updatedAt · 2026-10-30
Lifecycle status
registry · 2026-10-30
License class
does not apply
remote-only server: ships no package, so there is nothing to look up in a package registry
Integrity hash
does not apply
remote-only server: ships no package, so there is nothing to look up in a package registry
Signature / provenance
does not apply
remote-only server: ships no package, so there is nothing to look up in a package registry
Dependency advisories
does not apply
ships no package, so there are no dependencies to audit
Popularity
does not apply
remote-only server: ships no package, so there is nothing to look up in a package registry
Publisher signals
not stated
no readable GitHub owner to describe
Maintenance
does not apply
server declares no repository link, so there is nothing to fetch
Environment
the publisher's infrastructure
where it runs, from the hosting type · 2026-10-30

“Not stated” means the source did not state it; “does not apply” means it does not apply to this kind of server; “our limit” means our own lookup failed. A linked value opens the directory filtered to the same value.

Cite or correct this page

Sources and corrections

Suggested citation

ProtocolProbe. “io.printdash/printdash: MCP server record.” Data checked 2026-10-30. https://protocolprobe.com/mcp/servers/io.printdash/printdash

Figures are valid for the date shown. Our facts on this page are CC BY 4.0: reuse them with a link and the check date. Quoted text (the publisher’s descriptions, website quotes, tool names) is not ours to license.

As JSON: this record in the API · API documentation.

Badge for your README

ProtocolProbe: 1 of 2 record checks met

[![ProtocolProbe](https://protocolprobe.com/api/v1/badge/io.printdash/printdash)](https://protocolprobe.com/mcp/servers/io.printdash/printdash)

It shows this server's record-check count: facts from public records, no tool called. It is not a security rating or a pass. It links here and updates after each data reload.

Something wrong, or is this yours?

If a fact here is wrong, tell us and we will re-check it. If you operate this server, you can run our checks on it yourself with the free self-test command; we call no server’s tools ourselves for anything shown here.

Write to hello@protocolprobe.com · corrections log · methodology