Skip to content
HLA-Verify logo

HLA-Verify MCP server

Which MCP servers are HLA-Verify's own, from the official registry and from asking its own domain, whether they answer, and what they offer. A program checked each of these, nobody copied them from a product page.

read 2026-10-24

← Back to HLA-Verify

Whose server it is
  • Registry namecom.hlaverify/hla-verifyverified in the MCP registry

The registry name sits under hlaverify.com. The registry only lets a publisher use that namespace after proving control of the domain through DNS or HTTP.

When we asked itchecked 2026-10-24
  • Stateanswerschecked 2026-10-24
  • Tools15
  • Server calls itselfhla-verify
  • Server version1.0.1
  • Protocol version2025-06-18

On 2026-10-24 the server answered initialize and tools/list without a sign-in. First answer in 279 ms.

Should an agent connect itNot proven either way yet
  • Its tools do every use case we checked: check allele names in typing reports against a pinned release; flag fabricated or deleted allele names in model output; normalize legacy typings to current nomenclature.
  • Checked on 4 of the 7 days it takes to judge reliability.

Once connected

  • For "flag fabricated or deleted allele names in model output", the likely first call is verify_text.
  • For "normalize legacy typings to current nomenclature", the likely first call is normalize_allele.

Said by rules from the measurements above. The likely first call is a model's pick from the tool list; read its description before relying on it.

Measured dailydaily checks: 4, the first on 2026-10-24
  • INITE MCP scoreafter a weeka score needs 7 daily checks: 4 so far
  • What an agent can do with it3 of 3 use cases
  • Answeredmeasuring4 of the 7 daily checks it takes to print a share
  • Median first answer122 ms
  • Space in an agent's context≈ 4,102 tokensthe definitions of all its tools (15), which an agent carries on every turn
  • Tool definitionsA · 99 of 100
  • Typed results15 of 15 toolsdeclared outputSchema: results come typed, read once
  • Parameters without a description: in 1 of 15

What an agent can do with it

  • can do · check allele names in typing reports against a pinned release
  • can do · flag fabricated or deleted allele names in model output
  • can do · normalize legacy typings to current nomenclature

Each of the product's use cases, put to Jev against this server's tool list: can an agent do it with these tools?

Worth a look

None of the five warning signs in these definitions.

A program checks the server once a day: initialize and tools/list, no model. Tokens are the definitions' length at about four characters a token. The grade averages six checks of every tool's name, description, schema and annotations; it says how well the tools are described, not whether they work. The score weighs what was measured and nothing else: answering (25%), doing the product's job (25%), definitions (20%), context (10%), use (10%) and how readily a client connects (10%). A part that was not measured is left out, and a hidden instruction caps the score at 40. The state of vendors' MCP servers: method and numbers →

Tools it offers15 tools · read 2026-10-24
  • 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…

  • 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…

  • 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…

  • 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…

  • 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…

  • 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…

  • 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 ^…

  • 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…

  • 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…

  • 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`…

  • 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…

  • 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…

  • 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…

  • 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…

  • about

    What this server is and is not, what to send it, benchmark evidence for why to use it, the beta state, and terms.

How to connect

Add the server to your MCP client config. Claude Desktop, Cursor and most other clients read this shape:

{
  "mcpServers": {
    "hla-verify": {
      "type": "http",
      "url": "https://api.hlaverify.com/mcp"
    }
  }
}

Add it

Claude Code, in a terminal

claude mcp add --transport http hlaverify https://api.hlaverify.com/mcp

Add to CursorAdd to VS Code

claude.ai, ChatGPT and other clients: add https://api.hlaverify.com/mcp as a custom connector in the settings.

Each line is something a program found when it went looking: the registry entry, the server's own answer, a spec that parses. A missing line means we did not find it, not that it does not exist.