Pressa - LaTeX to PDF
REMOTE · API.PRESSA.DEV · 2 COMPONENTS · SCANNED SEP 25
Compile LaTeX to PDF without installing TeX Live. No API key needed to start.
Available components
How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →
Endpoint Security80
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- No authorisation is required to call this server. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one. See how to fix → View diagnostics → Partial
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability60
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 489 tokens (~489/item across 1 items; 1 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management10
- Stability observed for 3 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 1 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 2 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
How do I install the Pressa - LaTeX to PDF MCP server?
Pressa - LaTeX to PDF is a hosted endpoint at https://api.pressa.dev/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
remote · api.pressa.dev
claude mcp add --transport http pressa-dev-pressa 'https://api.pressa.dev/mcp'
{
"mcpServers": {
"pressa-dev-pressa": {
"url": "https://api.pressa.dev/mcp"
}
}
} {
"servers": {
"pressa-dev-pressa": {
"type": "http",
"url": "https://api.pressa.dev/mcp"
}
}
} [mcp_servers.pressa-dev-pressa] url = "https://api.pressa.dev/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"pressa-dev-pressa": {
"type": "remote",
"url": "https://api.pressa.dev/mcp",
"enabled": true
}
}
} openclaw mcp add pressa-dev-pressa --url 'https://api.pressa.dev/mcp' --transport streamable-http
mcp_servers:
pressa-dev-pressa:
url: "https://api.pressa.dev/mcp" {
"McpServers": {
"pressa-dev-pressa": {
"Transport": "http",
"Url": "https://api.pressa.dev/mcp"
}
}
} assistant mcp add pressa-dev-pressa -t streamable-http -u 'https://api.pressa.dev/mcp'
{
"mcpServers": {
"pressa-dev-pressa": {
"type": "http",
"url": "https://api.pressa.dev/mcp"
}
}
} The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 25 Sept 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 24 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 3 to 7. That category is still filling its 30-day observation window: 1 days of observed history at the previous scan, 2 at this one. The score rises as the window fills, whether or not the server changes.
- 23 Sept 26 0
- Stability: unverified → 0.03 ▲ functional
- 22 Sept 26 71
First indexed and scored.
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 25 Sept 2026 · Probed https://api.pressa.dev/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=pressa.dev | CN=YE1,O=Let's Encrypt,C=US | 31 Jul 2026 | 29 Oct 2026 | ECDSA 256 | ECDSA-SHA384 | 5a6213e2aebeab837a180cc7fac0a18cb99 |
| SANs: *.pressa.dev, pressa.dev | ||||||
| CN=YE1,O=Let's Encrypt,C=US (CA) | CN=Root YE,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | ECDSA 384 | ECDSA-SHA384 | 5ddd70dd31f801c85c186a7a04b80afe |
| CN=Root YE,O=ISRG,C=US (CA) | CN=ISRG Root X2,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | ECDSA-SHA384 | 872165fc34b6e5fba8add5b3705fb53a |
| CN=ISRG Root X2,O=Internet Security Research Group,C=US (CA) | CN=ISRG Root X1,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | SHA256-RSA | 6c8f1dc727c7117f7baf853ac980f9cd |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of api.pressa.dev. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| dev. | present | 60074 | 8 | Verified |
| pressa.dev. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 200 |
| Header | Value |
|---|---|
| strict-transport-security | max-age=63072000; includeSubDomains |
| content-security-policy | default-src 'self' https:; font-src 'self' https: data:; img-src 'self' https: data: blob:; object-src 'none'; worker-src 'self' blob:; style-src 'self' https: 'unsafe-inline'; script-src 'self' 'unsafe-inline' blob: https://challenges.cloudflare.com 'nonce-sMfmsqmE2EF9uedzePLGjg=='; frame-src 'self' https://challenges.cloudflare.com https://polar.sh https://checkout.polar.sh; connect-src 'self' https: https://api.polar.sh https://polar.sh |
| x-content-type-options | nosniff |
| x-frame-options | SAMEORIGIN |
| referrer-policy | strict-origin-when-cross-origin |
| permissions-policy | interest-cohort=() |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://api.pressa.dev/mcp | Verified | 200 | |
| http (plaintext) | http://api.pressa.dev/mcp | HTTPS enforced | 308 | https://api.pressa.dev/mcp |
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
compile Compile LaTeX to PDF ~456
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.
| Name | Type | Req | Description |
|---|---|---|---|
| compiler | string | – | Defaults to pdflatex. Anonymous callers may only use pdflatex. |
| latex | string | yes | Complete LaTeX source, including \documentclass and \begin{document}...\end{document}. |
No output schema declared.
No examples provided.
What is the Pressa - LaTeX to PDF MCP server?
Pressa - LaTeX to PDF is an MCP server listed in the public MCP registry as io.github.pressa-dev/pressa. Compile LaTeX to PDF without installing TeX Live. No API key needed to start. This page covers its hosted endpoint (https://api.pressa.dev/mcp).
Is the Pressa - LaTeX to PDF MCP server safe to use?
Pressa - LaTeX to PDF scores 72 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the Pressa - LaTeX to PDF MCP server expose?
Pressa - LaTeX to PDF exposes 1 tool: compile. Their descriptions and schemas cost roughly 456 tokens of context every time the server is loaded.
Does the Pressa - LaTeX to PDF MCP server require authentication?
No. We connected to Pressa - LaTeX to PDF without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the Pressa - LaTeX to PDF MCP server still maintained?
Pressa - LaTeX to PDF is still listed as active in the MCP registry. We last reached this channel on 25 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.