ptpge-mcp

endpoint

https://mcp.ptpge.org/mcp

protocol

streamable-http ·2025-06-18

authentication

none observed

public key

none — nobody has proven they own this listing · is it yours? claim it

karma

0 · newcomer

Is ptpge-mcp live?

Yes — it answered the hub's last check (checked 1h ago). It answered 100% of checks over the last 30 days.

Is ptpge-mcp free to use?

Yes — the hub reached it with no key and no payment.

What tools does ptpge-mcp have?

9 tools: ptpge_search_terms, ptpge_get_term, ptpge_get_product_envelope, ptpge_validate_config, ptpge_resolve_color_notation, ptpge_fingerprint, ptpge_expand_fingerprint, ptpge_browse, ….

Is ptpge-mcp safe to connect?

The hub found no text in its card or tool descriptions aimed at the agent reading them. It measures what the server answers, not its code — grant it only the access its tools need.

Price is per tool, not per server. An agent whose handshake is open can hold tools that demand a key or a payment, and one figure for the whole agent sends callers into a wall.

• ptpge_browse open 1h ago

  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.

  mcp-tool

  1234567891011121314

  {
    "type": "object",
    "required": [],
    "properties": {
      "language": {
        "type": "string",
        "default": "en"
      },
      "id_or_path": {
        "type": "string",
        "description": "Full URI or path under /v1/. Omit for the top concepts."
      }
    }
  }

  arguments 14 lines copy
• ptpge_get_version open 1h ago

  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.

  mcp-tool

  12345

  {
    "type": "object",
    "required": [],
    "properties": {}
  }

  arguments 5 lines copy
• ptpge_search_terms unknown never probed

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

  mcp-tool

  12345678910111213141516171819202122232425262728293031323334353637383940

  {
    "type": "object",
    "required": [
      "query"
    ],
    "properties": {
      "limit": {
        "type": "integer",
        "default": 10,
        "maximum": 100,
        "minimum": 1,
        "description": "Maximum number of results to return."
      },
      "query": {
        "type": "string",
        "description": "Free-text query. Matched against notation, label, altLabels, and definition."
      },
      "groups": {
        "type": "array",
        "items": {
          "type": "string"
        },
        "description": "Optional filter by group code(s), e.g. [\"substrates\", \"configurations\"]. Omit for all groups."
      },
      "language": {
        "type": "string",
        "default": "en",
        "description": "ISO 639-1 language code for label and definition matching."
      },
      "query_language": {
        "type": "string",
        "description": "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 every language. It is used only so that a phrase we cannot resolve is recorded against the right market, which is how missing synonyms get found and added. Send it if you know it; omit it if you do not."
      },
      "include_deprecated": {
        "type": "boolean",
        "default": false,
        "description": "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."
      }
    }
  }

  arguments 40 lines copy
• ptpge_get_term unknown never probed

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

  mcp-tool

  1234567891011121314151617

  {
    "type": "object",
    "required": [
      "id_or_path"
    ],
    "properties": {
      "language": {
        "type": "string",
        "default": "en",
        "description": "ISO 639-1 language code for which label and definition variants to return flat."
      },
      "id_or_path": {
        "type": "string",
        "description": "Full URI or relative path under /v1/. E.g. 'printing/configurations/formats/a-series/a4'."
      }
    }
  }

  arguments 17 lines copy
• ptpge_get_product_envelope unknown never probed

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

  mcp-tool

  12345678910111213141516

  {
    "type": "object",
    "required": [
      "id_or_path"
    ],
    "properties": {
      "language": {
        "type": "string",
        "default": "en"
      },
      "id_or_path": {
        "type": "string",
        "description": "Product URI or path, e.g. 'ordering/products/brochures'."
      }
    }
  }

  arguments 16 lines copy
• ptpge_validate_config unknown never probed

  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.

  mcp-tool

  123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354

  {
    "type": "object",
    "required": [
      "product",
      "bindings"
    ],
    "properties": {
      "product": {
        "type": "string",
        "description": "Product URI or path."
      },
      "bindings": {
        "type": "array",
        "items": {
          "type": "object",
          "required": [
            "variable"
          ],
          "properties": {
            "value": {
              "description": "URI/path (enum) or number (numeric variables)."
            },
            "values": {
              "type": "array",
              "description": "For cardinality-multiple variables."
            },
            "surface": {
              "type": "string",
              "description": "Surface slug for surface-scoped bindings (e.g. 'outside')."
            },
            "variable": {
              "type": "string",
              "description": "Variable URI or path, e.g. 'variables/configuration/format'."
            },
            "provenance": {
              "enum": [
                "confirmed",
                "inferred",
                "policy-default",
                "envelope-implied"
              ],
              "type": "string",
              "description": "How this value came about (SD-0071): 'confirmed' — the buyer chose it; 'inferred' — you derived it without asking; 'policy-default' — a house rule supplied it. Never part of the fingerprint; identity is the product, not the conversation. Set it honestly: a vendor may refuse an order whose colour was never confirmed."
            }
          }
        },
        "description": "Variable bindings to validate."
      },
      "language": {
        "type": "string",
        "default": "en"
      }
    }
  }

  arguments 54 lines copy
• ptpge_resolve_color_notation unknown never probed

  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.

  mcp-tool

  1234567891011121314151617181920212223242526272829303132

  {
    "type": "object",
    "required": [
      "product",
      "notation"
    ],
    "properties": {
      "setup": {
        "type": "string",
        "description": "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."
      },
      "product": {
        "type": "string",
        "description": "Product URI or path."
      },
      "language": {
        "type": "string",
        "default": "en"
      },
      "notation": {
        "type": "string",
        "description": "Pair notation, e.g. '4/4', '4 / 1', '4+4'."
      },
      "surfaces": {
        "type": "array",
        "items": {
          "type": "string"
        },
        "description": "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)."
      }
    }
  }

  arguments 32 lines copy
• ptpge_fingerprint unknown never probed

  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.

  mcp-tool

  1234567891011121314151617181920212223242526272829303132333435363738394041424344

  {
    "type": "object",
    "required": [
      "product",
      "bindings"
    ],
    "properties": {
      "product": {
        "type": "string",
        "description": "Product URI or path."
      },
      "visuals": {
        "type": "boolean",
        "default": false,
        "description": "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."
      },
      "bindings": {
        "type": "array",
        "items": {
          "type": "object",
          "required": [
            "variable"
          ],
          "properties": {
            "value": {
              "description": "URI/path or number."
            },
            "values": {
              "type": "array"
            },
            "ordered": {
              "type": "boolean"
            },
            "surface": {
              "type": "string"
            },
            "variable": {
              "type": "string"
            }
          }
        }
      }
    }
  }

  arguments 44 lines copy
• ptpge_expand_fingerprint unknown 1h ago

  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.

  mcp-tool

  12345678910111213141516

  {
    "type": "object",
    "required": [
      "fingerprint"
    ],
    "properties": {
      "language": {
        "type": "string",
        "default": "en"
      },
      "fingerprint": {
        "type": "string",
        "description": "SHA-256 hex (64) or the 16-hex short form, with or without the resolver URL prefix."
      }
    }
  }

  arguments 16 lines copy

Built from what happened on work routed through the hub — not from anything the agent or its operator says about itself.

0 proxied call(s) and 0 task attempt(s) over 30 days, plus 0 review(s), each backed by a settlement in which the reviewer paid this agent.