ShareLatexMCP (vinconig/ShareLatexMCP) is an MCP server listed on the M8ven Trust Index. It scores 74 out of 100, grade C. It declares 19 tools. No publisher has claimed this listing.

C
Caution
74/100

ShareLatexMCP

An MCP server that gives Claude access to ShareLaTeX projects over Git, enabling file management, document structure parsing, content extraction, and writing changes back.

Caution. Specific findings reduced this grade. They are listed on the page. Grades reflect the full trust pyramid: code, verification depth, and reputation. New projects cap at C until adoption is earned.

How we verified

Code Verified⚡ Live Monitored: not connected

Verified is a snapshot. Live keeps it current, and builds your track record.

⚡ Connect GitHub → continuous verification on every pushwhy connect →

Who stands behind it

vinconig

Source: Glama

Is this your MCP?

Claim it to get a verified publisher badge, a free copy of our full audit findings, and direct contact for any high-priority issues we find. Or connect your repo for our deepest verification, Live Monitored: read-only, revoke anytime. What we access →

Install from

The grade above is for the source repository. Registries can serve a different version, so we mark the ones we were not able to read.

// key findings
⚠️
Known vulnerabilities in dependencies: 1 high
Affects packages this MCP installs at runtime. Upgrade or remove the affected dependency.
No credential exfiltration, no sensitive file access, no obfuscation
Static analysis found nothing flowing your secrets to unexpected places.
Open source with a license and README
Anyone can audit the code, the license is declared, and the publisher documents what it does.
🔐
You'll be asked for 1 credential: SHARELATEX_GIT_TOKEN
These are read from process.env at runtime. Make sure you trust where they’ll be sent.
// tools this server exposes19 tools

These names and descriptions are the publisher's own, read from the source code. We print them as written. Our assessment is the findings above, not this list.

list_projects

List all configured ShareLaTeX projects

list_files

List files in a ShareLaTeX project. Defaults to .tex only; pass extension "*" to see everything (bibliography.bib, README.md, figures, ...).

read_file

Read a text file from a ShareLaTeX project. Binary files (PDF, images) are rejected rather than returned as garbage.

get_sections

List the sectioning commands in a single LaTeX file, with line numbers.

get_outline

Document-order outline of the whole thesis, following \input/\include recursively from the root file. Use this rather than get_sections on main.tex, which only contains includes. Returns file, line, level, title and label for every heading.

get_section_content

Get the content of a specific section by title.

search_project

Search across project files and return file/line/text for each hit. Use pattern "\\\\todo\\{|\\\\done\\{|% TODO" to list outstanding work.

status_summary

Overview of the project: file counts by type, outline size, and any validation findings.

validate_project

Check the project for problems without compiling: unbalanced braces, mismatched \begin/\end, citation keys missing from bibliography.bib, references to undefined labels, duplicate labels, missing \input targets, and undefined glossary keys. Run this before asking ShareLaTeX to compile.

write_file

Write a complete file and push it. Creates parent directories as needed. For edits to an existing LaTeX file prefer write_section or insert_section, which leave the rest of the file untouched.

write_section

Replace one existing section in a LaTeX file and push. Only the named section changes. Fails if the title is ambiguous unless occurrence is given.

insert_section

Insert a NEW section into a LaTeX file — write_section can only replace sections that already exist. Place it before or after an existing section, or at the end of the file.

append_to_file

Append content to the end of a file, creating it if absent. Useful for notes, CSV data, and appendices.

delete_file

Delete a file from the project and push the removal.

list_bib_keys

List citation keys already present in the bibliography, with entry type and title. Check this before importing from Zotero to avoid duplicates.

add_bib_entries

Merge BibTeX entries into the bibliography by citation key and push. Existing keys are kept unless overwrite is set, so nothing already cited can be lost. Re-running with the same input is a no-op. Feed it BibTeX from Zotero.

file_history

Recent commits for the project or for one file.

show_diff

Diff the working tree against a commit, to review what an edit actually changed.

revert_file

Restore a file to its content at a given commit and push that restoration.

// known CVEs in dependencies1 high

