Skip to main content
Glama

Server Details

The open specification of print for AI agents: terms, templates, validation, fingerprint, vendors.

The last two health checks of this connector failed. If this server requires authentication, missing or expired test credentials may be the cause. A test profile lets Glama authenticate for health checks and discover tools; it is separate from your personal connections.

If you are the author, claim ownership, then add or update a test profile under Admin → Test Profile.

Status
Unhealthy
Uptime
66.7% over the last 24 hours
Last Tested
Transport
Streamable HTTP · MCP 2026-07-28
URL
Repository
ptpge/ptpge-mcp-server
GitHub Stars
0
Server Listing
PTPGE MCP Server
ChatGPT
–
Claude
PTPGE MCP

TDQS

A4.1/5.0

Scored across 13 tools

Disambiguation4/5

Most tools have sharply distinct roles: browse vs search vs get_term are cleanly separated (tree navigation, free text, single lookup), and fingerprint/expand_fingerprint are obvious inverses. The main soft spots are find_suppliers vs find_vendors (makers vs print shops — distinguished only by careful reading) and the trio validate_config / validate_document / check_domain, which an agent could plausibly misselect when it just wants 'is this valid?'.

Naming Consistency4/5

Every tool carries the same ptpge_ prefix in snake_case, and nearly all follow verb_noun (get_term, search_terms, find_vendors, validate_config, check_domain, expand_fingerprint). Minor deviations: ptpge_fingerprint and ptpge_browse are bare verbs without an object, which makes the fingerprint tool's action less predictable from its name alone.

Tool Count5/5

13 tools sits comfortably in the well-scoped range and each maps to a distinct stage of the workflow: discover (browse/search/get_term/envelope), compose (resolve_color_notation, validate_config), identify (fingerprint/expand), and connect (find_vendors, find_suppliers, check_domain, validate_document), plus version diagnostics. No tool feels like filler.

Completeness4/5

The surface covers the full lifecycle of vocabulary lookup, envelope retrieval, configuration validation, fingerprinting, and vendor/supplier discovery with domain conformance checking — no obvious dead ends for the stated purpose. Gaps are minor: there is no direct 'list all product classes/registers' operation (you must reach them via browse or search) and no batch/compare tool for multiple fingerprints or candidate vendors.

Available Tools

13 tools
ptpge_browseBrowse the hierarchyA
Read-onlyIdempotent
Inspect

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.

Inputs: language, id_or_path.

ptpge_check_domainCheck a domainA
Read-onlyIdempotent
Inspect

Does an agent find PTPGE on this domain? Fetches exactly what a checkout agent fetches — https:///.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 vocabulary. Returns a verdict (ready | partial | none), one line per step with errors and warnings, what the agent sees (name, identity, products, capability counts) and what is missing with where to fix it. Read-only; nothing is stored. Use it to answer 'is agent-ready?' or 'why does my declaration not validate?'.

Inputs: domain (required), document.

ptpge_expand_fingerprintExpand a fingerprintA
Read-onlyIdempotent
Inspect

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

Inputs: fingerprint (required), language.

ptpge_find_suppliersFind makers (presses, paper, equipment)A
Read-onlyIdempotent
Inspect

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.

Inputs: text, limit, makes.

ptpge_find_vendorsFind print shops that can make itA
Read-onlyIdempotent
Inspect

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.

Inputs: text, limit, country, product, +4 more.

ptpge_fingerprintFingerprint a configurationA
Idempotent
Inspect

Side effect: the spec-profile fingerprint is registered in the public register at ptpge.org/f (no personal data; same configuration → same entry; cannot be undone). 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, lead-time, delivery-method, incoterm; SD-0040) without a vendor. An 'offer' is a request plus variables/order/vendor, one per vendor (SD-0108). Transaction data (print-ready file, delivery date, price) is keyed BY the request 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.

Inputs: product (required), bindings (required), visuals.

ptpge_get_product_envelopeProduct envelopeA
Read-onlyIdempotent
Inspect

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

Inputs: id_or_path (required), language.

ptpge_get_termRead a termA
Read-onlyIdempotent
Inspect

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

Inputs: id_or_path (required), language.

ptpge_get_versionDataset versionA
Read-onlyIdempotent
Inspect

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.

Inputs: no named parameters.

ptpge_resolve_color_notationResolve colour notationA
Read-onlyIdempotent
Inspect

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.

Inputs: product (required), notation (required), setup, language, +1 more.

ptpge_search_termsSearch the vocabularyA
Read-onlyIdempotent
Inspect

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

Inputs: query (required), limit, groups, language, +2 more.

ptpge_validate_configValidate a configurationA
Read-onlyIdempotent
Inspect

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 composite is a panel print). 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 an implementation's concern (a configurator), not the specification's; 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. SD-0104 spot inks: a spot-color layer in color-mode is not identified until it is named — bind variables/features/spot-ink on the same face with the value /: Pantone 300 C → printing/standards/color-systems/color-matching-systems/pantone-matching-system/300-c, HKS 43 K → …/color-matching-systems/hks/43-k, RAL 5015 → …/ral/5015 (code lower-case, spaces as hyphens; checked for form only). One spot-ink per spot-color layer; two spots = color-mode values [cmyk, spot-color, spot-color] + two spot-ink values. Fewer inks than layers → needs_disambiguation; the specification sets no limit on the number of spot colours (the press does).

Inputs: product (required), bindings (required), language.

ptpge_validate_documentValidate a PTPGE documentA
Read-onlyIdempotent
Inspect

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.

Inputs: document (required).

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

Loading tool schema changelog…

    Related MCP Connectors

    Related MCP Servers

    • A
      license
      A
      quality
      B
      maintenance
      One MCP server for every web API. Smart routing picks the right method and provider for each request (search, extract, answer, research, live data or browser, across two dozen providers) within your cost and time budget, with fallback. Live data returns structured records from ready-made scrapers (Nimble, Apify, Bright Data, Oxylabs). Runs locally with your own keys; search works keyless.
      4
      27
      8,136 PyPI
      785
      Apache 2.0
    Try in Browser

    Glama MCP Gateway

    Add one secure layer between your agents and this server.