Use whenever the user wants to obtain, download, or fetch a paper's PDF — given a DOI, an arXiv id, a paper title, a citation, or a list of DOIs. Trigger on phrases like "download this paper", "find the PDF for [DOI]", "grab me the [Nature/bioRxiv/arXiv] paper on X", "get the open-access version", "I need this…
Add academic papers to Zotero via MCP (DOI/PMID/title); fetch full-text PDFs through a publisher-aware route ladder (Unpaywall → Elsevier/Wiley/Springer TDM → institutional proxy → SFX); PDFs land in a linked-files folder (ZotMoov), never uploaded to Zotero cloud. Also verifies that a downloaded PDF really is that…
A reference-list audit for academic papers that checks citations, formatting, identifiers such as DOIs and URLs, journal names, metadata, completeness, duplicates, self-citations, and ordering. DOI means a persistent identifier for a research publication.
Cut a libgen-mcp release — bump VERSION, mirror it into the version-bearing manifests, regenerate llms.txt, tag, and publish to npm and LobeHub. Use when cutting or preparing a release, bumping the version, or publishing to the MCP registry, npm or LobeHub Marketplace.
Add a new MCP tool to libgen-mcp end-to-end: input/output structs with jsonschema descriptions, a recovery-wrapped handler, Markdown rendering, tests, and docs. Use when extending the tool surface. Prefer deepening an existing tool first.
Go testing patterns including table-driven tests, subtests, benchmarks, fuzzing, and test coverage. Follows TDD methodology with idiomatic Go practices.
Use when the user asks to verify citations, audit source links, check blog/report/lecture references, or reduce a long bibliography to sources that need human review using the paper-verify CLI or MCP tools.
Use when the user asks to fact-check, verify, or score the citations/sources/references in a document from a chat (no terminal) — extracts citations with bundled code, fetches and judges each source with web tools, then scores through paper-verify's standard 100-point rubric via --from-evidence.
Use when the user wants to download a paper PDF from a DOI (or title, resolved to a DOI first). Tries Unpaywall, arXiv, bioRxiv/medRxiv, PubMed Central, Semantic Scholar, and Sci-Hub mirrors as a last-resort fallback.
MCP definition linter rules reference. Use when bun run lint:mcp or bun run devcheck reports a lint error or warning (format-parity, schema-is-object, name-format, server-json-, etc.) and you need to understand the rule, its severity, and how to fix it. Every rule ID the linter emits has an entry in this doc.
Design the tool surface, resources, and service layer for a new MCP server. Use when starting a new server, planning a major feature expansion, or when the user describes a domain/API they want to expose via MCP. Produces a design doc at docs/design.md that drives implementation.
Use whenever the user mentions Zenodo, depositing or publishing research artifacts (datasets, software, papers, posters) to Zenodo, minting a DOI for a dataset/code release, uploading files to a Zenodo record, creating a new version of a Zenodo deposit, or searching Zenodo records. Covers the full Zenodo REST API…
Use when the user asks to search, inspect, summarize, compare, cite, or reason over locally indexed paper PDFs in rag-paper via MCP tools or direct local Chroma/rag-paper access.