Build on Nuclide

The schema file has no dependencies beyond Zod. Copy it (or add the repo as a git submodule) and infer the types; the JSON under /api/v1/ parses with it unchanged.

// types/nuclide.ts: copy src/lib/schema.ts from the repo next to this file, then
import { EntitySchema, type Entity, type Drug, type Trial, KIND_META } from "./schema";

export type Neighbours = Record<string, Array<{ id: string; kind: string; name: string; route: string }>>;
export type EntityResponse = { entity: Entity; route: string; neighbours: Neighbours };

export async function getEntity(id: string): Promise<EntityResponse> {
  const r = await fetch(`https://nuclide.cc/api/v1/entities/${id}.json`);
  if (!r.ok) throw new Error(`Nuclide: ${id} not found`);
  const data = (await r.json()) as EntityResponse;
  data.entity = EntitySchema.parse(data.entity); // validates and applies defaults
  return data;
}

export async function listKind<K extends Entity["kind"]>(kind: K): Promise<Extract<Entity, { kind: K }>[]> {
  const r = await fetch(`https://nuclide.cc/api/v1/${KIND_META[kind].plural}.json`);
  return (await r.json()) as Extract<Entity, { kind: K }>[];
}

Take a cancer and a set of biomarkers, find the products aimed at those targets in that cancer, then pull live recruiting studies from ClinicalTrials.gov for each product. Two static fetches plus the public registry API; no server needed.

const SITE = "https://nuclide.cc";
const indicationId = "tnbc";
const biomarkers = ["trop2", "pdl1", "brca"]; // Nuclide target ids; see /targets/

const { neighbours } = await fetch(`${SITE}/api/v1/entities/${indicationId}.json`).then((r) => r.json());
const products = (neighbours.drug ?? []) as Array<{ id: string; name: string }>;
const drugs = await fetch(`${SITE}/api/v1/drugs.json`).then((r) => r.json());
const byId = new Map(drugs.map((d: { id: string }) => [d.id, d]));

const matches = products
  .map((p) => byId.get(p.id))
  .filter((d) => d && d.targets.some((t: string) => biomarkers.includes(t)) && d.status !== "withdrawn");

for (const d of matches) {
  const q = new URLSearchParams({ "query.intr": d.name.replace(/\s*\(.*?\)\s*/g, " ").trim(), "query.cond": "triple negative breast cancer", "filter.overallStatus": "RECRUITING", pageSize: "5", format: "json" });
  const studies = await fetch(`https://clinicaltrials.gov/api/v2/studies?${q}`).then((r) => r.json());
  console.log(d.name, d.status, studies.studies?.map((s: { protocolSection: { identificationModule: { nctId: string } } }) => s.protocolSection.identificationModule.nctId));
}

The site’s own ask and query surfaces use the same approach; see src/lib/biomarker-match.ts and src/lib/ctgov.ts in the repo for the edge cases (aliases, combination names, condition wording).

One fetch of all.json gives every object plus a backlink map, enough to compute counts, funnels and rankings client-side. This counts products by modality and status for a target.

const { entities, incoming } = await fetch("https://nuclide.cc/api/v1/all.json").then((r) => r.json());
const drugs = entities.filter((e) => e.kind === "drug" && e.targets.includes("her2"));
const funnel = {};
for (const d of drugs) funnel[d.status ?? "unknown"] = (funnel[d.status ?? "unknown"] ?? 0) + 1;
console.table(funnel);

// Everything that links to HER2, grouped by kind (trials, indications, pathways, papers...)
const linkers = incoming["her2"].reduce((m, x) => ({ ...m, [x.kind]: (m[x.kind] ?? 0) + 1 }), {});
console.table(linkers);

// Refresh: meta.json carries the build time; re-fetch when it changes
const { built, counts } = await fetch("https://nuclide.cc/api/v1/meta.json").then((r) => r.json());

all.json is a few megabytes; for a production dashboard fetch the per-kind files you need and cache on meta.json’s built timestamp. The pages under landscape grid and scorecards are built this way at build time.

The MCP server gives an assistant grounded tools instead of a scraped context window. Clone the repo, install, and point your MCP-capable client at it.

git clone https://github.com/casadesante/Nuclide.git && cd Nuclide && npm ci

# Claude Desktop, Cursor, or any MCP client: add a stdio server
{
  "mcpServers": {
    "nuclide": { "command": "npm", "args": ["run", "mcp"], "cwd": "/path/to/Nuclide" }
  }
}

# Tools exposed: search(query, limit), get_entity(id), list_kind(kind),
# for_cancer(indicationId), rank(...). Every answer carries the object url so the
# assistant can cite nuclide.cc and the reader can check the source.

Without MCP, the same grounding works with search.json (compact id, kind, name, tldr, route documents) as a retrieval index and entities/<id>.json as the fetch step.

Every object has an iframe card at /embed/<id>/: kind, status, name and plain-English summary, linking back to the page. Cards are noindex and inherit nothing from your page.