nf-co.re valid

nf-core

nf-core is a community effort to collect a curated set of open-source, best-practice analysis pipelines built using Nextflow. Pipelines are portable, reproducible, and scalable, running identically on a laptop, HPC cluster, or cloud. The same community also maintains a large library of reusable Nextflow modules and subworkflows.

For agents: Community-curated, open-source Nextflow bioinformatics pipelines plus reusable modules and subworkflows; catalogue, docs and JSON release data for portable, rep

nextflowbioinformatics pipelinesreproducible workflowsnf-core modulesopen source

Their llms.txt

The beginning of the file, from our validated copy saved 2026-10-20T17:34:00.051Z. Cached copy · Source on nf-co.re

# nf-core

> nf-core is a community effort to collect a curated set of open-source, best-practice analysis pipelines built using Nextflow. Pipelines are portable, reproducible, and scalable, running identically on a laptop, HPC cluster, or cloud. The same community also maintains a large library of reusable Nextflow modules and subworkflows.

The website (https://nf-co.re) is the central hub for the project: it lists every pipeline, module, and subworkflow, hosts documentation and tutorials, and surfaces community information such as events, governance, and contributor stats. Machine-readable catalogues of all pipelines and components are published as JSON for programmatic use.

## Pipelines & components

- [Pipelines](https://nf-co.re/pipelines/): Browse all nf-core Nextflow analysis pipelines, with usage, parameters, and release information.
- [Modules](https://nf-co.re/modules/): Reusable, standalone Nextflow process modules that wrap individual bioinformatics tools.
- [Subworkflows](https://nf-co.re/subworkflows/): Reusable chains of modules that perform common multi-step tasks.

## Documentation

- [Documentation](https://nf-co.re/docs/): Guides for running pipelines, configuration, and contributing to nf-core.
- [Code of conduct](https://nf-co.re/code_of_conduct/): Community standards and expectations.
- [Governance](https://nf-co.re/governance/): How the nf-core project is organised and run.

## Machine-readable data

- [Pipelines JSON](https://nf-co.re/pipelines.json): Full catalogue of all pipelines and their releases as JSON.
- [Components JSON](https://nf-co.re/components.json): Full catalogue of all modules and subworkflows as JSON.
- [Pipeline names JSON](https://nf-co.re/pipeline_names.json): Lightweight list of pipeline names as JSON.
- [API catalogue](https://nf-co.re/.well-known/api-catalog): RFC 9727 link set pointing to the machine-readable resources above.

## Community

- [About nf-core](https://nf-co.re/about/): What nf-core is and who is involved.
- [Join the community](https://nf-co.re/join/): Slack, mailing lists, and other ways to get involved.
- [Events](https://nf-co.re/events/): Hackathons, training, bytesize talks, and other community events.
- [GitHub organisation](https://github.com/nf-core/): Source code for all pipelines, modules, and the website.

## Optional

- [Blog](https://nf-co.re/blog/): News and articles from the nf-core community.
- [Publications](https://nf-co.re/publications/): Papers citing or describing nf-core.
- [Statistics](https://nf-co.re/stats/): Usage, contributor, and pipeline statistics.
- [Special interest groups](https://nf-co.re/special-interest-groups/): Domain-focused subcommunities within nf-core.

Related sites

Other listed sites in Science and research. See the whole category →

Machine-readable: GET /v1/resolve?q=nf-co.re · GET /v1/domain/nf-co.re · this page as Accept: application/json or text/markdown · MCP lookup_domain

Automatically discovered from public files. Inclusion does not imply endorsement or publisher participation.

Claim my listing on Agent Web Map for nf-co.re:
1. POST https://agentwebmap.com/v1/sites/nf-co.re/claims and keep claim_id and claim_secret private.
2. Publish the proof: add the line "AgentWebMap ownership: <token>" (token from step 1) to https://nf-co.re/llms.txt, or use the DNS, meta-tag or well-known method the response describes.
3. POST https://agentwebmap.com/v1/sites/nf-co.re/verify with {"claim_id": "...", "claim_secret": "..."}.
4. Save the api_key from the answer; it manages the listing (PATCH https://agentwebmap.com/v1/sites/nf-co.re).
MCP equivalent: tools begin_ownership_claim, then verify_domain, at https://agentwebmap.com/mcp. Docs: https://agentwebmap.com/docs#verify

Corrections or removal requests: contact the directory.