Kuaidi100 launched China's first MCP-protocol-compatible logistics information service platform. The core API services of Kuaidi100's Baidiy
Printags shop is installed from its publisher's own source and answers where it runs, so this marketplace is not in the path of a single call. There is no address here to send one to, and a panel that pretended otherwise would be showing you an answer we made up. Install it and call it from your own client — the Installation tab has the entry for each one.
What it does
Prepare a cart of printed PVC, NFC and wood cards on the Printags shop; no account needed.
Quickstart
# 1 — add it to Claude Code
claude mcp add --scope user --transport http printags-shop-mcp https://studio.printags.com/mcp
# 2 — ask your agent for something these tools do
# list_products, quote_cart, create_upload and 4 more
Printags shop costs nothing on mcprush: there is no plan to choose here, no cap to set and nothing mcprush can bill you for.
Collected from a public index. Nobody has claimed this account, so nothing here was written by its author — claim it if it is yours.
Where are you running it?
Every route below installs the same thing and ends at the same approval screen. Nothing here runs on your machine and nothing runs on ours: this server answers at its publisher’s own address, and what you install is the connection straight to it.
This is a public server: it answers at its publisher’s own address and this marketplace is not in the path. Claude Code registers it in one command; --scope user makes it available in every project. The transport below is http, as the publisher's own manifest declares it.
claude mcp add --scope user --transport http printags-shop-mcp https://studio.printags.com/mcpReconnect, or start a new session, and the tools appear in the model’s tool list.
One config entry pointing straight at the publisher’s own address — this marketplace is not in the path, and nothing from this listing executes on your machine.
7 tools, with what each one reads, writes and reaches shown before you agree — the same list on every route above. Read the tool surface.
Tool surface
What the model actually sees. Descriptions are diffed on every release — see version history.
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| locale | string | no | Langue de la personne : noms des produits, et page du Studio où elle arrivera. Celle de la conversation. |
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| lines | array | yes | — |
| country_code | string | no | Pays de livraison, ISO 3166-1 alpha-2 (défaut FR). Hors de France, des frais d'expédition s'ajoutent. |
| locale | string | no | Langue de la personne : noms des produits, et page du Studio où elle arrivera. Celle de la conversation. |
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 fair
| Parameter | Type | Required | Notes |
|---|---|---|---|
| file_name | string | yes | — |
| content_type | string | yes | — |
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| file_name | string | yes | — |
| content_type | string | yes | — |
| content_base64 | string | yes | — |
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| file | object | yes | Le fichier joint par la personne, rempli par ChatGPT : ne jamais inventer ni modifier ces champs. |
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
| Parameter | Type | Required | Notes |
|---|---|---|---|
| lines | array | yes | — |
| locale | string | no | Langue de la personne : noms des produits, et page du Studio où elle arrivera. Celle de la conversation. |
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| tracking_token | string | yes | Le jeton de suivi de la commande (UUID). |
- Every tool — any call limit is its publisher’s, not ours
- No card, and mcprush charges nothing for it
- Runs at its publisher’s own address — this marketplace is not in the path
- Nothing to cap, because mcprush bills nothing
What counts against your monthly calls
| Tool | Unit | Calls used | Out of the allowance |
|---|
Nothing here is billable: mcprush charges nothing to install Printags shop or to call it, at any volume.
Two independent axes, because powerful and malicious are different questions. The grade is threat only. The capability level is blast radius, and it is never a penalty on the grade — it is priced as one subtract-only term in the score, where you can see it.
| Term | Level | What it prices | Points |
|---|---|---|---|
| capability-exposure | moderate | capability blast radius (moderate) — client exposure if the model is manipulated | −3 |
| coverage-honesty | manifest | inspection depth (manifest) — how much of the target the scan could see | −4 |
What the scan could actually read
A grade is only as meaningful as its coverage, so the scanner publishes its own depth before it publishes its result.
The scan read each tool’s name, description, input schema and annotations exactly as the server listed them the last time it answered us; no code was reviewed. We ask the server again about once a month, and a list that changed is graded again.
The implementation source was not read — this reflects the declared tool metadata only.
Capability — what it could do if the model were manipulated
Tags derived from each tool’s schema and the implementation, not from what the tool calls itself. moderate is the level these add up to.
| Tool | Capability tags | Why the tag was assigned |
|---|---|---|
| list_products | no tags | |
| quote_cart | no tags | |
| create_upload | external-sinkstate-write | external-sink: keyword "curl"; state-write: declares readOnlyHint: false |
| upload_file | external-sinkstate-write | external-sink: keyword "upload_file"; state-write: declares readOnlyHint: false |
| upload_visual | state-write | state-write: declares readOnlyHint: false |
| prepare_cart | state-write | state-write: declares readOnlyHint: false |
| get_order_status | no tags |
Toxic-flow graph
The lethal trifecta, checked as a graph rather than as a checklist: untrusted input, a sensitive source and an external sink have to meet before there is a path worth worrying about.
The public result for this release does not print the flow graph, so there is nothing to show here. That is not the same as "no paths were found": what the scan did read is above, under coverage.
Supply chain and provenance
This is the first scan of this surface here, so there is nothing yet to compare it against.
Every result on this tab comes from one deterministic pass over the published package — offline, rule by rule, and auditable line by line above. Same methodology version, same bytes, same score.
Release history
This is an address its publisher runs: which release it serves is theirs to choose, so there is nothing here to pin. The history below is for reading; the current release on file is 1.0.0.
No release note was published with this version.
One review per account, from a signed-in account that does not publish this listing. Nothing else is asked — you can say what you think before you install it. Publishers can reply once per review, and a review can be edited or deleted by whoever wrote it.
Any signed-in account that does not publish Printags shop can review it, once — before installing it or after. A review from an account that has installed it is marked as one.
Nobody has reviewed this listing. The rating on the card is the mean of the reviews written here and nothing else, so there is no rating until somebody writes the first — which takes a signed-in account that does not publish it, and nothing else.