@pipeworx/catnap

HIV-1 broadly neutralizing antibody potency (LANL CATNAP: IC50/IC80/ID50 across antibody-virus panels) plus HIV T-cell epitope and antibody-binding-site records (LANL HIV Molecular Immunology Database).

Part of Pipeworx — an MCP gateway connecting AI agents to 1573+ live data sources.

Tools

• catnap_search_neutralization(antibody?, virus?, limit?) — antibody-virus neutralization measurements (IC50/IC80/ID50), the antibody's potency compared across viral strains. Censored bounds (>150, <.05) are returned as censored: true with numeric_value: null — never coerced to a number.
• catnap_antibody_info(name, limit?) — antibody metadata: epitope/binding region, structure (PDB), isolation paper, panel summary stats.
• immunology_search(table, mab_name?, epitope?, protein_name?, limit?) — T-cell epitopes (CTL/CD8+ or T-helper/CD4+) or antibody binding sites, queried live from LANL's own API.

Auth

Keyless. catnap_search_neutralization and catnap_antibody_info return neutralization/antibody data ingested monthly from LANL's CATNAP bulk files (credentials injected by the gateway). immunology_search calls LANL's public JSON API directly on every call — no ingest.

Data sources

• https://www.hiv.lanl.gov/components/sequence/HIV/neutralization/index.html (CATNAP) — antibody-virus neutralization panels (IC50/IC80/ID50), compiled by LANL from published papers. Monthly bulk tab-delimited files (assay_*.txt, abs_*.txt, viruses_*.txt), filename dated at each drop — the ingest scrapes the download page for the current links rather than hardcoding a date. Ingested by workers/data-pipeline/src/datasets/catnap.ts on a monthly cadence into catnap_neutralization, catnap_antibodies, catnap_viruses (see supabase/migrations/170_catnap_neutralization.sql).
• https://www.hiv.lanl.gov/mojo/immunology/api/v2 (HIV Molecular Immunology Database JSON API) — CTL/CD8+, T-helper/CD4+ and antibody epitope/binding-site records. Keyless, queried live, no ingest.

What to get right

• Censored values are never coerced. IC50/IC80/ID50 in the source are sometimes a bound (>150 = not neutralized up to the highest concentration tested; <.05 = fully neutralized at the lowest concentration tested), not a point estimate. Every measurement carries _raw (verbatim string), _value (numeric, null when censored) and _censor ('<'/'>', null otherwise). A >50 stored as 50 would invert a potency ranking.
• Assay context travels with every value. IC50/IC80 from different papers use different protocols and virus stocks — the tool always returns reference/pubmed_id and never implies cross-study comparability just because two values are both labelled "IC50".
• Two different questions live in this one pack. catnap_search_neutralization/catnap_antibody_info answer "how potent is this antibody" (CATNAP); immunology_search answers "where on the virus does this immune response target, and which HLA restricts it" (Immunology DB) — a different upstream database with its own record IDs.

Refresh path

workers/data-pipeline/src/datasets/catnap.ts, registered in workers/data-pipeline/src/datasets/index.ts, schedule: 'monthly'. Re-fetches and re-parses all three CATNAP bulk files each run (the neutralization file is ~200k rows / ~16MB, chunk-upserted with a cursor across invocations); no stale-row delete — CATNAP accumulates measurements rather than retracting them.

Quick Start

Add to your MCP client (Claude Desktop, Cursor, Windsurf, etc.):

{
  "mcpServers": {
    "catnap": {
      "url": "https://gateway.pipeworx.io/catnap/mcp"
    }
  }
}

What this endpoint actually serves

tools/list at https://gateway.pipeworx.io/catnap/mcp returns the tools in the table above plus the shared Pipeworx meta-tools — ask_pipeworx, discover_tools, search_within, remember/recall and the rest of the gateway-wide set. So the tool count you see is larger than this table: a single-pack endpoint currently lists roughly 30 shared tools alongside the pack's own. The connection's initialize response states its exact scope, and is the authoritative answer for a given day.

This is deliberate, not multiplexing by accident. The meta-tools are what let a scoped connection answer a question this pack does not cover — via ask_pipeworx, which routes across the whole catalog — without you adding a second MCP server. There is currently no way to mount a pack endpoint without them; if the extra schemas cost you more context than the routing is worth, connect to the full gateway once rather than to several pack endpoints.

Or connect to the full Pipeworx gateway to get every pack's tools listed directly, instead of just this one's:

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

Both URLs reach the same gateway and the same 1573+ data sources. The only difference is which pack's tools are listed directly; ask_pipeworx reaches all of them from either one.

Standalone (no gateway account)

This package also runs as a local stdio MCP server — no Pipeworx account, no gateway round-trip:

{
  "mcpServers": {
    "catnap": {
      "command": "npx",
      "args": ["-y", "@pipeworx/mcp-catnap"]
    }
  }
}

Or run it directly to confirm it starts:

npx -y @pipeworx/mcp-catnap

It speaks MCP over stdin/stdout and answers initialize/tools/list/tools/call for only this pack's tools — none of the shared meta-tools the gateway connection above adds. Same source, same tools, no ask_pipeworx routing.

Using with ask_pipeworx

Instead of calling tools directly, you can ask questions in plain English — this works on the pack endpoint above as well as on the full gateway:

ask_pipeworx({ question: "your question about Catnap data" })

The gateway picks the right tool and fills the arguments automatically.

More

• Docs and guides
• pipeworx.io

License

MIT