{"id":"com.hlaverify/hla-verify","slug":"com-hlaverify-hla-verify","title":"HLA-Verify","description":"HLA nomenclature and match checks against a pinned IPD-IMGT/HLA release. No patient identifiers.","version":"1.0.1","publisher":{"kind":"domain","id":"hlaverify.com","label":"hlaverify.com","url":"https://hlaverify.com"},"website":"https://hlaverify.com","repository":"https://github.com/jasonbrelsford/verifiable-science-envs","remotes":[{"type":"streamable-http","url":"https://api.hlaverify.com/mcp","headers":[{"description":"Optional. Without a key /mcp shares the free tier (60 requests/minute); keys: https://api.hlaverify.com/pricing","isSecret":true,"name":"X-API-Key"}]}],"packages":[],"published":"2026-09-16","updated":"2026-09-16","status":"online","auth":"","latency_ms":1523,"checked":"2026-11-19","uptime":100,"checks":3,"tools":[{"name":"verify_text","title":"","description":"Scan HLA typing report text, or model output about HLA, for allele-shaped tokens and classify each one: valid / legacy spelling such as A*0201 or Cw*0702 (valid, with modern form and flag deprecated_name) / G-P group / deleted (with successor) / hallucinated (an invented name, never passed as real) / NMDP MAC code (seen, not expanded) / KIR name (out of scope, not checked); a valid token with fewe","read_only":true},{"name":"normalize_allele","title":"","description":"Normalize one reported HLA allele name (any era or reporting shorthand: legacy A*0101, Cw*0702 or Cw*07:02, G/P group names, A*02:XX, two-field A*02:01g, optional HLA- prefix) to current 2-field form, with G group, P group, serologic equivalent, and flags. NMDP MAC codes (A*02:AB) are recognised but not expanded (flag mac_code). A name that does not exist comes back UNRESOLVABLE (flag nonexistent_","read_only":true},{"name":"allele_info","title":"","description":"Look up one name in the pinned release and return what it is: assigned (G/P group, first release, confirmed status, WMDA serology, null flag), valid_prefix (member count and sample, plus resolution: what a name with fewer than four fields does and does not distinguish), group (a G or P group name: member count and sample), or deleted (successor). Reported shorthands are accepted as /v1/normalize a","read_only":true},{"name":"match_score","title":"","description":"Count a donor-recipient HLA match by the published counting rules (R1-R6): allele arithmetic over chromosomes, not a donor recommendation. recipient/donor: {\"A\": [\"A*01:01\",\"A*02:01\"], \"B\": [...], ...} (two reported alleles per locus, any nomenclature era including G/P group names such as A*02:01:01G; allele strings only, no patient identifiers). framework: 6/6, 8/8, 10/10, 12/12, or antigen. Retu","read_only":true},{"name":"check_typing","title":"","description":"QC-check one HLA typing (all loci) against the pinned release: resolves every reported allele, flags unresolvable/outdated/locus-mismatched/null alleles, flags too-many/single/homozygous per locus, computes the B-leader (-21 M/T) and KIR-ligand (C1/C2/Bw4) profile, and DRB3/4/5 expected-vs-reported. Nomenclature and internal-consistency checking of the report, not clinical interpretation. typing: ","read_only":true},{"name":"donor_compat","title":"","description":"Donor/recipient immunogenetic compatibility under two published rule sets: HLA-B leader match (-21 M/T, Petersdorf 2020) for a single HLA-B mismatch, and KIR ligand (C1/C2/Bw4) class comparison, computed over each side's full typing QC. Rule checking against published frameworks; it does not rank or recommend a donor. recipient/donor: {\"A\": [...], \"B\": [...], \"C\": [...], \"DRB1\": [...], ...} (allel","read_only":true},{"name":"validate_gl_string","title":"","description":"Validate and normalize a GL String (Genotype List, ^ | + ~ / grammar): resolves every allele token, flags outdated/unresolvable names and structural problems (mixed loci within a slash-list, a repeated locus within a haplotype or across ^ blocks, more than two haplotypes, differing loci across a genotype or genotype list, empty elements), and returns the normalized string. Grammar and nomenclature","read_only":true},{"name":"pgx_lookup","title":"","description":"Which drugs an HLA typing carries a published pharmacogenomic association for. Looks each allele up in hla-pgx-open (CPIC guidelines + PharmGKB clinical annotations, CC BY-SA, snapshot date in every answer) after normalizing the name first, so any era or shorthand works (A*3101, B*5701, HLA-B*15:02:01G) and every conversion leaves a flag. Returns per allele the current name, the two-field form, th","read_only":true},{"name":"pgx_pair","title":"","description":"For a donor-recipient pair, which genome carries each actionable HLA-drug association. Screens both typings as pgx_lookup does and marks every CPIC level-A, allele-positive association in_recipient, in_donor, discordant (present in exactly one) and whose_hla (both / recipient_only / donor_only). Guideline lookup over published CPIC and PharmGKB associations, keyed by two-field HLA allele. Decision","read_only":true},{"name":"translate_names","title":"","description":"Translate HLA allele names from one IPD-IMGT/HLA release to another, through each allele's HLA ID, using the official Allelelist_history.txt (every release since 1.05.0). Give the names as they were written in release `from` (omit `from` to accept a name used in any release); `to` defaults to the current release. Each row says unchanged, renamed (to_name), deleted (reason, successor and its name i","read_only":true},{"name":"release_diff","title":"","description":"Which HLA allele names were added, removed (with the deletion reason and successor) and renamed between two IPD-IMGT/HLA releases, optionally for one locus. Counts are complete; each list is cut at `limit` and `truncated` says so. Use it to see what a release update changes before re-running or re-reporting typings.","read_only":true},{"name":"allele_history","title":"","description":"Every name the allele behind an HLA name has had, release by release since IPD-IMGT/HLA 1.05.0: its HLA ID, current name, the first and last release that used this name, the full timeline of names, and the deletion note if the name was retired. `as_of` adds what it was called in that release. Use it to answer when a name appeared, changed or disappeared; a retired name is answered with its deletio","read_only":true},{"name":"beta_signup","title":"","description":"Put a user on the beta notification list: one email when anything about early access changes. Ask before calling: it records the address they give you. Re-signing the same address is safe (status already_recorded). Someone who needs a higher rate limit today should get a free key with research_access: it is issued instantly.","read_only":false},{"name":"research_access","title":"","description":"Get the user a free HLA-Verify API key, instantly. HLA-Verify is free for anyone: the key comes back in this result (status issued, field key) with 1,000 calls/day, 250 typings per call and 60 requests/minute; the user sends it as the X-API-Key header (or connects this MCP server with it). Ask before calling: it stores the email address with the key, used for service notices only. The key is shown","read_only":false},{"name":"about","title":"","description":"What this server is and is not, what to send it, benchmark evidence for why to use it, the beta state, and terms.","read_only":true}],"server_info":{"name":"hla-verify","version":"1.0.1"},"category":"health","tags":["research"],"kind":"remote","source":"registry","submitted":{},"first_party":true,"domain_rank":null,"score":100,"indexable":true,"first_seen":"2026-09-16","stars":0,"badges":[],"sponsor":null,"page":"https://agentsindex.org/agents/com-hlaverify-hla-verify/"}