io.github.cyanheads/biorxiv-mcp-server

The materials list BIORXIV_MAILTO and MCP_LOG_LEVEL. The former appears to be a contact email rather than a highly sensitive API key, but it is still identifiable information that could leak through logs or poor config handling; no high-privilege token is indicated.

The tool is described as searching and retrieving bioRxiv/medRxiv preprints, so it likely sends DOI, date-range, or keyword queries to relevant scholarly services. No explicit remote host is listed in the system facts and no extra third-party endpoint is disclosed, so this is currently a normal, purpose-aligned network egress case.

The system marks it as executes-code, meaning it runs a local service process as an MCP tool. This is normal MCP behavior; the materials do not show shell access, privilege escalation, or unrelated execution capabilities beyond its retrieval purpose.

From the description, it mainly handles user-supplied DOI, keywords, and date ranges, then returns preprint data. There is no stated need for broad local file access, system directory access, or other clearly excessive data permissions, but as a locally run MCP service it should still be deployed with least privilege.

The source is the official registry, with an auditable open-source repository and updates within the last year, all of which materially reduce risk. Although community stars are low and the license is not stated, the available materials show no red flags such as closed-source distribution, abandonment, or suspicious packaging.