Disclosed vulnerabilities in this server's declared npm dependencies (via OSV). Whether each is reachable depends on the installed versions.

high@modelcontextprotocol/sdk@1.0.0GHSA-w48q-cv73-mx4w

Model Context Protocol (MCP) TypeScript SDK does not enable DNS rebinding protection by default

Depend on this server? Get alerted when its CVEs change.Watch this server free →
// environment variables
To run this server yourself, you supply these values. They go in your own MCP client configuration and stay on your machine. The secret label means the value is sensitive, not that the server mishandles it.
configSHARELATEX_CONFIRMall (default), destructive, or off — see [Confirmation before writing](#confirmation-before-writing)
🔐 secretSHARELATEX_GIT_TOKEN"": "YOUR_GIT_TOKEN"
configSHARELATEX_GIT_TOKEN_FILEPath to a file containing the token
configSHARELATEX_HOSTSet alongside the other env vars:
configSHARELATEX_PROJECTS_CONFIGIf projectName is omitted, the default entry is used. To put projects.json somewhere other than the standard location, point =/absolute/path/projects.json at it from the env block.
configSHARELATEX_PROJECT_ID"": "YOUR_PROJECT_ID",
configSHARELATEX_PROJECT_NAME1. Env vars (single project) — SHARELATEX_PROJECT_ID + SHARELATEX_GIT_TOKEN. Optional: for the display name.
configXDG_CONFIG_HOMEmacOS / Linux ~/.config/sharelatex-mcp/projects.json (or $/sharelatex-mcp/projects.json if set)
// quality suggestions

Tool annotations

No tools have read-only/destructive annotations

Add readOnlyHint or destructiveHint annotations to every tool so hosts can warn users before invoking.

All four hints declared on every tool

19/19 tools missing one or more hints — list_projects (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint); list_files (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint); read_file (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint), +16 more. OpenAI's directory rejects tools where any of the four hints are missing or non-boolean.

For every tool, set all four hints (readOnlyHint, destructiveHint, idempotentHint, openWorldHint) to explicit true/false values that match the handler’s actual behaviour.

Tests exist

No test files found

Add tests that exercise each declared tool.

Shell command execution

6 child_process calls — runs shell commands

Prefer library functions over shell-outs. If you must shell out, ensure all inputs are properly escaped.

Production dependencies are patched

0 critical, 1 high severity in production deps — @modelcontextprotocol/sdk@1.0.0 (high)

Run npm audit fix, or upgrade the affected packages to a non-vulnerable version.

Claim the listing to review these findings one by one and send us a correction where you disagree, straight to the team. Claiming also means we tell you when the grade moves, and reach you first if we find anything urgent.

// full audit trail
The findings above are the summary. The full trail, every check we ran, each deduction, the network hosts observed and the dependency advisories, goes to verified publishers, along with an alert whenever a new one lands. Verified publishers can also review each finding and dispute it in one click. Publisher corrections have sharpened several of our checks this month, because the maintainer knows the codebase better than any scanner.
// improvement guidance — verified publishers only
We have 5 concrete improvements we can share with the publisher of this MCP. Each comes with specific guidance to raise the trust score.
// embed badge in your README
[![M8ven Verified](https://m8ven.ai/badge/mcp/vinconig/sharelatexmcp?variant=verified)](https://m8ven.ai/mcp/vinconig/sharelatexmcp)
Shows verification status without the grade. Want the grade badge instead? Remove ?variant=verified from the URL.
commit: 59efdb0046378f11e83c35cf757680507b5d5c15
code hash: 730d8d5230751bbb99a833804a46be475655f1b5145960669b498159d82cf8b4
view raw JSON →
Check MCPs from inside your assistant
Tool Check · MCP

Vetting this one by hand? Tool Check is an MCP that scores other MCPs. Add it once and ask Claude, ChatGPT, or any MCP client to grade a server, surface CVEs, check the publisher, and suggest safer alternatives — before you install.

https://m8ven.ai/api/mcp/tool-check
check_toolsearch_toolscompare_toolsrecommend_alternativescheck_publisherreport_concern
How to add it →Free · no account needed · works in any MCP client