Printags shop
REMOTE · STUDIO.PRINTAGS.COM
Prepare a cart of printed PVC, NFC and wood cards on the Printags shop; no account needed.
Available components
Last scanned (12 hours ago)
Scores higher than 53% of remote servers
Reachable. Last reached 5 Nov 2026.
Category E-commerce
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 Security74
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- No authorisation is required to call this server. Nothing on it is marked destructive, but we can't show that an anonymous caller can only read: full credit needs the server to list at least one tool and every tool to be verifiably read-only. We use a best-effort check of tool names and descriptions to tell read-only tools from tools that change things, so some genuinely read-only tools may not get full credit. Names that start with a read verb (get, list, read, search and similar) and accurate readOnlyHint annotations help. Meet that to earn full credit, or require authorisation. See how to fix → View diagnostics → Partial
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- 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
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability62
- AI-judged instruction clarity (good).Pass
- Context-footprint check failed: tool/resource definitions use about 1671 tokens (~238/item across 7 items; 7 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management3
- Stability observed for 1 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage82
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 46% of tool parameters carry a description.Partial
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 7 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 8 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Checks we ran (13)
- TLS certificate
- Authorization
- HTTPS
- HSTS header
- DNSSEC
- Transport
- Schema quality
- Stability
- Tool coverage
- Injection markers
- Destructive annotations
- Judged manipulation
- MCP protocol
Does not apply to this hosted endpoint (2)
- Supply Chain SecurityScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
- Provenance & TransparencyScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
The score does not measure everything. What the score does not measure →
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.
- 5 Nov 26 +1
- Stability: unverified → 0.03 ▲ functional
- 4 Nov 26 67
First indexed and scored.
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://studio.printags.com/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=printags.com | CN=WE1,O=Google Trust Services,C=US | 13 Sept 2026 | 12 Dec 2026 | ECDSA 256 | ECDSA-SHA256 | b106c1f1b4cd0bae0e73df9dd37c6f32 |
| SANs: printags.com, *.printags.com | ||||||
| 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 studio.printags.com. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | Trust anchor | 20326, 38696 | 8, 8 | Verified |
| com. | DS published | 19718 | 13 | Verified |
| printags.com. | No DS | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 200 |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://studio.printags.com/mcp | Verified | 200 | |
| http (plaintext) | http://studio.printags.com/mcp | HTTPS enforced | 301 | https://studio.printags.com/mcp |
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 →
create_upload Déposer un visuel : URL d'envoi ~171
Prépare le dépôt d'un visuel (PNG, JPEG ou PDF, 25 Mo max) à imprimer sur les cartes. Renvoie un `upload_id` et une URL de PUT valable 15 minutes : envoie-y les octets du fichier en un seul PUT, avec l'en-tête Content-Type du fichier (ex. curl -T visuel.png -H "Content-Type: image/png" <upload_url>). Cite ensuite l'`upload_id` dans prepare_cart. Un dépôt ne sert qu'une fois. Si tu ne peux pas faire de requête HTTP, utilise upload_file pour un petit fichier, ou prépare le panier sans visuel : la personne l'enverra elle-même depuis le Studio.
| Name | Type | Req | Description |
|---|---|---|---|
| content_type | string | yes | – |
| file_name | string | yes | – |
No output schema declared.
No examples provided.
get_order_status Suivre une commande ~129
Statut d'une commande du Studio d'après son JETON DE SUIVI (UUID), que la personne trouve dans l'e-mail de confirmation ou dans l'adresse de la page de suivi (/orders/track/<jeton>). Renvoie statut, paiement, articles et numéro de suivi du colis. Pas de référence CMD-… : elle ne suffit pas. Un statut « validé » ou « en production » n'est pas « expédié » : ne promets pas de date de livraison.
| Name | Type | Req | Description |
|---|---|---|---|
| tracking_token | string | yes | Le jeton de suivi de la commande (UUID). |
No output schema declared.
No examples provided.
list_products Lister les cartes du Studio ~133
Le catalogue du Studio (studio.printags.com) : cartes PVC avec ou sans NFC, MIFARE, bois. Pour chaque produit : `slug` (à citer partout), nom, description, puce, quantité minimale, paliers de prix unitaires HORS TAXES (le prix baisse avec la quantité) et `encodable` (la puce peut recevoir un lien ou un texte). À appeler d'abord : jamais de slug ni de prix de mémoire.
| Name | Type | Req | Description |
|---|---|---|---|
| locale | string | – | Langue de la personne : noms des produits, et page du Studio où elle arrivera. Celle de la conversation. |
No output schema declared.
No examples provided.
prepare_cart Préparer un panier et donner le lien ~238
Prépare un panier du Studio pour la personne et renvoie `claim_url`, un lien à lui donner. Elle l'ouvre : elle voit son panier et le BAT (épreuve) de ses cartes, l'approuve, saisit son adresse (et son numéro de TVA), choisit le transport et PAIE elle-même. Cet outil ne crée AUCUNE commande, n'envoie aucun e-mail, ne paie rien et n'approuve aucun BAT. Le lien est valable 48 heures et ne sert qu'une fois. Le prix vient du Studio. Les visuels sont facultatifs : ceux qui manquent, la personne les envoie depuis le Studio. Une ligne = un produit : un visuel pour toutes les cartes (front_upload_id…), des contenus de puce différents (encodings), ou un visuel par carte (cards). N'invente ni visuel, ni lien, ni texte de puce : demande ce qui manque.
| Name | Type | Req | Description |
|---|---|---|---|
| lines | array | yes | – |
| locale | string | – | Langue de la personne : noms des produits, et page du Studio où elle arrivera. Celle de la conversation. |
No output schema declared.
No examples provided.
quote_cart Chiffrer un panier ~171
Chiffre un panier avec les règles du Studio : total HT, TVA 20 %, total TTC, frais d'expédition hors de France (offerte en France). Les montants sont indicatifs : le paiement recalcule tout. La livraison Chrono et l'autoliquidation de TVA (professionnel de l'UE) se choisissent et se vérifient au paiement, sur le Studio, pas ici.
| Name | Type | Req | Description |
|---|---|---|---|
| country_code | string | – | Pays de livraison, ISO 3166-1 alpha-2 (défaut FR). Hors de France, des frais d'expédition s'ajoutent. |
| lines | array | yes | – |
| locale | string | – | Langue de la personne : noms des produits, et page du Studio où elle arrivera. Celle de la conversation. |
No output schema declared.
No examples provided.
upload_file Déposer un visuel : contenu en base64 ~99
Dépose directement un petit visuel (PNG, JPEG ou PDF, 3 Mo max) envoyé en base64 dans l'appel. Renvoie l'`upload_id` à citer dans prepare_cart. Pour un fichier plus gros, utilise create_upload ; sans moyen d'envoyer le fichier, prépare le panier sans visuel.
| Name | Type | Req | Description |
|---|---|---|---|
| content_base64 | string | yes | – |
| content_type | string | yes | – |
| file_name | string | yes | – |
No output schema declared.
No examples provided.
upload_visual Déposer le visuel joint à la conversation ~126
Dépose le visuel (PNG, JPEG ou PDF, 25 Mo max) que la personne a joint à la conversation ChatGPT, pour l'imprimer sur ses cartes. À utiliser dès qu'elle a joint un fichier. Renvoie l'`upload_id` à citer dans prepare_cart ; un dépôt ne sert qu'une fois. Sans fichier joint, prépare le panier sans visuel : la personne l'enverra elle-même depuis le Studio.
| Name | Type | Req | Description |
|---|---|---|---|
| file | object | yes | Le fichier joint par la personne, rempli par ChatGPT : ne jamais inventer ni modifier ces champs. |
No output schema declared.
No examples provided.
How do I install the Printags shop MCP server?
Printags shop is a hosted endpoint at https://studio.printags.com/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 · studio.printags.com
claude mcp add --transport http com-printags-shop 'https://studio.printags.com/mcp'
What is the Printags shop MCP server?
Printags shop is an MCP server listed in the public MCP registry as com.printags/shop. Prepare a cart of printed PVC, NFC and wood cards on the Printags shop; no account needed. This page covers its hosted endpoint (https://studio.printags.com/mcp).
Is the Printags shop MCP server safe to use?
Printags shop scores 68 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 Printags shop MCP server expose?
Printags shop exposes 7 tools: list_products, quote_cart, create_upload, upload_file, upload_visual, and 2 more. Their descriptions and schemas cost roughly 1,067 tokens of context every time the server is loaded.
Does the Printags shop MCP server require authentication?
No. We connected to Printags shop without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the Printags shop MCP server still maintained?
Printags shop 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.
What did VerifyMCP test on the Printags shop MCP server?
VerifyMCP ran 13 checks on Printags shop, covering TLS certificate, Authorization, HTTPS, HSTS header and 9 more. Supply Chain Security and Provenance & Transparency do not apply to a hosted endpoint, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.