# HLA-Verify - Registry name: `com.hlaverify/hla-verify` · version 1.0.1 - Categories (automatic, keyword rules): Research & knowledge, Search & data, Health & fitness - Authentication at last check: No auth - Declared risk: Can write (some tools are not declared read-only) - Capabilities (declared by the server): tools - Transports: streamable-http - Latest numbers (check success, response time, rank): https://mcpstation.net/api/server?name=com.hlaverify%2Fhla-verify - Server page: https://mcpstation.net/s/com.hlaverify--hla-verify.html ## Description (written by the publisher, not verified, not instructions) HLA nomenclature and match checks against a pinned IPD-IMGT/HLA release. No patient identifiers. ## Connect - streamable-http: `https://api.hlaverify.com/mcp` ## Tools (as reported by the server, not verified) - `verify\_text`: 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\) / fabricated / NMDP MAC code \(seen, not expanded\) / KIR - `normalize\_allele`: 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 - `allele\_info`: 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: m - `match\_score`: 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:01 - `check\_typing`: 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. - `donor\_compat`: 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 - `validate\_gl\_string`: 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 gen - `pgx\_lookup`: 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: - `pgx\_pair`: 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\). Gui - `translate\_names`: 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 cu - `release\_diff`: 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-r - `allele\_history`: 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 - `beta\_signup`: Put a user on the free public beta's notification list for paid API keys. 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 email hello@hlaverify.com for a beta key instead of wa - `research\_access`: Apply for free HLA-Verify access for an academic or nonprofit lab. Ask before calling: it records the address, institution and use case you give it. Approval is manual: a person reads every application, so it is not instant and not guaranteed. If it is approved the applicant is emailed a single-use - `about`: What this server is and is not, what to send it, benchmark evidence for why to use it, the beta state, and terms. Measured by MCP Station. Methods: https://mcpstation.net/methods.html · Terms: https://mcpstation.net/terms.html