Skip to content
PTPGE logo

PTPGE MCP server

Which MCP servers are PTPGE's own, from the official registry and from asking its own domain, whether they answer, and what they offer. A program checked each of these, nobody copied them from a product page.

read 2026-10-27

← Back to PTPGE

Whose server it is
  • Registry nameorg.ptpge/mcp-serververified in the MCP registry

The registry name sits under ptpge.org. The registry only lets a publisher use that namespace after proving control of the domain through DNS or HTTP.

When we asked itchecked 2026-10-27
  • Stateanswerschecked 2026-10-27
  • Tools11
  • Server calls itselfptpge-mcp
  • Server version0.40.2
  • Protocol version2025-06-18

On 2026-10-27 the server answered initialize and tools/list without a sign-in. First answer in 2084 ms.

Should an agent connect itNot proven either way yet
  • Whether its tools do the product's job has not been judged yet.

Once connected

  • Parameters are untyped or undescribed in 6 of 11 tools: check arguments before calling.

Said by rules from the measurements above. The likely first call is a model's pick from the tool list; read its description before relying on it.

Measured dailydaily checks: 8, the first on 2026-10-27
  • INITE MCP score75 of 100answers 75 · definitions 91 · context 95 · use 0 · connects 100
  • Answered75% of days6 of 8 daily checks
  • Median first answer464 ms
  • Space in an agent's context≈ 3,563 tokensthe definitions of all its tools (11), which an agent carries on every turn
  • Tool definitionsA · 91 of 100
  • Typed results0 of 11 toolsdeclared outputSchema: results come typed, read once
  • Parameters without a description: in 6 of 11

What an agent can do with it

  • not sure · resolve a plain-language print request to a fingerprint
  • not sure · compare buyer requests, vendor offers and finished jobs
  • not sure · look up a configuration's permanent identity page

Each of the product's use cases, put to Jev against this server's tool list: can an agent do it with these tools?

Worth a look

None of the five warning signs in these definitions.

A program checks the server once a day: initialize and tools/list, no model. Tokens are the definitions' length at about four characters a token. The grade averages six checks of every tool's name, description, schema and annotations; it says how well the tools are described, not whether they work. The score weighs what was measured and nothing else: answering (25%), doing the product's job (25%), definitions (20%), context (10%), use (10%) and how readily a client connects (10%). A part that was not measured is left out, and a hidden instruction caps the score at 40. The state of vendors' MCP servers: method and numbers →

Tools it offers11 tools · read 2026-10-27
  • 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 /…

  • 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…

  • 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…

  • 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…

  • 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…

  • 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…

  • 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…

  • 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…

  • 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…

  • 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…

How to connect

Add the server to your MCP client config. Claude Desktop, Cursor and most other clients read this shape:

{
  "mcpServers": {
    "ptpge": {
      "type": "http",
      "url": "https://mcp.ptpge.org/mcp"
    }
  }
}

Add it

Claude Code, in a terminal

claude mcp add --transport http ptpge https://mcp.ptpge.org/mcp

Add to CursorAdd to VS Code

claude.ai, ChatGPT and other clients: add https://mcp.ptpge.org/mcp as a custom connector in the settings.

Each line is something a program found when it went looking: the registry entry, the server's own answer, a spec that parses. A missing line means we did not find it, not that it does not exist.