HLA-Verify is an MCP server with 10 tools an agent can call, among them about, allele_info, beta_signup. It answers at https://api.hlaverify.com/mcp over streamable HTTP, and it listed its tools to an anonymous client, so no sign-in was needed for that. Our probes reached it 4 of 4 times since 16 September 2026; the last check, on 22 October 2026, succeeded.
HLA nomenclature and match checks against a pinned IPD-IMGT/HLA release. No patient identifiers.
Description as the publisher wrote it.
| Tool | What it does |
|---|---|
about | What this server is and is not, what to send it, benchmark evidence for why to use it, the beta state, and terms. |
allele_info | Look up one exact 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), or deleted (successor). Not found if the name has n Inputs: name |
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 s Inputs: email, org, use_case, source |
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-li Inputs: typing |
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. Rul Inputs: recipient, donor |
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 n Inputs: recipient, donor, framework |
normalize_allele | Normalize one reported HLA allele name (any era) to current 2-field form, with G group, P group, serologic equivalent, and flags. Inputs: name |
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 guarante Inputs: email, institution, use_case, expected_volume, source |
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 ^ b Inputs: gl |
verify_text | Scan HLA typing report text, or model output about HLA, for allele-shaped tokens and classify each one: valid / legacy (with modern form) / deleted (with successor) / fabricated. Nomenclature checking against a pinned IPD-IMGT/HLA release, Inputs: text |
Every block below points at https://api.hlaverify.com/mcp. Pick your client and copy.
claude mcp add --transport http hla-verify https://api.hlaverify.com/mcp
{
"mcpServers": {
"hla-verify": {
"command": "npx",
"args": ["-y", "mcp-remote", "https://api.hlaverify.com/mcp"]
}
}
}{
"mcpServers": {
"hla-verify": {
"url": "https://api.hlaverify.com/mcp"
}
}
}{
"servers": {
"hla-verify": {
"type": "http",
"url": "https://api.hlaverify.com/mcp"
}
}
}{
"context_servers": {
"hla-verify": {
"url": "https://api.hlaverify.com/mcp"
}
}
}{
"mcpServers": {
"hla-verify": {
"serverUrl": "https://api.hlaverify.com/mcp"
}
}
}{
"mcpServers": {
"hla-verify": {
"url": "https://api.hlaverify.com/mcp"
}
}
}name: HLA-Verify
version: 0.0.1
schema: v1
mcpServers:
- name: HLA-Verify
type: streamable-http
url: https://api.hlaverify.com/mcp{
"mcpServers": {
"hla-verify": {
"httpUrl": "https://api.hlaverify.com/mcp"
}
}
}{
"mcpServers": {
"hla-verify": {
"type": "http",
"url": "https://api.hlaverify.com/mcp"
}
}
}{
"mcpServers": {
"hla-verify": {
"url": "https://api.hlaverify.com/mcp"
}
}
}goose://extension?url=https%3A%2F%2Fapi.hlaverify.com%2Fmcp&type=streamable_http&id=hla-verify&name=HLA-Verify
It answered our last check on 22 October 2026 in 161 ms. Over 4 checks since 16 September 2026 it answered 4. Status here comes from Neuronto's own probes, not from the publisher.
Yes. It is published by hlaverify.com and served from api.hlaverify.com, the vendor's own domain: https://api.hlaverify.com/mcp.
10, as returned by the server's own tools/list on 24 September 2026: about, allele_info, beta_signup, check_typing, donor_compat, match_score, normalize_allele, research_access, and 2 more.
It answered our last check on 22 October 2026 in 161 ms. Over 4 checks since 16 September 2026 it answered 4.
Put the server under mcpServers in ~/.cursor/mcp.json with the URL https://api.hlaverify.com/mcp. The exact JSON is above, with the same setup for Claude Code, Claude Desktop, VS Code, Windsurf, Zed, Gemini CLI and the rest.
It listed its tools to an anonymous client, so reading the tool list needs no key. Individual tools can still ask for credentials in their own inputs.
Publisher: com.hlaverify. Endpoint host: api.hlaverify.com. ARD identifier: urn:air:com.hlaverify:mcp:hla-verify.
First indexed 16 September 2026. The tools are exactly what the server returned; nothing on this page
is inferred from its name. Ranking in Neuronto search is never for sale.