HLA-Verify
Server Details
HLA nomenclature and match checks against a pinned IPD-IMGT/HLA release. No patient identifiers.
- Status
- Healthy
- Uptime
- 100.0% over the last 24 hours
- Last Tested
- Transport
- Streamable HTTP · MCP 2025-11-25
- URL
- Repository
- jasonbrelsford/verifiable-science-envs
- GitHub Stars
- 0
- ChatGPT
- –
- Claude
- –
TDQS
Scored across 15 tools
Most tools have clearly distinct purposes (QC a typing, count a match, check compatibility, look up PGx associations, diff releases). A few pairs blur: allele_info vs normalize_allele both take a shorthand allele and return normalized facts with flags, allele_history vs translate_names both span releases, and check_typing/validate_gl_string/verify_text all validate allele tokens in different containers. The long descriptions do draw the boundaries, so misselection is possible but recoverable.
All snake_case with no camelCase mixing, so it is readable throughout. The conventions differ, though: action-first names (normalize_allele, verify_text, match_score, check_typing) sit alongside noun-only names (allele_info, allele_history, donor_compat, pgx_lookup, release_diff) and meta names (about, beta_signup, research_access).
Fifteen tools sit at the top of the well-scoped band but each maps to a distinct capability: nomenclature lookup/history/translation, typing QC, GL-string validation, text verification, match counting, compatibility rules, PGx pair analysis, and three account/meta tools. Nothing looks redundant enough to drop, and the surface is not padded.
The nomenclature-verification domain is well covered end to end: single allele, full typing, GL Strings, free text, cross-release translation and diffs, plus downstream match/compatibility/PGx analysis and access provisioning. Minor gaps remain, such as no way to list all members of a G/P group (only a count and sample) and no batch allele-history endpoint.
Available Tools
15 toolsaboutARead-onlyIdempotentInspect
What this server is and is not, what to send it, benchmark evidence for why to use it, the beta state, and terms.
Inputs: no named parameters. Returns: api, why, beta, code, +13 more
allele_historyARead-onlyIdempotentInspect
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 deletion note, and a name that never existed is refused with an error result, not guessed at. An allele string only, no patient identifiers.
Inputs: name (required), as_of. Returns: object
allele_infoARead-onlyIdempotentInspect
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 accepts them — legacy spellings (A0101, Cw0702, Cw07:02), the XX code (A02:XX), two-field A02:01g, an optional HLA- prefix — and answer with the facts of the name they stand for plus resolves_to and a flag (deprecated_name, xx_code, lg_notation); an NMDP multiple allele code (A02:AB) returns mac_code, recognised but not expanded. A name that has never existed in any release is refused, not guessed at: the tool returns an error result (HTTP 404 on /v1/allele) and never a near match. A deleted name is answered as deleted, with its successor when the release records one.
Inputs: name (required). Returns: Found: release, name, status and the status-specific fields. Never assigned: on…
beta_signupAIdempotentInspect
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.
Inputs: email (required), org, source, use_case. Returns: ok, status, message, release
check_typingARead-onlyIdempotentInspect
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: {"A": ["A01:01", "A02:01"], "B": [...], "DRB1": [...], ...} (any nomenclature era, G/P group names, A02:XX and two-field A02:01g included; NMDP MAC codes are flagged, not expanded; allele strings only, no patient identifiers).
Inputs: typing (required). Returns: loci, valid, counts, drb345, +4 more
donor_compatARead-onlyIdempotentInspect
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": [...], ...} (allele strings only, no patient identifiers). Decision support only; not a medical device.
Inputs: donor (required), recipient (required). Returns: issues, release, b_leader, attribution, +3 more
match_scoreARead-onlyIdempotentInspect
Count a donor-recipient HLA match by the published counting rules (R1-R6): allele arithmetic over chromosomes, not a donor recommendation. recipient/donor: {"A": ["A01:01","A02: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. Returns count, per-locus verdicts, GvH/HvG mismatch counts, and flags; unresolvable typing yields 'potential', never a confident count.
Inputs: donor (required), recipient (required), framework. Returns: count, flags, release, verdicts, +4 more
normalize_alleleARead-onlyIdempotentInspect
Normalize one reported HLA allele name (any era or reporting shorthand: legacy A0101, Cw0702 or Cw07:02, G/P group names, A02:XX, two-field A02:01g, optional HLA- prefix) to current 2-field form, with G group, P group, serologic equivalent, and flags. NMDP MAC codes (A02:AB) are recognised but not expanded (flag mac_code). A name that does not exist comes back UNRESOLVABLE (flag nonexistent_allele), never corrected to a nearby real one.
Inputs: name (required). Returns: flags, g_group, reported, current_name, +1 more
pgx_lookupARead-onlyIdempotentInspect
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 (A3101, B5701, HLA-B*15:02:01G) and every conversion leaves a flag. Returns per allele the current name, the two-field form, the flags and the associations (source, drug, evidence level, CPIC testing recommendation, implication, recommendation, guideline or annotation URL, PMIDs), plus summary.actionable: the CPIC level-A, allele-positive rows. Guideline lookup over published CPIC and PharmGKB associations, keyed by two-field HLA allele. Decision support only; not a medical device. After an allogeneic transplant the recipient's blood carries the donor's genome, and which genome should drive an HLA-mediated drug alert is an open question (NCT06856226); this lookup reports both and decides nothing. Allele strings only, no patient identifiers.
Inputs: typing, alleles. Returns: scope, alleles, license, release, +3 more
pgx_pairARead-onlyIdempotentInspect
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 support only; not a medical device. After an allogeneic transplant the recipient's blood carries the donor's genome, and which genome should drive an HLA-mediated drug alert is an open question (NCT06856226); this lookup reports both and decides nothing. Allele strings only, no patient identifiers.
Inputs: donor (required), recipient (required). Returns: donor, scope, license, release, +5 more
release_diffARead-onlyIdempotentInspect
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.
Inputs: to (required), from (required), limit, locus. Returns: object
research_accessAIdempotentInspect
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 once: give it to the user straight away. One key per address; asking again returns already_issued and never the key (lost keys: hello@hlaverify.com). Disposable inboxes are refused. Verified labs that need more can set tier "lab" with institution and use_case to apply for the Lab tier (10,000 calls/day, 5,000 typings per call): that is reviewed, and an approved key is emailed.
Inputs: email (required), tier, source, use_case, +2 more. Returns: ok, key, tier, usage, +6 more
translate_namesARead-onlyIdempotentInspect
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 in to), not_yet_named, not_in_from_release, ambiguous (each allele listed) or unknown. Use it when data typed under an older release has to be compared with or reported under a newer one. Lab shorthand (B1501, A02:XX) belongs in normalize_allele first. Allele strings only, no patient identifiers.
Inputs: names (required), to, from. Returns: object
validate_gl_stringARead-onlyIdempotentInspect
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 checking only; send allele names, not patient identifiers.
Inputs: gl (required). Returns: loci, valid, counts, issues, +5 more
verify_textARead-onlyIdempotentInspect
Scan HLA typing report text, or model output about HLA, for allele-shaped tokens and classify each one: valid / legacy spelling such as A0201 or Cw0702 (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 fewer than four fields carries resolution, what that field count does and does not distinguish. Nomenclature checking against a pinned IPD-IMGT/HLA release, not interpretation of a case. Use on any AI-generated or transcribed content mentioning HLA. Send the HLA content only, with patient identifiers removed first.
Inputs: text (required). Returns: clean, counts, tokens, release, +1 more
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
Related MCP Connectors
Germline ACMG/AMP classification, genes, disease associations, literature and API-key case analysis.
dbSNP refSNP records and HGVS/SPDI/rsID normalization for human genetic variants, from NCBI…
Ancestry allele frequencies, LoF constraint, variant lists, and coverage from gnomAD, with ClinVar.
Pharmacogenomics for AI agents: cited drug–gene, gene and rsID lookups plus a medication screen.
Related MCP Servers
- AlicenseNot gradedqualityDmaintenanceEnables real-time pharmacogenomics analysis, including variant clinical significance, drug-gene interactions, and dosing guidelines, by connecting to ClinVar, PharmGKB, gnomAD, and other databases.1MIT
- AlicenseAqualityBmaintenanceGrounds gene-nomenclature work in the HUGO Gene Nomenclature Committee (HGNC) dataset, enabling resolution of gene symbols and IDs to canonical HGNC identifiers, plus cross-references and batch operations.9MIT
- AlicenseNot gradedqualityCmaintenanceEnables resolving genetic variant identifiers (HGVS, dbSNP, ClinVar, gnomAD) to stable ClinGen Allele Registry IDs (CA#) and cross-references, providing a canonical allele identity across genome builds.Apache 2.0
- AlicenseNot gradedqualityDmaintenanceA local-first MCP server that annotates whole-genome VCF files and lets you query pharmacogenomics, disease risk, and carrier status through natural language.7MIT
Glama MCP Gateway
Add one secure layer between your agents and this server.