# org.ptpge/mcp-server (remote · mcp.ptpge.org)

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

- Trust score: 66/100 (medium)
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-10-18

## Components

- remote · `mcp.ptpge.org`: 66/100 (this document), [markdown](https://verifymcp.io/servers/org-ptpge-mcp-server/mcp.md), [page](https://verifymcp.io/servers/org-ptpge-mcp-server/mcp)

## Channel facts

- Endpoint: `https://mcp.ptpge.org/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `0.36.8`

## Trust breakdown

How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-10-18.

- **Endpoint Security**: 63/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - No authorisation is required to call this server. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one.
  - HTTPS enforcement could not be verified: the plaintext port answered with HTTP 405, which proves neither a plaintext path nor enforcement.
  - HSTS check failed: the Strict-Transport-Security header is absent.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 61/100
  - AI-judged instruction clarity (good).
  - Context-footprint check failed: tool/resource definitions use about 2576 tokens (~234/item across 11 items; 11 tools + 0 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 20/100
  - Stability observed for 6 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 93/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 79% of tool parameters carry a description.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 11 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 12 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a current MCP spec version (2026-07-28).

## Install

### How do I install the org.ptpge/mcp-server server?

org.ptpge/mcp-server is a hosted endpoint at https://mcp.ptpge.org/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

### Claude

```bash
claude mcp add --transport http org-ptpge-mcp-server 'https://mcp.ptpge.org/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "org-ptpge-mcp-server": {
      "url": "https://mcp.ptpge.org/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "org-ptpge-mcp-server": {
      "type": "http",
      "url": "https://mcp.ptpge.org/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.org-ptpge-mcp-server]
url = "https://mcp.ptpge.org/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "org-ptpge-mcp-server": {
      "type": "remote",
      "url": "https://mcp.ptpge.org/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add org-ptpge-mcp-server --url 'https://mcp.ptpge.org/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  org-ptpge-mcp-server:
    url: "https://mcp.ptpge.org/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "org-ptpge-mcp-server": {
      "Transport": "http",
      "Url": "https://mcp.ptpge.org/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add org-ptpge-mcp-server -t streamable-http -u 'https://mcp.ptpge.org/mcp'
```

### Other

```json
{
  "mcpServers": {
    "org-ptpge-mcp-server": {
      "type": "http",
      "url": "https://mcp.ptpge.org/mcp"
    }
  }
}
```

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-10-17 (score 66, +1)

- [functional] Server version: 0.39.1 → 0.40.0
- [functional] New tool “ptpge_validate_document”

### 2026-10-15 (score 65, +1)

- [security] Tool “ptpge_expand_fingerprint” rewrote its description, which is the text the model reads
- [security] Tool “ptpge_fingerprint” rewrote its description, which is the text the model reads
- [functional] Server version: 0.38.6 → 0.39.1

### 2026-10-14 (score 64, 0)

- [functional] Server version: 0.37.3 → 0.38.6

### 2026-10-13 (score 64, 0)

- [security] Tool “ptpge_validate_config” rewrote its description, which is the text the model reads
- [functional improvement] Stability: unverified → 0.03
- [functional] Server version: 0.36.8 → 0.37.3

### 2026-10-12 (score 64)

First indexed and scored.

## MCP tools (11)

### `ptpge_search_terms` (~301 tokens)

Search the vocabulary

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

Input parameters:

- `groups` (array): Optional filter by group code(s), e.g. ["substrates", "configurations"]. Omit for all groups.
- `include_deprecated` (boolean): 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.
- `language` (string): ISO 639-1 language code for label and definition matching.
- `limit` (integer): Maximum number of results to return.
- `query` (string, required): Free-text query. Matched against notation, label, altLabels, and definition.
- `query_language` (string): 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 eve…

### `ptpge_get_term` (~127 tokens)

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

Input parameters:

- `id_or_path` (string, required): Full URI or relative path under /v1/. E.g. 'printing/configurations/formats/a-series/a4'.
- `language` (string): ISO 639-1 language code for which label and definition variants to return flat.

### `ptpge_get_version` (~52 tokens)

Dataset 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` (~99 tokens)

Browse the hierarchy

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.

Input parameters:

- `id_or_path` (string): Full URI or path under /v1/. Omit for the top concepts.
- `language` (string)

### `ptpge_get_product_envelope` (~120 tokens)

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, instead of many individual ptpge_get_term calls. Absent predicates mean NOT supported (closed semantics).

Input parameters:

- `id_or_path` (string, required): Product URI or path, e.g. 'ordering/products/brochures'.
- `language` (string)

### `ptpge_validate_config` (~582 tokens)

Validate a configuration

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 <matching-system term>/<code>: Pantone 300 C → printing/standards/color-systems/color…

Input parameters:

- `bindings` (array, required): Variable bindings to validate.
- `language` (string)
- `product` (string, required): Product URI or path.

### `ptpge_resolve_color_notation` (~317 tokens)

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

Input parameters:

- `language` (string)
- `notation` (string, required): Pair notation, e.g. '4/4', '4 / 1', '4+4'.
- `product` (string, required): Product URI or path.
- `setup` (string): 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.
- `surfaces` (array): 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).

