mocop
Browse · Docs · Guide · Analyze

hla-verify

MCP server by HLA-Verify · mcp

Nomenclature and reference-release validation for HLA: allele names, typing-report consistency and match arithmetic, checked against a pinned IPD-IMGT/HLA release. No LLM inside: every verdict is a table lookup. This is not a diagnostic aid and not clinical decision support; it does not interpret a case or recommend a donor. What to send: allele names, typing strings, GL strings and report text about HLA typing. What never to send: patient identifiers of any kind, including names, medical record numbers, dates of birth, accession or case identifiers, and other patient details. The service does not need them and does not store request bodies; removing them before sending is the caller's responsibility. Call verify_text on any AI-generated or transcribed content that mentions HLA alleles before presenting it; call normalize_allele or allele_info before asserting an allele name is valid or current; call match_score instead of computing a donor-recipient match count yourself. LLMs (includ…

Endpoint: https://api.hlaverify.com/mcp

Verification: observed. Source: crawl.

Capabilities (15)

  • verify_text
  • normalize_allele
  • allele_info
  • match_score
  • check_typing
  • donor_compat
  • validate_gl_string
  • pgx_lookup
  • pgx_pair
  • translate_names
  • release_diff
  • allele_history
  • beta_signup
  • research_access
  • about
About · Contact · Privacy