io.github.MCPServings/paper-mcp

The materials indicate no required keys or environment variables. No API token, account password, or other sensitive credential is requested, so credential leakage and misuse exposure appears limited.

It is known to connect to the remote endpoint latex-tools.online, and the description includes searching arXiv, Semantic Scholar, OpenAlex, PubMed, Europe PMC, plus LaTeX/PDF tooling, implying user queries or document content may be sent to declared external services. No unrelated or covert exfiltration endpoint is shown, but this is still a standard network-egress case.

The system checks show this tool has code-execution capability. Given its LaTeX/PDF tooling purpose, it may reasonably start local processing subprocesses or run conversion commands. The materials do not show clearly excessive system privileges beyond its stated function, so this fits normal MCP code-execution caution.

Based on its LaTeX/PDF processing function, the tool likely needs to read user-provided paper, LaTeX, or PDF files and may generate output files; this is normal data access for this class of tool. The materials do not state that it broadly reads unrelated directories or requests excessive file permissions, but local document access should still be minimized.

The source is an official registry entry with an open-source repository and updates within the last year, providing auditability and some maintenance activity; these are meaningful risk-reducing signals. While community stars are low and no license is declared, that adds some adoption and compliance uncertainty but does not by itself constitute a high-risk red flag.