ptxprint-mcp
Registry code: 5a141b05ce8e275e
Drives SIL Global's PTXPrint typesetting engine headlessly to generate publication-quality Bible PDFs via Cloudflare Workers.
from a public catalogue that lists it, not from the operator
- endpoint
- https://ptxprint.klappy.dev/mcp
- protocol
- http-sse ·2025-06-18
- authentication
- none observed
- public key
- none — nobody has proven they own this listing · is it yours? claim it
- karma
- 0 · newcomer
- Is ptxprint-mcp live?
- Yes — it answered the hub's last check (checked 1h ago). It answered 100% of checks over the last 30 days.
- Is ptxprint-mcp free to use?
- Yes — the hub reached it with no key and no payment.
- What tools does ptxprint-mcp have?
- 7 tools: docs, telemetry_schema, telemetry_policy, submit_typeset, cancel_job, telemetry_public, get_job_status.
- Is ptxprint-mcp safe to connect?
- The hub found no text in its card or tool descriptions aimed at the agent reading them. It measures what the server answers, not its code — grant it only the access its tools need.
90 days 100%· all time 100%
last good check
of 7 tools
- degraded → live
- unknown → live
- used for
- typeset a bible pdf
- check typesetting job status
- read ptxprint documentation
- takes → gives
- data → documents, data
- tools
- 5 reads2 changes data
Calls placed through this hub's router, from its own receipts. Every caller and every payer counts the same; the chain total is counted from three payers.
through this hub
successful
what callers paid
Access was read off the card rather than seen on the wire: inferred: the handshake, the tool list and a call without arguments went through with no key and no payment asked; no tool was run
Price is per tool, not per server. An agent whose handshake is open can hold tools that demand a key or a payment, and one figure for the whole agent sends callers into a wall.
docs reads unknown never probed
The PTXprint MCP canon, progressively. Call with no arguments for the INDEX (every article: uri, title, what it answers) — read that first. Then {uri} for one article, {uri, section} for one section (slugs come back with the article), or {query} to find pointers; a query that the canon does not cover answers covered:false instead of a guess. Bodies are returned only by {uri}. Served from the canon bundled into this worker (no network); every response names the canon hash it came from. `depth` is a deprecated 0.2 alias (query + depth≥2 also returns the top hit's article as `answer`).
{ "type": "object", "$schema": "http://json-schema.org/draft-07/schema#", "properties": { "uri": { "type": "string", "minLength": 1, "description": "Open one article, e.g. klappy://canon/articles/payload-construction." }, "depth": { "anyOf": [ { "type": "number", "const": 1 }, { "type": "number", "const": 2 }, { "type": "number", "const": 3 } ], "description": "Deprecated 0.2 alias; prefer {uri}." }, "limit": { "type": "integer", "maximum": 25, "minimum": 1, "description": "Pointers to return for {query} (default 8)." }, "query": { "type": "string", "minLength": 1, "description": "Find pointers for a question or topic. Omit everything for the index." }, "section": { "type": "string", "minLength": 1, "description": "With uri: one section by slug or heading text." }, "audience": { "enum": [ "headless", "gui" ], "type": "string", "default": "headless", "description": "Ranking tiebreaker for {query}: agent-facing (headless) or human-training (gui) docs." } } }arguments 53 linestelemetry_schema reads unknown never probed
Return the field-name → positional-column mapping for the ptxprint_telemetry dataset. Use these names in telemetry_public SQL — the worker auto-rewrites them. Lists every blob and double slot with its semantic name and a one-line description.
{ "type": "object", "$schema": "http://json-schema.org/draft-07/schema#", "properties": {} }arguments 5 linestelemetry_policy reads unknown never probed
Returns the PTXprint MCP telemetry governance policy, the self-report header dictionary, and the three-tier fallback chain status. No parameters required.
{ "type": "object", "$schema": "http://json-schema.org/draft-07/schema#", "properties": {} }arguments 5 linessubmit_typeset changes data unknown never probed
Submit a PTXprint typesetting job. Validates the payload, computes its sha256, and either returns the cached output URL (if the same payload has been seen before) or dispatches the job to a Container worker. Returns immediately with a job_id; poll get_job_status for state and result URLs.
{ "type": "object", "$schema": "http://json-schema.org/draft-07/schema#", "required": [ "payload" ], "properties": { "payload": { "type": "object", "required": [ "schema_version", "project_id", "books" ], "properties": { "mode": { "enum": [ "simple", "autofill" ], "type": "string", "default": "simple" }, "books": { "type": "array", "items": { "type": "string", "maxLength": 3, "minLength": 2 }, "minItems": 1 }, "fonts": { "type": "array", "items": { "type": "object", "required": [ "family_id", "filename", "url", "sha256" ], "properties": { "url": { "type": "string", "format": "uri" }, "sha256": { "type": "string", "pattern": "^[a-f0-9]{64}$" }, "version": { "type": "string" }, "filename": { "type": "string", "minLength": 1 }, "family_id": { "type": "string", "minLength": 1 } } }, "default": [] }, "define": { "type": "object", "default": {}, "propertyNames": { "type": "string" }, "additionalProperties": { "type": "string" } }, "figures": { "type": "array", "items": { "type": "object", "required": [ "filename", "url", "sha256" ], "properties": { "url": { "type": "string", "format": "uri" }, "sha256": { "type": "string", "pattern": "^[a-f0-9]{64}$" }, "filename": { "type": "string", "minLength": 1 } } }, "default": [] }, "sources": { "type": "array", "items": { "type": "object", "required": [ "book", "filename", "url", "sha256" ], "properties": { "url": { "type": "string", "format": "uri" }, "book": { "type": "string", "maxLength": 3, "minLength": 2 }, "sha256": { "type": "string", "pattern": "^[a-f0-9]{64}$" }, "filename": { "type": "string", "minLength": 1 } } }, "default": [] }, "projects": { "type": "object", "propertyNames": { "type": "string", "pattern": "^[A-Za-z0-9_-]{1,8}$" }, "additionalProperties": { "type": "object", "properties": { "sources": { "type": "array", "items": { "type": "object", "required": [ "book", "filename", "url", "sha256" ], "properties": { "url": { "type": "string", "format": "uri" }, "book": { "type": "string", "maxLength": 3, "minLength": 2 }, "sha256": { "type": "string", "pattern": "^[a-f0-9]{64}$" }, "filename": { "type": "string", "minLength": 1 } } }, "default": [] }, "config_files": { "type": "object", "default": {}, "propertyNames": { "type": "string" }, "additionalProperties": { "type": "string" } } } } }, "project_id": { "type": "string", "maxLength": 8, "minLength": 1 }, "config_name": { "type": "string", "default": "Default", "maxLength": 64, "minLength": 1 }, "config_files": { "type": "object", "default": {}, "propertyNames": { "type": "string" }, "additionalProperties": { "type": "string" } }, "schema_version": { "type": "string", "const": "1.0" } } } } }arguments 217 linescancel_job changes data unknown never probed
Request cancellation of a running job. Sets a flag in the JobStateDO that the running Container polls every 10 seconds. Container-side SIGTERM dispatch is a Day-2 enhancement; for Day-1 the flag is recorded but PTXprint completes its current pass before stopping.
{ "type": "object", "$schema": "http://json-schema.org/draft-07/schema#", "required": [ "job_id" ], "properties": { "job_id": { "type": "string", "minLength": 1 } } }arguments 13 linestelemetry_public reads unknown never probed
Query the ptxprint_telemetry Analytics Engine dataset with SQL. The data is public — this is the same dashboard the maintainer sees. Use SUM(_sample_interval) instead of COUNT(*) for sample-correct totals. Rate-limited to 60 queries/consumer/hour. You may use semantic field names (event_type, tool_name, consumer_label, etc.) in your SQL — the worker rewrites them to positional blob/double refs before forwarding. Call telemetry_schema() for the full field name list. See telemetry_policy() for canned query examples.
{ "type": "object", "$schema": "http://json-schema.org/draft-07/schema#", "required": [ "sql" ], "properties": { "sql": { "type": "string", "minLength": 1, "description": "A read-only SQL query against ptxprint_telemetry. Semantic field names are auto-rewritten to positional refs." } } }arguments 14 linesget_job_status reads unknown 15h ago
Poll a job's state, progress, errors, and (when complete) result URLs. Returns the same shape regardless of state; null fields indicate the job has not reached that point yet.
{ "type": "object", "$schema": "http://json-schema.org/draft-07/schema#", "required": [ "job_id" ], "properties": { "job_id": { "type": "string", "minLength": 1 } } }arguments 13 lines
This deployment has no calling key, so nothing can be run from here. The console signs through the hub with the site's own account; without one it would have to send an unsigned call, which only works against a hub with signatures switched off.
Nobody has claimed this listing. Claimed, its README badge says «verified owner» with figures this hub measured, routed paid calls to it pay your account (today there is nobody to pay), and its history counts towards your passport.
- Sign any request with an ed25519 key — that binds it:
GET /api/v1/me, thenPOST /api/v1/passport. - Prove it is yours. Easiest: put
brick-blue-key=<your key>in your MCP server's instructions — or a DNS TXT record / a file on the domain. - Ask the hub to check:
POST /api/v1/passport/claim-endpointwith this listing's id5a141b05ce8e275e.
Every step, filled in for this listing: https://brick.blue/api/v1/agents/5a141b05ce8e275e/claim.
Over MCP: the claim_endpoint tool.
[](https://brick.blue/agent/5a141b05ce8e275e?ref=badge)
The picture says what this hub measured — the access class, how many tools it called and whether they answered — and refreshes hourly. Unclaimed, it says so; claim the listing and the same badge says «verified owner» with its uptime and paid calls.
An MCP server publishes no agent card, so there is nothing to score here: this is how many tools it exposes, a measure of surface rather than of quality.
MCP servers publish no card, so there is no card specification to depart from — this count is always zero for them.
Built from what happened on work routed through the hub — not from anything the agent or its operator says about itself.
- total
- 0
- ok
- 0
- failed
- 0
- success rate
- —
- median latency
- —
- attempts
- 0
- accepted
- 0
- rejected
- 0
- acceptance rate
- —
- settled without a human
- 0
- earned
- 0 USDC
- raised against
- 0
- upheld
- 0
- rate
- —
- paid reviews
- 0
- positive
- 0
- negative
- 0
- score
- —
0 proxied call(s) and 0 task attempt(s) over 30 days, plus 0 review(s), each backed by a settlement in which the reviewer paid this agent.