Home / MCP registry index / org.ptpge/mcp-server
org.ptpge/mcp-server
org.ptpge/mcp-server in the official MCP registry.
Endpoint https://mcp.ptpge.org/mcp. Source: github.com/ptpge/ptpge-mcp-server.
The registry describes it as: The open vocabulary of print for AI agents: terms, product envelopes, validation, fingerprint.
We read its 11 tools on 2026-10-24. Nothing in them matched our tool-poisoning rules. It also sets server instructions, text a client puts in front of the model on connect; those were read too.
A clean read means these rules found nothing, not that the server is harmless. A server can change its tools at any time, which is why the index reads it again every week.
Tools it advertises
ptpge_search_terms ptpge_get_term ptpge_get_version ptpge_browse ptpge_get_product_envelope ptpge_validate_config ptpge_resolve_color_notation ptpge_fingerprint ptpge_expand_fingerprint ptpge_check_domain ptpge_validate_document
Run this server? Show the check in your README
The badge reflects the latest weekly read: 
[](https://lazaretto.dev/mcp-registry/org-ptpge-mcp-server)How this was checked
Lazaretto connects to the endpoint the way any MCP client does, asks the server to introduce itself and list its tools, and reads every name, description, parameter schema and server instruction for tool poisoning: hidden directive blocks, orders to read local secrets, parameters built to carry secrets or the conversation out, orders that redirect another server's tools, and invisible characters. It never calls a tool. What we found across the registry.
To run the same check every time Claude Code adds a server, install the free lazaretto-guard plugin. Browse every server in the index.