Latex Submission Lint

io.github.jmshinhwaPublished by GitHub account jmshinhwav1.0.5Updated Oct 24, 2026

Seventeen rules on your .tex file: the statements the editorial office looks for, and the source tha

VerifiedSTDIODesktop onlyDeveloper Tools

Overview

AI-generated overview

A local MCP server that lints a LaTeX .tex file against seventeen rules aimed at journal submission checks.

What you can do
  • Checks a .tex file against seventeen rules covering the statements an editorial office looks for and the source material behind them.
  • Reports findings so an assistant can point out what a submission is missing or where the source does not support a claim.
  • Runs as a local process over stdio, so the assistant calls it directly on the user's machine.
When to use it
Useful when preparing or reviewing a LaTeX manuscript before journal submission and you want an assistant to flag missing editorial statements or unsupported claims in the source.
Requirements
Runs locally via npx from the npm package @readystack/latex-submission-lint over stdio. No authentication, environment variables or headers are declared. Desktop-only; not available as a web executable.
Before you install
The supplied README does not describe this tool's usage and instead contains unrelated theme and website content, so the exact rules and behaviour cannot be verified from the listing. Review the package before running it, since it executes locally on your files.

Installation

In SourceWeft

  1. Open Latex Submission Lint in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.

Other MCP clients

Follow the launch instructions in the repository.

README

readystack-themes

Made by ReadyStack · free calculators and templates at getreadystack.com VS Code themes by ReadyStack

Source: README.md at commit ee1c884

Tools

0
SourceWeft has not started this package in its sandbox yet, so its tools are not known.

Version history

2
  1. v1.0.5LatestSep 23, 2026
  2. v1.0.1Sep 16, 2026

Score

40% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 days25 pts

    Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.

  • Auth declared10 pts

    Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.

  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts
  • License10 pts

    Declare a license in the repository or the registry entry.