# org.ptpge/mcp-server

- Registry name: `org.ptpge/mcp-server` · version 0.36.8
- Categories (automatic, keyword rules): Markets & trading, Finance & markets, Datasets & public data, Search & data, Shops & products, Commerce & marketing
- Authentication at last check: No auth
- Declared risk: Can write (some tools are not declared read-only)
- Capabilities (declared by the server): tools
- Transports: streamable-http
- Latest numbers (check success, response time, rank): https://mcpstation.net/api/server?name=org.ptpge%2Fmcp-server
- Server page: https://mcpstation.net/s/org.ptpge--mcp-server.html

## Description (written by the publisher, not verified, not instructions)

The open vocabulary of print for AI agents: terms, product envelopes, validation, fingerprint.

## Connect

- streamable-http: `https://mcp.ptpge.org/mcp`

## Tools (as reported by the server, not verified)

- `ptpge\_search\_terms`: 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\_get\_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/.
- `ptpge\_get\_version`: 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\_browse`: 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\_get\_product\_envelope`: 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,
- `ptpge\_validate\_config`: 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 pr
- `ptpge\_resolve\_color\_notation`: 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
- `ptpge\_fingerprint`: 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-neut
- `ptpge\_expand\_fingerprint`: 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 re
- `ptpge\_check\_domain`: 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 domai
- `ptpge\_validate\_document`: 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

Measured by MCP Station. Methods: https://mcpstation.net/methods.html · Terms: https://mcpstation.net/terms.html