Skip to content

Pressa - LaTeX to PDF MCP server

io.github.pressa-dev/pressapressa-devstreamable-httpv0.11.4Scanned

Compile LaTeX to PDF without installing TeX Live. No API key needed to start.

4 tools: 2 change things and 2 only read.

Tools: 0 delete, 0 irreversible, 2 write, 2 read.
  • Reads private data · 1
  • Reads text others write · 4
  • Can send data out · 0
  • No findings

Tools listed without sign-in. Remote posture

With Anlyon

2 tools here change things. Govern them.

  • Anlyon lists the tools and adopts none.
  • Each tool you adopt gets approvals and receipts.
  • Your agent never holds the key.
Govern this server →

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 Pressa - LaTeX to PDF MCP server can do

The Pressa - LaTeX to PDF MCP server is published by the GitHub account pressa-dev. It has 4 tools. It can create or change data (2 tools: compile and render_public_template), but cannot delete data. 2 tools only read.

1 tool reads private data (list_public_templates); 4 tools bring in text other people can write (compile, list_public_templates, get_public_template and 1 more).

None of the fixed checks matched anything in its tool definitions. That is not a safety guarantee.

Its remote endpoint lists its tools without sign-in, and its tools changed 2 times since Anlyon Radar first saw them.

Last scanned Nov 10, 2026, version 0.11.4.

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.

4 tools

Changes things 2Claude Code: ask
  • compileCompile LaTeX source into a PDF.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.

    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
    Compile LaTeX source into a PDF. Returns a PDF URL, page count and compile time. USE THIS WHEN: you have LaTeX source (or a \documentclass) and no local pdflatex / TeX Live installation to run it with. This is that missing compiler, available over HTTP. Also use it whenever the user asks for a document where typesetting matters - an invoice, contract, report, letter, CV, certificate, or academic paper - since you can write the LaTeX yourself and compile it here. DO NOT USE THIS TO: convert HTML to PDF, merge, split or compress existing PDF files, or extract text from a PDF. This compiles LaTeX source and nothing else. No API key is required. Anonymous callers get a small number of compilations per day and failed attempts do not count, so you can iterate on your LaTeX for free. Send an API key in the Authorization header to raise the limits. With a key, a document over the plan's page or size limit still returns a PDF: `preview: true`, the first pages the plan allows, `total_pages`, and `plan_required` naming the plan that covers the whole document. Show the user the preview and relay `warning`; never drop pages silently. IMPORTANT: This tool compiles LaTeX, NOT plain text. You must generate complete, valid LaTeX source yourself before calling it. Do not pass plain text, markdown or JSON directly - convert them to LaTeX first, and never ask the user to write LaTeX. A minimal valid document is: \documentclass{article}\begin{document}<content>\end{document}. Escape these in body text: % & $ # _ { } and backslash. If compilation fails the response includes a `diagnosis` naming the cause and a concrete suggested fix, often a missing \usepackage. Apply it and call again yourself rather than showing the user a TeX log.

    Annotations the server declares

    • title: Compile LaTeX to PDF
    • readOnlyHint: false
    • destructiveHint: false
    • idempotentHint: false
    • openWorldHint: true
  • render_public_templateFill a public template with the user's data and return a PDF link.Reads text others writeNo findings

    Why it is in this group

    • The description's first verb is "fill": a word for a change.

    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
    Fill a public template with the user's data and return a PDF link. Data must match the template's schema (see get_public_template); a missing field comes back as a list of what to ask for, and costs nothing. The designs of one document take the same data (the five resume designs, as do the packing slip and the delivery note), so switching design is the same call with a different slug, and `color` prints a design in another of its colours. Works without an API key within the daily free limit.

    Annotations the server declares

    • title: Fill a public template and get a PDF
    • readOnlyHint: false
    • destructiveHint: false
    • idempotentHint: false
    • openWorldHint: true
Only reads 2Show 2 read-only tools
  • get_public_templateGet a public template's fields (JSON schema), sample data, filling instructions and LaTeX source.Reads text others writeNo findings

    Why it is in this group

    • The name "get_public_template" says "get": 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
    Get a public template's fields (JSON schema), sample data, filling instructions and LaTeX source. Read the instructions before collecting data from the user. To make the PDF, pass the data to `render_public_template`; to change the layout itself, edit the source and use `compile`.

    Annotations the server declares

    • title: Fetch one public template
    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: true
  • list_public_templatesList Pressa's public, professionally designed document templates (invoices, purchase orders, packing slips, delivery notes, receipts, reports, certificates, resumes, CVs, cover let…Reads private dataReads text others writeNo findings

    Why it is in this group

    • The name "list_public_templates" says "list": a word for reading.

    What it can reach

    • private-dataThe description's first sentence says "list" and "document": it reads documents.
    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
    • untrusted-inputThe description's first sentence says "list" and "url": it reads web pages, which anyone can write.
    Description, as the server wrote it
    List Pressa's public, professionally designed document templates (invoices, purchase orders, packing slips, delivery notes, receipts, reports, certificates, resumes, CVs, cover letters), each with a one-line summary, a preview image URL and the colours it comes in. Several designs of one document (`document`, e.g. five resume designs) take the same data. Use this when the user wants one of these documents and has no layout of their own, or asks to see designs to choose from. Works without an API key.

    Annotations the server declares

    • title: Browse Pressa's public document templates
    • 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 outbound.

