MCP server for DeepL translation API
The open vocabulary of print for AI agents 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
The open vocabulary of print for AI agents: terms, product envelopes, validation, fingerprint.
Quickstart
# 1 — add it to Claude Code
claude mcp add --scope user --transport http the-open-vocabulary-of-print-for-ai-agents-mcp https://mcp.ptpge.org/mcp
# 2 — ask your agent for something these tools do
# ptpge_search_terms, ptpge_get_term, ptpge_get_version and 7 more
The open vocabulary of print for AI agents 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 the-open-vocabulary-of-print-for-ai-agents-mcp https://mcp.ptpge.org/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.
10 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.
Free-text search over the PTPGE vocabulary and registers — the open specification of print. Returns a ranked list of matching terms with their URI, notation, preferred label, level (top-concept / group / category / sub-category / element), group, and a relevance score (0.0–1.0).
| Parameter | Type | Required | Notes |
|---|---|---|---|
| query | string | yes | Free-text query. Matched against notation, label, altLabels, and definition. |
| limit | integer | no | Maximum number of results to return. |
| groups | array | no | Optional filter by group code(s), e.g. ["substrates", "configurations"]. Omit for all groups. |
| language | string | no | ISO 639-1 language code for label and definition matching. |
| query_language | string | no | ISO 639-1 code for the language the QUERY is written in — not the language of the labels you want back (that is language). Optional, and it never changes the results: search always looks across ever |
| include_deprecated | boolean | no | Also return deprecated terms (they still resolve by URI but are no longer vocabulary). Default false: a brand name resolves to its register entry (kind=supplier) instead of the retired term. |
Fetch full context for a single PTPGE term: definition, broader/narrower relations, exactMatch / closeMatch mappings, properties, notation, level, and metadata. Accepts either a full URI (https://ptpge.org/v1/...) or a relative path under /v1/.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| id_or_path | string | yes | Full URI or relative path under /v1/. E.g. 'printing/configurations/formats/a-series/a4'. |
| language | string | no | ISO 639-1 language code for which label and definition variants to return flat. |
Return the current PTPGE dataset version, total term count, counts per level and per group, license, scheme URL, and server version. Useful for version-pinning, health checks, and diagnostics.
No parameter schema on file.
Navigate the PTPGE hierarchy. Returns a node and its children (id, notation, label, level, elementType, hasChildren). Omit id_or_path to get the three top concepts (printing, ordering, variables). Use this for systematic exploration instead of guessing search keywords.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| id_or_path | string | no | Full URI or path under /v1/. Omit for the top concepts. |
| language | string | no | — |
Return the complete Configuration Envelope of a product class in one call: supportsSetupModel, every supports* and perSurfaceSupports* predicate with resolved labels, plus typical* descriptors. This is the full menu of what can be configured for the product — use it before composing a configuration, instead of many individual ptpge_get_term calls. Absent predicates mean NOT supported (closed seman
| Parameter | Type | Required | Notes |
|---|---|---|---|
| id_or_path | string | yes | Product URI or path, e.g. 'ordering/products/brochures'. |
| language | string | no | — |
Envelope validation of a product configuration against the specification: checks every binding against the product's supports* envelopes. When a value is not in this template's envelope but another template takes every bound value, the result carries alsoOfferedBy (ranked) and switchHint — switch product and validate again rather than dropping what the buyer asked for (a poster on aluminium compos
| Parameter | Type | Required | Notes |
|---|---|---|---|
| product | string | yes | Product URI or path. |
| bindings | array | yes | Variable bindings to validate. |
| language | string | no | — |
Resolve print colour pair notation (4/4, 4/1, 4+4) into per-surface colour bindings for a given product. The number is a COUNT OF SEPARATIONS, not a colour: it is resolved by searching the combinations this product's envelope actually supports whose colorChannelCount sums to that number. Returns one of three outcomes per surface — a deterministic binding, needs_disambiguation with the candidate
| Parameter | Type | Required | Notes |
|---|---|---|---|
| product | string | yes | Product URI or path. |
| notation | string | yes | Pair notation, e.g. '4/4', '4 / 1', '4+4'. |
| surfaces | array | no | Optional surface slugs in notation order. Without them the faces come from 'setup' (or the product's only setup): flat-sheet front/back, folded-sheet outside/inside, roll face/back (SD-0083). |
| setup | string | no | Optional setup-model URI/path (e.g. 'printing/configurations/setup-models/folded-sheet/tri-fold') so the surfaces match the fold. Required for products with several setups. |
| language | string | no | — |
Compute the canonical ptpge-cfs/1 serialization and SHA-256 fingerprint of a resolved product configuration (SD-0040) — the vendor-neutral identity used as quote/order/cache key. Returns both profiles in strict containment spec ⊂ request: 'spec' = the manufacturable artifact, commercial cluster excluded; 'request' = spec plus the commercial cluster — the variables under variables/order/ (quantity,
| Parameter | Type | Required | Notes |
|---|---|---|---|
| product | string | yes | Product URI or path. |
| bindings | array | yes | — |
| visuals | boolean | no | Also return markSvg (the ptpge-mark/1 recognition mark) and qrSvg (QR encoding the resolver permalink) per profile. Off by default to keep payloads small. |
Expand a spec or request fingerprint (ptpge-cfs/1, full 64-hex or 16-hex short form) back into its structured configuration — the read-back path for MIS/ERP: matched profile, product, every binding with resolved labels, the canonical string, and the dataset version. This is a LOOKUP in the public resolver (ptpge.org/f/), not an inversion of the hash: it resolves when the fingerprint has been regis
| Parameter | Type | Required | Notes |
|---|---|---|---|
| fingerprint | string | yes | SHA-256 hex (64) or the 16-hex short form, with or without the resolver URL prefix. |
| language | string | no | — |
Does an agent find PTPGE on this domain? Fetches exactly what a checkout agent fetches — https://<domain>/.well-known/ucp (the UCP manifest and its ptpge block), the vendor declaration at /.well-known/ptpge/declaration.json, the identity in the vendors register, and a supplier catalogue if the domain is a maker — and validates each against its published JSON Schema (ptpge.org/v1/schemas/) and the
| Parameter | Type | Required | Notes |
|---|---|---|---|
| domain | string | yes | A hostname or URL, e.g. trykkverk.no or https://trykkverk.no/. |
| document | string | no | Optional: https URL of a declaration or catalogue hosted elsewhere than the known path (a register entry marked «hosted»). |
- 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 The open vocabulary of print for AI agents 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.
This listing is an address its publisher runs, and you connect to it directly — this marketplace is not in the path. The scanner reads packages and public source, and an address is neither: the repository linked on this page is where this record was collected from, not a copy of what the address serves, so it is not graded in its place. So there is no grade — not a withheld one, an unmeasured one.
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 0.36.8.
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 The open vocabulary of print for AI agents 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.