MagicTeX
NPM · MAGICTEX-MCP · SCANNED SEP 20
LaTeX editor for AI agents: live PDF preview, PDF comments that drive edits, git history
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 Security99
- 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
- 35 of 165 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency48
- 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 (AGPL-3.0-or-later).Pass
- Actively maintained (last published 54 days ago).Pass
- Publishes a security disclosure policy (SECURITY.md).Pass
Schema Quality & AI Usability78
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 1080 tokens (~154/item across 7 items; 7 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 Management80
- Stability observed for 24 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 7 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 7 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 MagicTeX MCP server?
MagicTeX runs locally as an npm package, launched with npx -y magictex-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 · magictex-mcp
claude mcp add zoelinuts-magictex -- npx -y magictex-mcp
{
"mcpServers": {
"zoelinuts-magictex": {
"command": "npx",
"args": [
"-y",
"magictex-mcp"
]
}
}
} {
"servers": {
"zoelinuts-magictex": {
"command": "npx",
"args": [
"-y",
"magictex-mcp"
]
}
}
} codex mcp add zoelinuts-magictex -- npx -y magictex-mcp
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"zoelinuts-magictex": {
"type": "local",
"command": [
"npx",
"-y",
"magictex-mcp"
],
"enabled": true
}
}
} openclaw mcp add zoelinuts-magictex --command npx --arg -y --arg magictex-mcp
mcp_servers:
zoelinuts-magictex:
command: "npx"
args: ["-y", "magictex-mcp"] {
"McpServers": {
"zoelinuts-magictex": {
"Transport": "stdio",
"Command": "npx",
"Arguments": [
"-y",
"magictex-mcp"
]
}
}
} assistant mcp add zoelinuts-magictex -t stdio -c npx -a -y magictex-mcp
{
"mcpServers": {
"zoelinuts-magictex": {
"command": "npx",
"args": [
"-y",
"magictex-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.
- 20 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 77 to 80. That category is still filling its 30-day observation window: 23 days of observed history at the previous scan, 24 at this one. The score rises as the window fills, whether or not the server changes.
- 19 Sept 26 −3
- Stability: pass → 0.77 functional
- 18 Sept 26 0
- Stability: 0.97 → pass security
- 17 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 93 to 97. That category is still filling its 30-day observation window: 28 days of observed history at the previous scan, 29 at this one. The score rises as the window fills, whether or not the server changes.
- 14 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 83 to 87. That category is still filling its 30-day observation window: 25 days of observed history at the previous scan, 26 at this one. The score rises as the window fills, whether or not the server changes.
- 12 Sept 26 −2
- CVE-2026-76845 no longer affects this package ▲ security
- Known CVEs: partial → pass ▲ security
- Stability: pass → 0.80 functional
- 11 Sept 26 0
- Stability: 0.97 → pass security
- 10 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 93 to 97. That category is still filling its 30-day observation window: 28 days of observed history at the previous scan, 29 at this one. The score rises as the window fills, whether or not the server changes.
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 20 Sept 2026 · Analysed npm/magictex-mcp@0.1.10
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 165 packages
| Packages resolved | 165 |
|---|---|
| Stale | 35 |
| 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 →
add_comment Raise a review comment on the paper ~239
Post a review comment anchored to a passage of the paper — for a reviewer agent marking up the document. Give the exact quoted text from the compiled paper (or the source prose) it refers to, and your comment/instruction. By default it is created as a *suggestion* the human accepts in the workspace before the author loop acts on it; pass accepted:true only in fully-autonomous ("copilot") mode to make it immediately actionable. Use this to leave many targeted comments rather than one long critique.
| Name | Type | Req | Description |
|---|---|---|---|
| accepted | boolean | – | Autonomous mode: create it already accepted (actionable) instead of a suggestion awaiting the human. Default false. |
| comment | string | yes | The review comment or revision instruction for this passage. |
| page | integer | – | PDF page the passage is on, if known (default 1; the workspace re-anchors by text anyway). |
| quote | string | yes | The exact passage the comment is about (a sentence or phrase from the paper). |
| role | string | – | Your role: "reviewer" (default) critiques and asks for changes; "defender" stress-tests claims / pushes back. |
No output schema declared.
No examples provided.
check_comments Check accepted PDF comments ~165
List the comments the user has accepted on the rendered PDF, as located work items. Each has an id, page, the quoted passage, the source file:line it anchors to (best-effort), and the user's instruction. Call this when the user asks to "address/check my comments" (or after they mention leaving comments) — or on each pass of an agent loop watching for new comments. For each item: open the source at the given location, make the requested edit (saving triggers a recompile + a checkpoint automatically), then call resolve_comment with its id and a one-line note. If it returns none, there is nothing accepted yet — reviewer suggestions awaiting the human's accept don't count.
| Name | Type | Req | Description |
|---|---|---|---|
| includeResolved | boolean | – | Also list resolved comments (default false). |
No output schema declared.
No examples provided.
list_checkpoints List recent checkpoints ~81
List recent checkpoints (auto-saved on each successful compile) — sha, timestamp, and file/line-change stat, newest first. Use this to find a sha to pass into show_diff, or to cite specific saved versions when summarizing a multi-step editing session.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | Max checkpoints to return, newest first (default 10). |
No output schema declared.
No examples provided.
render_preview Render LaTeX preview ~300
Compile the current project's LaTeX to a PDF locally and update the live preview. Uses the machine's TeX install when it has one, otherwise a bundled WASM TeX Live in a headless browser — so no local TeX is required. Returns compile success/errors, which engine and backend ran, the file count, and the local preview URL — open it to see the rendered pages. Call this after editing .tex files to see and verify the rendered result.
| Name | Type | Req | Description |
|---|---|---|---|
| backend | string | – | Compiler backend. Default "auto": use the local TeX install (latexmk) when there is one — full package fidelity, output matching Overleaf — else the bundled WASM TeX Live. "system" forces the local o… |
| engine | string | – | TeX engine. Defaults to xelatex. |
| mainFile | string | – | Path to the main .tex file, relative to the project root. Auto-detected (by scanning for \documentclass) if omitted. |
| shellEscape | boolean | – | Let the document run external programs (LaTeX shell-escape) — needed by \includesvg (Inkscape), minted (Pygments) and similar. Off by default: it lets a .tex execute shell commands, so enable it only… |
No output schema declared.
No examples provided.
reply_to_comment Reply to a comment thread ~107
Add a reply to a comment's thread — to ask the human a clarifying question, explain your reasoning, or (as a defender) push back on another agent's suggestion before it is resolved. Use the comment id from check_comments. This does not resolve the comment; use resolve_comment for that.
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | The comment id, from check_comments. |
| role | string | – | Who is replying (default "author"). |
| text | string | yes | Your reply. |
No output schema declared.
No examples provided.
resolve_comment Resolve a PDF comment ~88
Mark a workspace comment as resolved after you have made the edit it asked for. Pass the comment id (from check_comments) and a one-line note describing what you changed — the note is shown to the user on the comment card.
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | The comment id, as returned by check_comments. |
| note | string | yes | One line describing the edit you made to address it. |
No output schema declared.
No examples provided.
show_diff Show diff (side-by-side image) ~100
Render a side-by-side git diff as an image, shown inline in the conversation. Use this when the user asks to SEE a diff visually — it returns a picture, not a text summary. Defaults to current uncommitted changes; pass a checkpoint sha for a specific saved version.
| Name | Type | Req | Description |
|---|---|---|---|
| checkpoint | string | – | A checkpoint commit sha (from the preview History panel) to diff. Omit to show the current uncommitted changes vs the last commit. |
No output schema declared.
No examples provided.
What is the MagicTeX MCP server?
MagicTeX is an MCP server listed in the public MCP registry as io.github.ZoeLinUTS/magictex. LaTeX editor for AI agents: live PDF preview, PDF comments that drive edits, git history. This page covers its npm package (magictex-mcp).
Is the MagicTeX MCP server safe to use?
MagicTeX scores 83 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 20 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 MagicTeX MCP server expose?
MagicTeX exposes 7 tools: render_preview, show_diff, list_checkpoints, check_comments, resolve_comment, and 2 more. Their descriptions and schemas cost roughly 1,080 tokens of context every time the server is loaded.
Is the MagicTeX MCP server still maintained?
MagicTeX is still listed as active in the MCP registry. We last reached this channel on 20 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 MagicTeX MCP server under?
MagicTeX declares the AGPL-3.0-or-later licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.