mcpbeat Sign in

HLA-Verify MCP Server

by hlaverify Your server? Claim it
answering

HLA-Verify is answering right now. Last checked 7 min ago. It exposes 10 tools. Last commit 18 Sep 2026.

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

Uptime history 46 hours of history
46 hours agonow
100.0%
Uptime 24h
92 of 92 checks
10
Tools
read from the server
106 ms
Response time
average over 24h
0
Stars
last commit 18 Sep 2026

What changed 1

Every tool that appeared, vanished or quietly changed what it asks for. Recorded since 17 September 2026. No other catalogue keeps this.

17 Sep a tool appeared research_access

What the code does

We read the source, 23 h ago · tools taken from the live server · rules 3dff92dd89df

Capabilities

What this server is able to do. For an MCP server this is often the job itself — a terminal server runs commands because that is what it is for. Listed so you know what you are plugging in, not as an accusation.

Page executes code built at runtime assets/demo.template.html:110 
  p.innerHTML = bad || d.counts.deleted

Is this your server and something here is wrong? Tell us — corrections are free and do not require a plan.

This code can reach further than it looks

We found places where it runs commands, builds paths or queries from values it is given. None of that is a flaw by itself — it becomes one when the code changes, and code changes quietly between releases. We re-read it on every one.

Three servers free · no card

Connect this server

Endpoint below is the one we actually reach during checks — not the one copied from a README. Last verified 7 min ago.

run in your terminal
claude mcp add hla-verify --transport http https://api.hlaverify.com/mcp
~/Library/Application Support/Claude/claude_desktop_config.json
{
  "mcpServers": {
    "hla-verify": {
      "url": "https://api.hlaverify.com/mcp"
    }
  }
}
~/.codex/config.toml
[mcp_servers.hla-verify]
url = "https://api.hlaverify.com/mcp"
.cursor/mcp.json
{
  "mcpServers": {
    "hla-verify": {
      "url": "https://api.hlaverify.com/mcp"
    }
  }
}
.vscode/mcp.json
{
  "mcpServers": {
    "hla-verify": {
      "url": "https://api.hlaverify.com/mcp"
    }
  }
}

Available tools 10

Read directly from the server with tools/list, grouped by what they act on. If a tool disappears, we record the date.

about
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
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 never existed in any release.
beta
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 should email [email protected] for a beta key instead of waiting.
donor
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. 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.
match
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 nomenclature era; 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.
normalize
normalize_allele
Normalize one reported HLA allele name (any era) to current 2-field form, with G group, P group, serologic equivalent, and flags.
research
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 guaranteed. If it is approved the applicant is emailed a single-use code that takes 100% off a subscription for 12 months at self-serve checkout, with no card and no contract. Re-applying with the same address is safe (status already_recorded) and never overwrites an application that has already been decided. Commercial labs should buy a tier at https://api.hlaverify.com/pricing instead.
typing
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-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": ["A*01:01", "A*02:01"], "B": [...], "DRB1": [...], ...} (any nomenclature era; allele strings only, no patient identifiers).
validate
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 ^ 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.
verify
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, 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.

Endpoints

URLTransportStateLatencyChecked
https://api.hlaverify.com/mcp streamable-http answering 92 ms 7 min ago

Alternatives to HLA-Verify

same job, measured the same way
Dokimo MCP
by ypratap11

Verify AI-agent revenue: recompute a Merkle proof and check it against an on-chain anchor.

3 tools answering
Verifa
by verifa-solutions

Identity verification, document checks, sanctions/PEP screening and case review as agent tools.

20 installs/wk answering
eleata Claim Verifier
by hernaninverso

Grounding/hallucination guard: verify a claim against evidence (Supported/Refuted/NEE).

34 installs/wk local only
Redacta MCP
by nickjlamb

Pseudonymise and restore patient identifiers & PII in text — local, HIPAA Safe Harbor mode.

48 installs/wk local only
Redra
by sacrosaunt

Search current class-action settlements and identify possible matches using structured filters.

5 tools answering
I
Laserbrain
by degibug-del

The drift harness as an MCP server. Offline, no key — a fixed reference an agent checks against.

993 installs/wk local only
LEGAION Verifier
by legaion

Checks legal citations against the official register they should come from, and records it.

answering
Noether Physics
by ranshiv

Physics assistant: checked equations, live simulations, claims verified against arXiv papers

880 installs/wk local only

HLA-Verify — questions

Answers built from our own checks of this server.

What can HLA-Verify do?
It exposes 10 tools, read directly from the server on our last check. Among them: about, allele_info, beta_signup, check_typing, donor_compat, match_score and 4 more. The full list with descriptions is on this page — we take it from the server itself via tools/list, not from a README. How MCP servers expose tools in the first place →
Is HLA-Verify working right now?
We send a real MCP handshake every 15 minutes. Over the last 24 hours 92 of 92 checks got a reply (100.0%), average response time 106 ms. The bar chart above shows every period we have measured.
How do I connect HLA-Verify?
Copy the ready config from this page — we generate it for Claude Code, Claude Desktop, Codex, Cursor and VS Code, each with the file path that client actually reads. It is a remote server, so there is nothing to install — the client connects to the address.
Does HLA-Verify need an API key?
No. HLA-Verify completed a full MCP handshake with us as an anonymous client and listed its tools without asking for anything. All 10 of them are readable on this page. This is what we observed, not what the docs claim.
How fast is HLA-Verify?
It answers our handshake in 106 ms on average, which is faster than 83% of all working MCP servers we measure. That puts it in the quick quarter of the ecosystem. The comparison comes from our own checks across the whole registry, every 15 minutes.
Is HLA-Verify open source?
Yes — it is published under the Apache-2.0 licence, written in JavaScript and 0 stars on GitHub. The source link is on this page, so you can read exactly what it does with your data before you connect it.