Search arXiv papers, download full text, semantic search, citation graphs, and alerts via MCP.
Tex Web is installed from its publisher's own source and answers where it runs, so this marketplace is not in the path of a single call. There is no address here to send one to, and a panel that pretended otherwise would be showing you an answer we made up. Install it and call it from your own client — the Installation tab has the entry for each one.
What it does
LaTeX paper review: comment on the PDF while an AI agent edits the source, with Overleaf sync.
Quickstart
# 1 — add it to Claude Code
claude mcp add --scope user tex-web-mcp '--' uvx tex-mcp-web mcp
# 2 — ask your agent for something these tools do
# guide, read_comments, overleaf and 5 more
Tex Web costs nothing on mcprush: there is no plan to choose here, no cap to set and nothing mcprush can bill you for.
Collected from a public index. Nobody has claimed this account, so nothing here was written by its author — claim it if it is yours.
Where are you running it?
Every route below installs the same thing and ends at the same approval screen. This one runs on your machine: your client starts Tex Web as a process under your own user, with your files and your network, so the tool surface below is what it can do to your computer rather than to a server somewhere else. Its scan result is on the Security tab — read the surface before you approve it.
This is a public server: you run it yourself and this marketplace is not in the path. You need uv (docs.astral.sh/uv): uvx comes with it. Claude Code registers it in one command; --scope user makes it available in every project. The '--' is in quotes so that PowerShell passes it on.
claude mcp add --scope user tex-web-mcp '--' uvx tex-mcp-web mcpReconnect, or start a new session, and the tools appear in the model’s tool list.
One config entry your client uses to start the process locally. A local server runs with your file system and your network, which is why it is priced without metering.
8 tools, with what each one reads, writes and reaches shown before you agree — the same list on every route above. Read the tool surface.
Tool surface
What the model actually sees. Descriptions are diffed on every release — see version history.
Read from its source code. A server that builds its tool list when it starts can list more tools than this.
Paths to files to read in full before editing the paper: its guideline and the ones that guideline extends, base first, when guideline is set, and the terms its reference papers use, when references is set.
Takes no parameters.
Read review threads: what is new, selected threads in full, or a listing.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| ids | array | no | — |
| new | boolean | no | Only what the reviewer has written since this call last answered; excludes ids. |
| status | string | no | — |
| unanswered | boolean | no | Only threads where the reviewer wrote to you after the thread's last answer: your reply, your Overleaf draft, or a reply sent to Overleaf. |
| since | string | no | A time this server printed, like '09-19 00:52'; only what came after it. |
| until | string | no | A time this server printed; a search looks only at what came up to that minute. |
| find | string | no | Words a search looks for, case ignored, in what was said in a thread and in its draft for Overleaf. |
| limit | integer | no | — |
| save | boolean | no | — |
This folder against its Overleaf project. state reads Overleaf again and names only what differs: get, Overleaf's edits not here, send, edits here not on Overleaf, choose, files waiting for the reviewer, and in a git clone the commits behind and ahead.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| action | string | no | — |
Compile the paper. Returns whether it succeeded, which pages changed, where the log is, and, when it failed, where each error is.
Takes no parameters.
Write to a comment thread.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| action | string | yes | — |
| id | string | no | — |
| text | string | no | — |
| anchor | no | — | |
| edits | array | no | — |
| changes | array | no | — |
| draft | string | no | — |
| entry | string | no | — |
| rev | string | no | — |
Render one PDF target as PNG.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| page | integer | no | — |
| bbox | array | no | — |
| source | string | no | — |
| comment | string | no | — |
| dpi | integer | no | 96 reads text. 150 or more shows fine detail at more tokens. |
| margin | number | no | — |
| grayscale | boolean | no | Set false when colour itself is being checked. |
Return a command and client-specific instructions for listening for Call agent.
Takes no parameters.
Report setup paths, the existing binding and the guidelines to choose from, without connecting or changing files.
Takes no parameters.
- Every tool, no call limit
- No card, and mcprush charges nothing for it
- Source published under MIT
- Runs on your machine — nothing of it reaches our gateway
- Nothing to cap, because mcprush bills nothing
What counts against your monthly calls
| Tool | Unit | Calls used | Out of the allowance |
|---|
Nothing here is billable: mcprush charges nothing to install Tex Web or to call it, at any volume.
Two independent axes, because powerful and malicious are different questions. The grade is threat only. The capability level is blast radius, and it is never a penalty on the grade — it is priced as one subtract-only term in the score, where you can see it.
| Term | Level | What it prices | Points |
|---|---|---|---|
| capability-exposure | high | capability blast radius (high) — client exposure if the model is manipulated | −6 |
| verification-discount | source | publisher verification (provenance) — cryptographic build provenance ties the artifact to its source | −0 |
| coverage-honesty | source | inspection depth (source) — how much of the target the scan could see | −0 |
What the scan could actually read
A grade is only as meaningful as its coverage, so the scanner publishes its own depth before it publishes its result.
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>".
Capability — what it could do if the model were manipulated
Tags derived from each tool’s schema and the implementation, not from what the tool calls itself. high is the level these add up to.
| Tool | Capability tags | Why the tag was assigned |
|---|---|---|
| guide | no tags | |
| read_comments | untrusted-input | untrusted-input: keyword "read_comment" |
| overleaf | no tags | |
| compile | no tags | |
| write_comments | no tags | |
| image | no tags | |
| listen | no tags | |
| setup_info | no tags |
Toxic-flow graph
The lethal trifecta, checked as a graph rather than as a checklist: untrusted input, a sensitive source and an external sink have to meet before there is a path worth worrying about.
The public result for this release does not print the flow graph, so there is nothing to show here. That is not the same as "no paths were found": what the scan did read is above, under coverage.
Supply chain and provenance
This is the first scan of this surface here, so there is nothing yet to compare it against.
Every result on this tab comes from one deterministic pass over the published package — offline, rule by rule, and auditable line by line above. Same methodology version, same bytes, same score.
Release history
Always latest — the install command names no version, so it installs the newest release when it runs; the current release on file is 0.8.5. Pin a release below and the command asks for exactly that one.
No release note was published with this version.
- The version this listing was on when mcprush began following its releases. The registry was not asked when it shipped, so this row carries no date.
One review per account, from a signed-in account that does not publish this listing. Nothing else is asked — you can say what you think before you install it. Publishers can reply once per review, and a review can be edited or deleted by whoever wrote it.
Any signed-in account that does not publish Tex Web can review it, once — before installing it or after. A review from an account that has installed it is marked as one.
Nobody has reviewed this listing. The rating on the card is the mean of the reviews written here and nothing else, so there is no rating until somebody writes the first — which takes a signed-in account that does not publish it, and nothing else.