MCP App Store
by KeenEthics
PTPGE MCP icon

PTPGE MCP MCP Server for Claude

By PTPGE

Overview

PTPGE is the open specification of print: a vocabulary of terms with permanent URIs (substrates, formats, folds, finishing, colour, binding …), product templates that say which choices apply to a product and which are required, and an identity — a complete configuration resolves to one fingerprint (ptpge-cfs/1) and one mark. Held by PTPGE, a non-profit association (being formed), CC BY 4.0. This connector gives Claude read-only access to that vocabulary. Ask in any language — «What is a roll fold?», «Which paper weights suit a tri-fold brochure?», «Fingerprint an A4 brochure, 170 g silk, 4/4, matte lamination» — and Claude searches the terms, reads the product envelope, validates the configuration against it and returns the fingerprint and a link to its page on ptpge.org. Useful for print buyers, agencies, printers and anyone building on print data. Thirteen tools — twelve read-only, one that registers (fingerprint: the spec hash is written to the public register at ptpge.org/f, no personal data): search terms · get term · dataset version · browse · product envelope · validate configuration · resolve colour notation (4/4, 4/1 …) · fingerprint · expand fingerprint · check domain (does an agent find a printer? — fetches its UCP manifest, declaration and register entry and validates each against the published schemas) · validate a document · find print shops that can make it (country, product, technology, certification — from each shop’s own declaration, never ranked, never priced) · find makers (presses, paper, equipment). PTPGE is in Public Beta: the vocabulary and the API are stable and versioned by date; term URIs never break (deprecated terms stay resolvable with a pointer to their successor).

How to connect

  1. Claude: Open the PTPGE MCP listing in the Claude connectors directory and choose Connect. Claude listing PTPGE MCP exposes 10 tools here.

Tools

ptpge_browse

Claude
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.

ptpge_check_domain

Claude

ptpge_expand_fingerprint

Claude
Expand a spec or offer 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 registered (every fingerprint computed by ptpge_fingerprint is self-registered within seconds). An unregistered fingerprint is still a valid identity — it simply has no stored expansion yet; returns status 'unknown' then.

ptpge_find_suppliers

Claude
Makers in the PTPGE supplier register — press and equipment builders, paper mills — with what each one makes (a term under printing/…) and, when the maker has claimed its identity, its own catalogue (/.well-known/ptpge/catalogue.json: press models, paper series). Filter by makes (a term path or slug: printing-presses, wide-format-printers, paper …) or free text. Read-only; cached ten minutes.

ptpge_find_vendors

Claude
Who can make this? Reads the PTPGE vendor register and every claimed print shop's own declaration (/.well-known/ptpge/declaration.json — the file is the source) and filters on what the documents say: country (ISO 3166-1 alpha-2), product template (e.g. ordering/products/booklets or just «booklets»), printing technology (a term under printing/technologies/printing-technologies — a parent matches its children, so «digital» finds laser and inkjet), certification (e.g. nordic-swan-ecolabel), substrate, or free text on name/city. Returns each matching shop with its identity, countries and cities, products, technologies, certifications, the matching offerings (minimum quantity, lead time) and the doors an agent needs next: the declaration, the UCP manifest, the register entry. Never ranked, never priced — for price and an order use the shop's own MCP endpoint from its manifest; the spec fingerprint is the same key everywhere. Read-only; cached ten minutes; nothing stored.

ptpge_fingerprint

Claude
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 ⊂ offer: 'spec' = the manufacturable artifact, commercial cluster excluded; 'offer' = spec plus the commercial cluster, which is exactly the four variables under variables/order/ — quantity, lead-time, delivery-method, incoterm (closed list, SD-0040). Transaction data (print-ready file, delivery date, price) is keyed BY the offer fingerprint and never hashed into it. SD-0083: the input is validated first and an identity is issued ONLY for a valid, complete configuration — every required axis of the product bound (or envelope-implied where the envelope offers one value; those are written into the identity) and every surface one of the bound setup's faces. Otherwise the result is error=not_fingerprintable with the validator's needs_disambiguation: put each question to the user verbatim, bind the answer, call again. Never guess a missing axis.

ptpge_get_product_envelope

Claude
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 semantics).

ptpge_get_term

Claude
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/.

ptpge_get_version

Claude
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.

ptpge_resolve_color_notation

Claude
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 combinations, or invalid_for_template when no combination is possible. IMPORTANT: when needs_disambiguation is returned you MUST put its question to the user and never infer the answer yourself. '1' is black on some products and a named spot colour on others; guessing gives two different products the same identity. Do not fingerprint an unresolved configuration.

ptpge_search_terms

Claude
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).

ptpge_validate_config

Claude
Layer 1 envelope validation of a product configuration: checks every binding against the product's supports envelopes, maps numeric substrate-weight (gsm) to its weight band via the bands' minWeight/maxWeight properties, and returns data-driven advisories (e.g. creasing recommended above the scoring thresholds). NOTE: this validates the ENVELOPE only — cross-variable legality (e.g. valid panel counts per fold topology) and vendor capability matching are Layer 2 (Configurator) services; commercial values (date, price) are not configuration and belong to the transaction layer. Elicitation contract (shared by every ptpge_ tool): whenever a result carries needs_disambiguation, each entry has a field, a question that MUST be put to the user verbatim, and candidates — never infer the answer, never fingerprint until it is resolved. SD-0083: the validator also checks completeness — a missing REQUIRED axis of the product (setup/fold, format, page count, binding, colour on the first face, shape where shape is the product) returns needs_disambiguation with the envelope's candidates; a required axis with exactly one allowed value is bound for you as envelope-implied; a surface name that is not a face of the bound setup (faces: flat-sheet front/back, folded-sheet outside/inside, multi-page front-cover…back-cover) is rejected with the allowed faces. complete: true means an identity can be issued.

ptpge_validate_document

Claude
Validate ONE document you hand over — a vendor declaration, supplier catalogue, request, quote or UCP manifest (its schema field says which) — against the published JSON Schema, the vocabulary (every term URI must exist; deprecated warns) and, for request/1 and quote/1, the identity: the spec and request fingerprints are recomputed from the configuration and must match what the document states; a quote's offer fingerprint must equal request + the quote's vendor (SD-0108). Nothing is fetched from any domain and nothing is stored. This is the PTPGE Ready conformance check for a module that writes these documents (ptpge.org/ready/). Returns valid, errors[], warnings[] and what was checked.

Similar Apps

Listed on MCP App Store

Listed on MCP App Store

Add this badge to your site or README. It links to this page.

HTML

<a href="https://mcp-app-store.keenethics-labs.com/app/ptpge-mcp"><img src="https://mcp-app-store.keenethics-labs.com/badges/listed-on-mcp-app-store.svg" alt="Listed on MCP App Store" width="220" height="44"></a>

Markdown

[![Listed on MCP App Store](https://mcp-app-store.keenethics-labs.com/badges/listed-on-mcp-app-store.svg)](https://mcp-app-store.keenethics-labs.com/app/ptpge-mcp)