Overleaf (mjyoo2) MCP Server
@mjyoo2/overleaf-mcp
npm
v1.0.0
Published by @mjyoo2 — no publish provenance, so origin is unverified, but the source is public: the repository link below is self-declared yet readable, so you can inspect the code before adopting it.
MCP server that lets AI assistants read Overleaf projects, parse LaTeX document structure, and push section-level edits back via Git.
The grade answers one question — how safe is this server for you to adopt — so it is computed in two auditable stages. Nothing below is an opinion or an LLM's guess; every line is a real term the deterministic engine applied, and the same input always yields the same number.
1. Threat score — 100 − 6.3 = 94. What the published surface and source actually contain:
| Points | What was found | Category |
|---|---|---|
| −6.3 | Untrusted input concatenated into a command sink MTC-SRC-009 | injection |
2. Client adoption risk — 94 − 7 = 87. Three small, subtract-only factors that reflect your risk in adopting it — a clean scan proves less on a powerful, unverified or barely-inspectable package, so the grade says so plainly:
| Points | Adoption-risk factor |
|---|---|
| −6 | capability blast radius (high) — client exposure if the model is manipulated |
| −1 | publisher verification (public source) — no provenance, but the source is public and inspectable |
Capability observations and info notes are shown under Findings but never scored.
Open any row's finding below for the file, line and evidence behind a deduction.
Findings 6
high Shell/command execution in server code (overleaf-mcp-server.js)MTC-SRC-002
In the server's implementation (`overleaf-mcp-server.js:9`): Spawning a shell/process is command-execution capability; with unsanitized tool input it is command injection / RCE. This is read from the code itself — not from the tool description — so a poisoned server cannot hide it behind honest-looking metadata.
Evidence: import { spawn } from 'child_process'; import { readFile, writeFile, access, readdir } from 'fs/promises'; import { pro
Fix: Review this call path: confirm it never receives unsanitized tool input, constrain it, or remove it. Treat a server whose code reaches these sinks as high-capability regardless of what its tools claim.
Location: server overleaf-mcp-server.js
medium Untrusted input concatenated into a command sink (overleaf-mcp-server.js)MTC-SRC-009
In the server's implementation (`overleaf-mcp-server.js:248`): A shell/process command assembled from concatenated or interpolated values is command injection when any part is attacker-influenced — the OWASP canonical RCE flow. Verify what reaches the interpolated value. This is read from the code itself — not from the tool description — so a poisoned server cannot hide it behind honest-looking metadata.
Evidence: onst { stdout } = await exec( `cd "${this.repoPath}" && git pull`, { env: { ...process.env, GIT_TERMINAL
Fix: Review this call path: confirm it never receives unsanitized tool input, constrain it, or remove it. Treat a server whose code reaches these sinks as high-capability regardless of what its tools claim.
Location: server overleaf-mcp-server.js
medium Tool "write_file" can modify the filesystemMTC-CAP-002
Tool "write_file" can write, overwrite or delete files (keyword "write_file" in tool name). Verify it is scoped to a safe directory.
Fix: Constrain file operations to an explicit, non-sensitive root; reject path traversal.
Location: tool write_file
low Mutating tool "write_file" declares no destructiveHintMTC-CAP-005
Tool "write_file" can mutate/egress but declares no destructiveHint. Clients that don't default to spec-safe behavior may not prompt before running it.
Fix: Declare accurate annotations, and gate destructive tools on user confirmation regardless.
Location: tool write_file
low Unconstrained path parameter "filePath" on "read_file"MTC-CAP-008
Tool "read_file" takes a path parameter "filePath" with no constraint. Without a canonicalize-and-contain check (not visible statically), this permits ../ traversal outside the intended root.
Fix: Resolve and verify the path stays within an allowed root; reject traversal sequences.
Location: tool read_file · inputSchema.properties.filePath
low Unconstrained path parameter "filePath" on "write_file"MTC-CAP-008
Tool "write_file" takes a path parameter "filePath" with no constraint. Without a canonicalize-and-contain check (not visible statically), this permits ../ traversal outside the intended root.
Fix: Resolve and verify the path stays within an allowed root; reject traversal sequences.
Location: tool write_file · inputSchema.properties.filePath
Tools 8
Each tool and what it can reach — statically extracted from the published source.
list_filesreads sensitive dataread_filereads sensitive datawrite_filewrites filesget_section_contentno sensitive capabilityget_sectionsno sensitive capabilitylist_projectsno sensitive capabilitystatus_summaryno sensitive capabilitywrite_sectionno sensitive capability
What this scan could not see
- Tools were statically extracted from the published source (8 recovered), not enumerated from a running server. Tool-poisoning, Unicode-smuggling, capability and toxic-flow analysis ran on this inferred surface, but a mis-parsed registration could be missed or mis-attributed, so tool-derived findings are capped below “confirmed”. To grade the real runtime surface, scan the running server: --command "npx -y <package>".
Versions 1
Scan history per published version. The engine is deterministic — the same version always yields the same score, so a changed score means the package itself changed.
| Version | Score | Findings | Engine | Scanned |
|---|---|---|---|---|
v1.0.0 latest |
B 87/100 | 6 | 1.13.0 | 2026-09-07 |
Embed this score
Show this server's live Trust Score in your README, docs or website. The badge is served straight from the registry and updates automatically after every rescan — no API key needed. It links back to this page, so anyone who sees the grade can also read the findings behind it instead of taking a number on faith.
Verify this score yourself
The score above is reproducible: the same package version always yields the same result. Run it locally or over the free API — no account, no LLM, fully deterministic.
npx mcptrustchecker scan @mjyoo2/overleaf-mcp --onlineOther implementations of Overleaf 5
Independent packages implementing the same tool, scanned with the same engine. Compare all 6 side by side →
MCP server for Overleaf projects
A minimal, auditable MCP server for editing Overleaf projects via Git
MCP server for Overleaf with tracked-changes support, via the Socket.IO web API (not the Git bridge).
MCP server connecting Claude to Overleaf — automated LaTeX resume editing, compilation, and job tailoring without copy-paste
MCP server for Overleaf integration - read LaTeX files, analyze document structure, and manage Overleaf projects via Git
More in Developer Tools
Hotel booking MCP server — 300K+ properties, real confirmation numbers, loyalty programs. Builders monetize every booking via Stripe Connect. The first MCP server that completes real hotel reservations inside AI conversations.
Manage AdGuard Home through AI assistants
Read-only Azure DevOps for MCP clients using only your existing browser session — no PAT, no Azure CLI. Browse work items, pull requests, comments, attachments and Artifacts feeds across every project, repo and feed you can access.
MCP server for Adobe Experience Manager Assets integration development
Servidor MCP para el tiempo oficial de España (API pública OpenData de AEMET). Predicción, observación y avisos como herramientas MCP tipadas.
A standalone MCP stdio bridge for Affinity by Canva's local MCP SSE server.