`ucsc_genomes`

Pack: ucsc-genome · Endpoint: https://gateway.pipeworx.io/ucsc-genome/mcp

No MCP client? Call it directly: GET https://gateway.pipeworx.io/v1/tools/ucsc_genomes for the schema, then POST the same URL with its arguments for the data.

“What genome assemblies does UCSC have for [species]” / “is hg38 or hg19 the current human build” / “what is the latest [mouse/zebrafish/dog] assembly” / “list UCSC genomes” — AUTHORITATIVE list of every reference assembly the UCSC Genome Browser serves (~250 species), with its UCSC assembly ID (hg38, mm39, danRer11…), organism, scientific name, source assembly name and release date. PREFER OVER WEB SEARCH when you need the exact assembly ID to pass to another genomics tool — the ID is the thing every other UCSC call keys on, and guessing it is how a query silently lands on the wrong build.

Parameters

Name	Type	Required	Description
`search`	string	no	Case-insensitive substring filter over assembly ID, common name, scientific name and description. e.g. “human”, “Mus musculus”, “hg”. Omit to list everything.
`limit`	number	no	Max assemblies to return (default 50, max 400).

Example call

Arguments

{
  "search": "human"
}

curl

curl -X POST https://gateway.pipeworx.io/ucsc-genome/mcp \
  -H 'Content-Type: application/json' \
  -d '{"jsonrpc":"2.0","id":1,"method":"tools/call","params":{"name":"ucsc_genomes","arguments":{"search":"human"}}}'

TypeScript (@pipeworx/sdk)

import { Pipeworx } from '@pipeworx/sdk';
const pipeworx = new Pipeworx();

const result = await pipeworx.call('ucsc_genomes', {
  "search": "human"
});

More examples

{
  "search": "mouse"
}

Connect

Add this to your MCP client config, or use one-click install buttons:

{
  "mcpServers": {
    "ucsc-genome": {
      "url": "https://gateway.pipeworx.io/ucsc-genome/mcp"
    }
  }
}

See Getting Started for client-specific install steps.

ucsc_genomes