Return a small health report — confirms the server is alive and configured.

Resolve an arXiv ID/URL, bioRxiv URL, DOI, or generic URL to canonical metadata.

For arXiv inputs this hits the arXiv export API to fetch title/authors/abstract. Other sources return the resolved URL with empty bibliographic fields (cheap by design).

Return best-effort full text + section split for a paper.

prefer: one of "auto" (default), "html" (force ar5iv HTML — arXiv only), or "pdf". Sections are normalised to lowercase canonical names: abstract, introduction, methods, experiments, results, discussion, conclusion, limitations, related_work.

Extract a structured methods object from a paper.

Pulls full text, isolates the methods-relevant section(s), then asks Claude (default: claude-sonnet-4-6) to fill out a Pydantic schema with steps, reagents, equipment, and analyses. Validation-enforced — invalid responses trigger one repair attempt before raising.

Requires ANTHROPIC_API_KEY in the server's environment.

Discover the code repo (if any) associated with a paper.

Strategy: scan the paper's full text and abstract for github.com URLs; fall back to Papers With Code lookup for arXiv papers.

Heuristic, no-clone reproducibility assessment of a GitHub repo.

Returns a verdict (likely-reproducible / partial / unlikely / insufficient-info) plus weighted signals: README quality, dependency files, fixture data, notebooks, figure-generating scripts, recent maintenance, license. No code is downloaded or executed. Set GITHUB_TOKEN to raise the API rate limit.

Generate an LLM summary of a paper in one of three modes.

abstract = 2-3 sentences close to the authors' framing. tldr = one-line takeaway. exec = executive summary (what / found / why-it-matters).

Resolve a paper + extract methods + find its code repo + assess reproducibility — in one call.

Returns a MethodsReproReview object. Read narrative first — it's a plain-English summary of everything retrieved, with every numeric score echoed in context (e.g. "moderate confidence (0.72)"). Then:

• status: "ok" (all sub-steps succeeded), "partial" (some failed — see errors), or "empty" (couldn't even resolve the input paper).

• metadata, methods, code_repo, repro_assessment: the structured sub-results. Any step that failed contributes null for its key; null means unavailable, not zero.

• errors: list of {step, error_type, message, hint} — one entry per failed sub-step, with an actionable hint where the failure pattern is recognised (e.g. missing ANTHROPIC_API_KEY, rate-limit, 404, timeout).

For the meaning of numeric scores and verdict buckets, see the "Scores & verdicts explained" section of the README.