Pressa - LaTeX to PDF
NPM · @PRESSA/MCP · 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 from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score → Why this is hard to score →
Supply Chain Security98
- No malware found by supply-chain analysis.Pass
- No known CVEs affecting this package version or its production dependencies.Pass
- No install/post-install scripts declared.Pass
- 31 of 96 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency45
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Provenance check failed: no build-provenance attestation is published. See how to fix → View diagnostics → Fail
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 2 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability62
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 1124 tokens (~1124/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 Management0
- Stability not yet verified: not enough scan history yet (needs a 30-day window).Unverified
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 1 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
Unverified: 1 category
A category scored 0 because we could not verify it: a data source with nothing on this package, evidence we could not reach, or a check we could not run. We only credit what we can confirm.
How do I install the Pressa - LaTeX to PDF MCP server?
Pressa - LaTeX to PDF runs locally as an npm package, launched with npx -y @pressa/mcp. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
npm · @pressa/mcp
claude mcp add pressa-dev-pressa -- npx -y @pressa/mcp
{
"mcpServers": {
"pressa-dev-pressa": {
"command": "npx",
"args": [
"-y",
"@pressa/mcp"
]
}
}
} {
"servers": {
"pressa-dev-pressa": {
"command": "npx",
"args": [
"-y",
"@pressa/mcp"
]
}
}
} codex mcp add pressa-dev-pressa -- npx -y @pressa/mcp
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"pressa-dev-pressa": {
"type": "local",
"command": [
"npx",
"-y",
"@pressa/mcp"
],
"enabled": true
}
}
} openclaw mcp add pressa-dev-pressa --command npx --arg -y --arg @pressa/mcp
mcp_servers:
pressa-dev-pressa:
command: "npx"
args: ["-y", "@pressa/mcp"] {
"McpServers": {
"pressa-dev-pressa": {
"Transport": "stdio",
"Command": "npx",
"Arguments": [
"-y",
"@pressa/mcp"
]
}
}
} assistant mcp add pressa-dev-pressa -t stdio -c npx -a -y @pressa/mcp
{
"mcpServers": {
"pressa-dev-pressa": {
"command": "npx",
"args": [
"-y",
"@pressa/mcp"
]
}
}
} 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
- 23 Sept 26 +15
- Malware scan: unverified → pass ▲ security
- 22 Sept 26 53
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 · Analysed npm/@pressa/mcp@0.7.2
Provenance No attestation
The registry publishes no build provenance for this version, so there is nothing to verify.
| Result | No attestation |
|---|---|
| Ecosystem | npm |
Background: How many MCP packages publish verified provenance →
Dependencies 96 packages
| Packages resolved | 96 |
|---|---|
| Stale | 31 |
| Tree resolution | Complete |
Background: SBOMs and build attestations, explained →
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 ~1,124
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 CONFIGURED, so this runs on the anonymous tier: pdflatex only, up to 3 pages, no image assets, and a small number of compilations per day. It works right now - use it. If the server reports the daily allowance is used up, tell the user they can get a free key at https://pressa.dev/users/sign_up in about 30 seconds with no credit card, then set PRESSA_API_KEY and restart this server. If a document is over the plan's page or size limit, the response still contains 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 (the AI agent) must generate complete, valid LaTeX source yourself before calling this tool. Do not pass user-provided plain text, markdown, JSON, or raw file contents directly - convert them to LaTeX first. Do not ask the user to write LaTeX; that is your job. A minimal valid document is: \documentclass{article}\begin{document}<content>\end{document}. Always include a documentclass declaration. Always wrap content in \begin{document}...\end{document}. Always escape these characters in body text: % becomes \%, & becomes \&, $ becomes \$, # becomes \#, _ becomes \_, { becomes \{, } becomes \}, backslash becomes \t…
| Name | Type | Req | Description |
|---|---|---|---|
| assets | object | – | Optional map of filename => base64-encoded binary. Supported formats: PNG, JPG, JPEG, PDF, SVG. Filenames must be plain (no paths, no leading dot, alphanumeric + _-). Each asset is written into the c… |
| compiler | string | – | LaTeX compiler to use (default: pdflatex). pdflatex and xelatex are available on every plan. lualatex requires Pro or Business; on Free or Starter it returns compiler_not_available. |
| latex | string | yes | Complete LaTeX source code. Must include \documentclass and a \begin{document}...\end{document} body. Plain text, markdown, raw notes, JSON, or fragments without these markers will be rejected with n… |
| use_stored_assets | array | – | Names of assets in the user's persistent library to inject into this compile. Use this instead of re-sending the same bytes in `assets` every time when a file (logo, signature, letterhead) will be re… |
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 npm package (@pressa/mcp).
Is the Pressa - LaTeX to PDF MCP server safe to use?
Pressa - LaTeX to PDF scores 68 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 25 September 2026. It declares no install or post-install scripts. 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 1,124 tokens of context every time the server is loaded.
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.
What licence is the Pressa - LaTeX to PDF MCP server under?
Pressa - LaTeX to PDF declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.