ptpge.org MCP server
org.ptpge/mcp-serverptpge.orgstreamable-httpv0.42.3Scanned
The open specification of print for AI agents: terms, templates, validation, fingerprint, vendors.
13 tools: 1 do something that can't be undone, 3 change things and 9 only read.
- Reads private data · 0
- Reads text others write · 7
- Can send data out · 0
- 2 findings
Tools listed without sign-in. Remote posture
With Anlyon
1 tool here does something that can't be undone. Govern it.
- Anlyon lists the tools and adopts none.
- Each tool you adopt gets approvals and receipts.
- Your agent never holds the key.
A tool your agent calls directly is not routed through Anlyon and is not governed by it. Anlyon Radar only lists and labels, and these labels are the same either way.
What the ptpge.org MCP server can do
The ptpge.org MCP server is published by ptpge.org, a domain the MCP Registry verified. It has 13 tools. It can do things that cannot be undone, such as sending, paying or publishing (ptpge_fingerprint) and create or change data (3 tools: ptpge_browse, ptpge_expand_fingerprint and ptpge_check_domain), but cannot delete data. 9 tools only read.
7 tools bring in text other people can write (ptpge_get_version, ptpge_browse, ptpge_fingerprint and 4 more).
The fixed checks matched 2 findings (annotation-conflict and long-description). Each one comes with the text it matched.
Its remote endpoint lists its tools without sign-in, and its tools changed once since Anlyon Radar first saw them.
Last scanned Nov 14, 2026, version 0.42.3.
Tools
Grouped by what each tool does, most consequential first. Open one for its reasons and full description; descriptions are the publisher's own words.
13 tools
Can't be undone 1Claude Code: ask
ptpge_fingerprintSide 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).Reads text others writeNo findings
Why it is in this group
- The description says "cannot be undone".
What it can reach
- untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
Description, as the server wrote it 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.
Annotations the server declares
- title: Fingerprint a configuration
- readOnlyHint: false
- destructiveHint: false
- idempotentHint: true
- openWorldHint: true
Changes things 3Claude Code: ask
ptpge_browseNavigate the PTPGE hierarchy.Reads text others write1 finding
Why it is in this group
- The name "ptpge_browse" says "browse": a word for reading.
- The description's first verb is "navigate": a word for a change.
- The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
What it can reach
- untrusted-inputThe name "ptpge_browse" says "browse": it reads web pages, which anyone can write.
Findings
- Warn
The server marks "ptpge_browse" read-only (readOnlyHint: true), and its own name, description or input give the class "write".
What this check looks forMatched text
annotations: {"readOnlyHint":true,"destructiveHint":false,"idempotentHint":true,"openWorldHint":false}; The name "ptpge_browse" says "browse": a word for reading.
Description, as the server wrote it 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.
Annotations the server declares
- title: Browse the hierarchy
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
ptpge_check_domainDoes an agent find PTPGE on this domain?Reads text others writeNo findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
- The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
What it can reach
- untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
Description, as the server wrote it 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?'.
Annotations the server declares
- title: Check a domain
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: true
ptpge_expand_fingerprintExpand 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, produ…No findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
- The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
Description, as the server wrote it 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.
Annotations the server declares
- title: Expand a fingerprint
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
Only reads 9Show 9 read-only tools
ptpge_find_suppliersMakers 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,…Reads text others writeNo findings
Why it is in this group
- The name "ptpge_find_suppliers" says "find": a word for reading.
What it can reach
- untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
Description, as the server wrote it 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.
Annotations the server declares
- title: Find makers (presses, paper, equipment)
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: true
ptpge_find_vendorsWho can make this?Reads text others writeNo findings
Why it is in this group
- The name "ptpge_find_vendors" says "find": a word for reading.
What it can reach
- untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
Description, as the server wrote it 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.
Annotations the server declares
- title: Find print shops that can make it
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: true
ptpge_get_product_envelopeReturn the complete Configuration Envelope of a product class in one call: supportsSetupModel, every supports* and perSurfaceSupports* predicate with resolved labels, plus typical*…No findings
Why it is in this group
- The name "ptpge_get_product_envelope" says "get": a word for reading.
Description, as the server wrote it 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).
Annotations the server declares
- title: Product envelope
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
ptpge_get_termFetch full context for a single PTPGE term: definition, broader/narrower relations, exactMatch / closeMatch mappings, properties, notation, level, and metadata.No findings
Why it is in this group
- The name "ptpge_get_term" says "get": a word for reading.
Description, as the server wrote it 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/.
Annotations the server declares
- title: Read a term
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
ptpge_get_versionReturn the current PTPGE dataset version, total term count, counts per level and per group, license, scheme URL, and server version.Reads text others writeNo findings
Why it is in this group
- The name "ptpge_get_version" says "get": a word for reading.
What it can reach
- untrusted-inputThe description's first sentence says "return" and "url": it reads web pages, which anyone can write.
Description, as the server wrote it 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.
Annotations the server declares
- title: Dataset version
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
ptpge_resolve_color_notationResolve print colour pair notation (4/4, 4/1, 4+4) into per-surface colour bindings for a given product.No findings
Why it is in this group
- The name "ptpge_resolve_color_notation" says "resolve": a word for reading.
Description, as the server wrote it 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.
Annotations the server declares
- title: Resolve colour notation
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
ptpge_search_termsFree-text search over the PTPGE vocabulary and registers — the open specification of print.No findings
Why it is in this group
- The name "ptpge_search_terms" says "search": a word for reading.
Description, as the server wrote it 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).
Annotations the server declares
- title: Search the vocabulary
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
ptpge_validate_configEnvelope validation of a product configuration against the specification: checks every binding against the product's supports* envelopes.1 finding
Why it is in this group
- The name "ptpge_validate_config" says "validate": a word for reading.
Findings
- Info
The description is 2,422 characters long, over the 2,000 this check looks for.
What this check looks forMatched text
description ends: "...; the specification sets no limit on the number of spot colours (the press does)."
Description, as the server wrote it 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-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).
Annotations the server declares
- title: Validate a configuration
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
ptpge_validate_documentValidate 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, …Reads text others writeNo findings
Why it is in this group
- The name "ptpge_validate_document" says "validate": a word for reading.
What it can reach
- untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
Description, as the server wrote it 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.
Annotations the server declares
- title: Validate a PTPGE document
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: true
This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.
Exfil surface
Which tools read private data, which read text someone else can write, and which can send data out. One of each is a path a prompt injection can use.
No private-data, untrusted-input, outbound path in this server alone: no tool is tagged private-data or outbound.
- Reads private data0
- Reads files, mail, messages, databases, secrets, calendars or repositories.
- Reads text others write7
- Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
- Can send data out0
- Can carry data to people or systems: it sends, posts or publishes, or takes a recipient, channel or URL.
Other servers in the same agent add their own tools to these paths. Audit your whole setup to see them together.
Remote posture
What anyone on the internet sees at the remote endpoint: an anonymous initialize and tools/list, and the public OAuth metadata.
Looked at Nov 20, 2026, 19:17 UTC, unchanged since Oct 22, 2026. No credentials were sent and no tool was called. What is looked at.
- Reachable
- yes
- HTTP status of an anonymous initialize
- 200
- tools/list served without credentials
- yes
- Tools that change things, listed without credentials
- 4
- Protocol version
- 2025-06-18
- WWW-Authenticate on 401
- not observed
- resource_metadata in WWW-Authenticate
- not observed
- RFC 9728 protected resource metadata
- not observed
- Authorization servers
- not observed
- Legacy HTTP+SSE transport
- no
- Dynamic client registration
- not observed
- Client ID metadata documents
- not observed
- HighThe whole server
The endpoint served tools/list without credentials, and the list has 4 tools that change things (1 irreversible, 3 write). Whether a call also works without credentials was not tested: tools are never called.
What this check looks forMatched text
https://mcp.ptpge.org/mcp: tools/list returned 13 tools to an anonymous client, including ptpge_fingerprint (irreversible), ptpge_browse (write), ptpge_expand_fingerprint (write), ptpge_check_domain (write)
Findings
Matches of fixed checks, with the text they matched.
- Warnptpge_browse
The server marks "ptpge_browse" read-only (readOnlyHint: true), and its own name, description or input give the class "write".
What this check looks forMatched text
annotations: {"readOnlyHint":true,"destructiveHint":false,"idempotentHint":true,"openWorldHint":false}; The name "ptpge_browse" says "browse": a word for reading.
The description is 2,422 characters long, over the 2,000 this check looks for.
What this check looks forMatched text
description ends: "...; the specification sets no limit on the number of spot colours (the press does)."
History
Changes to its tool definitions and to its remote endpoint, newest first.
Tools2 added.+2 addedView diff
- Added:ptpge_find_suppliersOnly reads
- Added:ptpge_find_vendorsOnly reads
Install
Pinned to version 0.42.3. Values in angle brackets are yours to fill in.
claude mcp add --transport http ptpge https://mcp.ptpge.org/mcpclaude mcp add --transport http ptpge https://mcp.ptpge.org/mcpRun in a terminal.
Claude Code permissions
Allow the reads, ask before a change or a way out, deny the deletes. Paste into .claude/settings.json.
{
"permissions": {
"allow": [
"mcp__ptpge__ptpge_search_terms",
"mcp__ptpge__ptpge_get_term",
"mcp__ptpge__ptpge_get_version",
"mcp__ptpge__ptpge_get_product_envelope",
"mcp__ptpge__ptpge_validate_config",
"mcp__ptpge__ptpge_resolve_color_notation",
"mcp__ptpge__ptpge_find_vendors",
"mcp__ptpge__ptpge_find_suppliers",
"mcp__ptpge__ptpge_validate_document"
],
"ask": [
"mcp__ptpge__ptpge_browse",
"mcp__ptpge__ptpge_fingerprint",
"mcp__ptpge__ptpge_expand_fingerprint",
"mcp__ptpge__ptpge_check_domain"
],
"deny": []
}
}Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. A read that can send data out (it takes a URL, say) asks first too. It assumes the server is installed as ptpge. Review it before you use it.
Capability tags behind 7 rules
- mcp__ptpge__ptpge_get_version untrusted-input
- mcp__ptpge__ptpge_browse untrusted-input
- mcp__ptpge__ptpge_fingerprint untrusted-input
- mcp__ptpge__ptpge_check_domain untrusted-input
- mcp__ptpge__ptpge_find_vendors untrusted-input
- mcp__ptpge__ptpge_find_suppliers untrusted-input
- mcp__ptpge__ptpge_validate_document untrusted-input
Pin
Keep the decision: fail CI when the tools change, follow every change, or show a badge.
Pin in CI
Fail a build when the tools you reviewed are not the tools the server serves today.
curl -s "https://radar.anlyon.com/api/v1/servers/org.ptpge/mcp-server/verify?hash=6575cfd98c309b0d748c7e203c941118b750d929ec1aa0d475252135517e7c03" | jq -e '.changed == false'Pinned hash 6575cfd98c30, from Nov 14, 2026, 16:18 UTC.
Watch
Get told when its tools change: a new tool, a new description, a new class.
https://radar.anlyon.com/servers/org.ptpge/mcp-server/changes.xmlAn Atom feed. Works in any feed reader or Slack's RSS app.
Badge
[](https://radar.anlyon.com/servers/org.ptpge/mcp-server)Source: MCP Registry · repository. Synced Nov 14, 2026, 16:18 UTC.
ptpge.org MCP server: questions and answers
Answered from the scan above, not from the publisher's description.
Is the ptpge.org MCP server safe?
- No scan can promise that. What its definitions show: 13 tools, 4 of which can change, send or delete something, and 2 findings from fixed checks. Allow the reads, ask before each change, and deny the deletes; the permissions block on this page does that.
Can the ptpge.org MCP server delete data?
- No tool is classed as destructive: going by their definitions, none of them deletes, cancels or revokes anything.
Can the ptpge.org MCP server do things that cannot be undone?
- Yes. 1 tool can send, pay, publish or merge: ptpge_fingerprint.
What tools does the ptpge.org MCP server have?
- 13 tools: 1 irreversible, 3 write, 9 read. ptpge_fingerprint, ptpge_browse, ptpge_expand_fingerprint, ptpge_check_domain, ptpge_search_terms, ptpge_get_term, ptpge_get_version, ptpge_get_product_envelope and 5 more.
Does the ptpge.org MCP server need sign-in or OAuth?
- Its remote endpoint listed its tools to an anonymous client, without sign-in.
Does the ptpge.org MCP server send data to outside services?
- None of its tools sends, posts or publishes, or takes a recipient, channel or URL.
Has the ptpge.org MCP server changed its tools?
- Yes, once since Anlyon Radar started tracking it, most recently on Nov 14, 2026. Every change is on this page and in its Atom feed.