Home / MCP registry index / io.printdash/printdash

Printdash

io.printdash/printdash in the official MCP registry. Endpoint https://api.printdash.io/functions/v1/mcp.

The registry describes it as: Online printing for Australia: products, exact prices, quotes, artwork checks and orders.

We read its 58 tools on 2026-11-01. Nothing in them matched our tool-poisoning rules. It also sets server instructions, text a client puts in front of the model on connect; those were read too.

A clean read means these rules found nothing, not that the server is harmless. A server can change its tools at any time, which is why the index reads it again every week.

Connect it

The endpoint answers MCP over HTTP; that is how we read it. Add it to your client:

Claude Code

claude mcp add --transport http printdash https://api.printdash.io/functions/v1/mcp

Cursor: ~/.cursor/mcp.json

{
  "mcpServers": {
    "printdash": {
      "url": "https://api.printdash.io/functions/v1/mcp"
    }
  }
}

VS Code

code --add-mcp '{"name":"printdash","type":"http","url":"https://api.printdash.io/functions/v1/mcp"}'

Some servers ask you to sign in the first time a client connects, or want a key from the people who run them; the server's own docs say which.

Let Claude Code check servers as it adds them

With the free lazaretto-guard plugin installed, when Claude Code adds a server for you or writes one into an MCP config, the plugin reads the server's tools first and asks you if one of our rules matches. Install it, restart Claude Code, then ask it to run the command above.

Install lazaretto-guard

claude plugin marketplace add jamesdfinance-dev/lazaretto-plugins
claude plugin install lazaretto-guard@lazaretto-plugins

Tools it advertises

ping list_products search_products get_product match_options get_artwork_guide get_artwork_requirements price_job price_quantities estimate_delivery get_account set_context list_addresses list_orders get_order list_quotes get_quote create_address update_address set_default_address delete_address get_cart add_to_cart update_cart_line remove_cart_line clear_cart create_quote update_quote duplicate_quote delete_quote share_quote email_quote convert_quote_to_order request_custom_quote list_quote_requests get_quote_request cancel_quote_request get_referral_summary send_invite confirm request_artwork_upload attach_artwork attach_artwork_from_url attach_artwork_inline get_artwork_uploader_link check_artwork get_mockup list_artwork remove_artwork prepare_checkout place_order cancel_order reorder request_reorder get_invoice list_pending_approvals approve_order reject_order

Tool changes

We compare every full read of this server with the one before. No change in what its tools say has been seen since we started keeping this record on 2026-10-30.

Fingerprint of its tools at our last full read (2026-11-01): f916038eff0fa34f. A client can hash the tools it is served the same way and compare; the full value and a hash per tool are in this page as JSON.

Run this server? Show the check in your README

The badge reflects the latest weekly read:

Markdown

[![MCP tool check](https://lazaretto.dev/mcp-registry/io-printdash-printdash/badge.svg)](https://lazaretto.dev/mcp-registry/io-printdash-printdash)

How this was checked

Lazaretto connects to the endpoint the way any MCP client does, asks the server to introduce itself and list its tools, and reads every name, description, parameter schema and server instruction for tool poisoning: hidden directive blocks, orders to read local secrets, parameters built to carry secrets or the conversation out, orders that redirect another server's tools, and invisible characters. It never calls a tool. What we found across the registry.

To run the same check every time Claude Code adds a server, install the free lazaretto-guard plugin. Browse every server in the index.