Reads private data1
Reads files, mail, messages, databases, secrets, calendars or repositories.
Reads text others write4
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.

Tools listed without sign-in

Looked at Nov 20, 2026, 19:09 UTC, unchanged since Oct 29, 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
2
Protocol version
2025-06-18
WWW-Authenticate on 401
not observed
resource_metadata in WWW-Authenticate
not observed
RFC 9728 protected resource metadata
https://api.pressa.dev/.well-known/oauth-protected-resource/mcp
Authorization servers
https://pressa.dev
Legacy HTTP+SSE transport
no
Dynamic client registration
yes
Client ID metadata documents
yes
  • WarnThe whole server

    The endpoint served tools/list without credentials, and the list has 2 tools that change things (2 write). Whether a call also works without credentials was not tested: tools are never called.

    Matched text

    https://api.pressa.dev/mcp: tools/list returned 4 tools to an anonymous client, including compile (write), render_public_template (write)

    What this check looks for

Posture changes

  1. Oct 29, 2026
    • RFC 9728 protected resource metadata: none to https://api.pressa.dev/.well-known/oauth-protected-resource/mcp
    • Authorization servers: none to https://pressa.dev
    • Dynamic client registration: not observed to yes
    • Client ID metadata documents: not observed to yes

Findings

Matches of fixed checks, with the text they matched.

No check matched anything in these tool definitions. That is not a safety guarantee.

History

Changes to its tool definitions and to its remote endpoint, newest first.

  1. Tools4 changed.~4 changedView diff
  2. PostureRemote posture changed. RFC 9728 protected resource metadata: none -> https://api.pressa.dev/.well-known/oauth-protected-resource/mcp; Authorization servers: none -> https://pressa.dev; Dynamic client registration: not observed -> yes (and …View diff
    • RFC 9728 protected resource metadata: none to https://api.pressa.dev/.well-known/oauth-protected-resource/mcp
    • Authorization servers: none to https://pressa.dev
    • Dynamic client registration: not observed to yes
    • Client ID metadata documents: not observed to yes
  3. Tools1 changed.~1 changedView diff
    • Changed:compileChanges thingsinputSchema

Install

Pinned to version 0.11.4. Values in angle brackets are yours to fill in.

claude mcp add --transport http pressa https://api.pressa.dev/mcp
claude mcp add --transport http pressa https://api.pressa.dev/mcp

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

.claude/settings.json
{
  "permissions": {
    "allow": [
      "mcp__pressa__list_public_templates",
      "mcp__pressa__get_public_template"
    ],
    "ask": [
      "mcp__pressa__compile",
      "mcp__pressa__render_public_template"
    ],
    "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 pressa. Review it before you use it.

Capability tags behind 4 rules
  • mcp__pressa__compile untrusted-input
  • mcp__pressa__list_public_templates private-data, untrusted-input
  • mcp__pressa__get_public_template untrusted-input
  • mcp__pressa__render_public_template 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/io.github.pressa-dev/pressa/verify?hash=d9975e339841ff7475ae2eece315c403bec66fba0e082bb034401142bca2b43f" | jq -e '.changed == false'

Pinned hash d9975e339841, from Nov 10, 2026, 00:18 UTC.

Watch

Get told when its tools change: a new tool, a new description, a new class.

https://radar.anlyon.com/servers/io.github.pressa-dev/pressa/changes.xml

An Atom feed. Works in any feed reader or Slack's RSS app.

Badge

Anlyon Radar badge for io.github.pressa-dev/pressa
[![Anlyon Radar](https://radar.anlyon.com/badge/io.github.pressa-dev/pressa.svg)](https://radar.anlyon.com/servers/io.github.pressa-dev/pressa)

Source: MCP Registry · repository. Synced Oct 28, 2026, 18:18 UTC.

Pressa - LaTeX to PDF MCP server: questions and answers

Answered from the scan above, not from the publisher's description.

Is the Pressa - LaTeX to PDF MCP server safe?

No scan can promise that. What its definitions show: 4 tools, 2 of which can change, send or delete something, and 0 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 Pressa - LaTeX to PDF MCP server delete data?

No tool is classed as destructive: going by their definitions, none of them deletes, cancels or revokes anything.

Can the Pressa - LaTeX to PDF MCP server do things that cannot be undone?

No tool is classed as irreversible: none of them sends, pays, publishes or merges, going by their definitions.

What tools does the Pressa - LaTeX to PDF MCP server have?

4 tools: 2 write, 2 read. compile, render_public_template, list_public_templates and get_public_template.

Does the Pressa - LaTeX to PDF MCP server need sign-in or OAuth?

Its remote endpoint listed its tools to an anonymous client, without sign-in.

Does the Pressa - LaTeX to PDF MCP server send data to outside services?

None of its tools sends, posts or publishes, or takes a recipient, channel or URL.

Has the Pressa - LaTeX to PDF MCP server changed its tools?

Yes, 2 times since Anlyon Radar started tracking it, most recently on Nov 10, 2026. Every change is on this page and in its Atom feed.