### `ptpge_fingerprint` (~320 tokens)

Fingerprint a configuration

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.

Input parameters:

- `bindings` (array, required)
- `product` (string, required): Product URI or path.
- `visuals` (boolean): 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.

### `ptpge_expand_fingerprint` (~186 tokens)

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

Input parameters:

- `fingerprint` (string, required): SHA-256 hex (64) or the 16-hex short form, with or without the resolver URL prefix.
- `language` (string)

### `ptpge_check_domain` (~239 tokens)

Check a 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 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 <printer> agent-ready?' or 'why does my declaration not validate?'.

Input parameters:

- `document` (string): Optional: https URL of a declaration or catalogue hosted elsewhere than the known path (a register entry marked «hosted»).
- `domain` (string, required): A hostname or URL, e.g. trykkverk.no or https://trykkverk.no/.

### `ptpge_validate_document` (~180 tokens)

Validate a PTPGE 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 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.

Input parameters:

- `document` (object, required): The document itself (JSON object with a `schema` field).

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/org-ptpge-mcp-server/mcp#diagnostics

## Score history

- 2026-10-18: 66
- 2026-10-17: 66
- 2026-10-16: 65
- 2026-10-15: 65
- 2026-10-14: 64
- 2026-10-13: 64
- 2026-10-12: 64

## Common questions

### What is the org.ptpge/mcp-server server?

org.ptpge/mcp-server is listed in the public MCP registry as org.ptpge/mcp-server. The open vocabulary of print for AI agents: terms, product envelopes, validation, fingerprint. This page covers its hosted endpoint (https://mcp.ptpge.org/mcp).

### Is the org.ptpge/mcp-server server safe to use?

org.ptpge/mcp-server scores 66 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

### What tools does the org.ptpge/mcp-server server expose?

org.ptpge/mcp-server exposes 11 tools: ptpge_search_terms, ptpge_get_term, ptpge_get_version, ptpge_browse, ptpge_get_product_envelope, and 6 more. Their descriptions and schemas cost roughly 2,523 tokens of context every time the server is loaded.

### Does the org.ptpge/mcp-server server require authentication?

No. We connected to org.ptpge/mcp-server without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

### Is the org.ptpge/mcp-server server still maintained?

org.ptpge/mcp-server is still listed as active in the MCP registry. We last reached this channel on 18 October 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

## Links

- Remote endpoint: https://mcp.ptpge.org/mcp
- Repository: https://github.com/ptpge/ptpge-mcp-server
- Changelog RSS feed: https://verifymcp.io/servers/org-ptpge-mcp-server/mcp.xml
- Changelog JSON feed: https://verifymcp.io/servers/org-ptpge-mcp-server/mcp.json
- HTML version of this page: https://verifymcp.io/servers/org-ptpge-mcp-server/mcp