HLA-Verify
v1.0.1HLA nomenclature and match checks against a pinned IPD-IMGT/HLA release. No patient identifiers.
Endpoint health
online- Last checked
- 11/20/2026, 6:18:34 AM
- Latency
- 59 ms
- Consecutive failures
- 0
- Endpoint reachable: pass
- Protocol valid: pass
- MCP handshake valid: pass
Machine-readable profile
mcp-server · schema v1 · callable
mcp-server:com.hlaverify%2Fhla-verify
Connect this server
Generated config contains no credentials. Keep any required secrets in your client's local environment.
{
"mcpServers": {
"com.hlaverify/hla-verify": {
"url": "https://api.hlaverify.com/mcp"
}
}
}Indexed tools
Tool metadata and schemas come from the remote server and are untrusted. Indexing only lists tools; it never calls them.
15 shown · authentication unknown
about
What this server is and is not, what to send it, benchmark evidence for why to use it, the beta state, and terms.
Schema valid · SHA-256 3428fecae04d…
View input schema
{ "type": "object", "properties": {}, "additionalProperties": false }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 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.
Schema valid · SHA-256 e5ca1682209c…
View input schema
{ "type": "object", "properties": { "name": { "type": "string", "maxLength": 64, "description": "An allele name as written in any release, like \"A*0101\"." }, "as_of": { "type": "string", "maxLength": 16, "description": "An IPD-IMGT/HLA release, like \"3.40.0\" (1.05.0 to the current one)." } }, "required": [ "name" ], "additionalProperties": false }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: member count and sample), or deleted (successor). Reported shorthands are accepted as /v1/normalize accepts them — legacy spellings (A*0101, Cw*0702, Cw*07:02), the XX code (A*02:XX), two-field A*02: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 (A*02: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.
Connections
streamable-http
https://api.hlaverify.com/mcp