io.github.jmshinhwa/latex-submission-lint MCP Server
io.github.jmshinhwa/latex-submission-lint
What this kind of tool is for
- Draft or rewrite copy in a format your agent can iterate on with you.
- Convert research notes or transcripts into publishable drafts.
- Keep terminology and tone consistent across a set of documents.
How to compare servers like this
- Output format:
- Prefer tools that emit clean markdown or structured text over unverifiable blobs.
- Source handling:
- Check how the tool treats citations and quotes; sourced claims beat paraphrase.
- Maintenance signal:
- Prompt-driven tools improve with updates; check the last-commit date.
- License clarity:
- Know what license governs the tool and any shipped prompt or template content.
This page carries your copy-paste config: pick your MCP client in the install section on this page and use the copy button.
What is the io.github.jmshinhwa/latex-submission-lint MCP server?
Seventeen rules on your .tex file: the statements the editorial office looks for, and the source tha
How to install io.github.jmshinhwa/latex-submission-lint
Copy-paste configuration for popular MCP clients.
{
"mcpServers": {
"latex-submission-lint": {
"command": "npx",
"args": [
"-y",
"@readystack/latex-submission-lint",
"--mcp"
]
}
}
}Related MCP servers
12 reglas de lectura fácil para guías y formularios de trámite (RD 707/2026, UNE 153101)
View repository →Finds the dependencies whose licence changed under you - Terraform 1.6+ BUSL, Redis 7.4+ SSPL, Bitna
View repository →Finds the lit-html binding positions auto-escaping does not cover, before the component ships
View repository →Marks every line of a Livewire or Blade file that the visitor's browser can call, rewrite or read
View repository →The Livewire 2 lines that die quietly in Livewire 3 — named, with the v3 replacement beside each
View repository →22 rules that name the lines where a Node or TypeScript service writes personal data into logs, cras
View repository →