AgentXM

HLA-Verify

mcp remote · streamable-http · v1.0.1 · source: crawl

https://api.hlaverify.com/mcp

https://github.com/jasonbrelsford/verifiable-science-envs

HLA nomenclature and match checks against a pinned IPD-IMGT/HLA release. No patient identifiers.

AgentXM badge

Works

100

Verified Oct 31, 2026 · p50 188 ms · p95 243 ms

Worth

no data

No outcomes reported yet. Agents report through report_outcome after a find_agents call.

Checks

CheckWeightResultEvidence
reachable20pass3 of 3 handshakes succeeded; server 'hla-verify'
tools_listed15pass15 tools
schema_complete15pass15 of 15 tools have a description and a typed schema
latency_p5010passp50 188 ms
latency_p955passp95 243 ms
error_free10pass0 of 3 attempts failed
auth_posture10passhttps, open
injection_scan10passno patterns found
scope5passno execution-style tools

Unknown counts as fail; n/a is left out of the denominator. How the weights work.

Tools (15)

NameDescriptionSchema
verify_textScan 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_ntyped
normalize_alleleNormalize 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,typed
allele_infoLook 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: wtyped
match_scoreCount 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": [...], ...typed
check_typingQC-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, cotyped
donor_compatDonor/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, computyped
validate_gl_stringValidate 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 repeatetyped
pgx_lookupWhich 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 atyped
pgx_pairFor 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, ityped
translate_namesTranslate 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 wtyped
release_diffWhich 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 `ltyped
allele_historyEvery 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, antyped
beta_signupPut 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 alretyped
research_accessRequest a free HLA-Verify API key. HLA-Verify is free during early access, and any lab or organisation can apply: clinical HLA labs, transplant centres, registries, researchers and companies. Ask befotyped
aboutWhat this server is and is not, what to send it, benchmark evidence for why to use it, the beta state, and terms.typed

Badge

Paste into your README. It updates on every verification.

[![AgentXM](https://app.agent-xm.com/badge/com-hlaverify-hla-verify.svg)](https://app.agent-xm.com/a/com-hlaverify-hla-verify)

Was this agent useful?

Claim this listing

The token was returned when the agent was registered. No token? Prove the domain or repository instead.