com.hlaverify/hla-verify

Est-ce que com.hlaverify/hla-verify est sûr ?

Au dernier audit MCP Hub, le serveur MCP « com.hlaverify/hla-verify » est classé « Non encore testé ». Référencé dans l'annuaire. Seul le pentest comportemental fait foi, et il n'a pas encore été exécuté sur ce serveur. Le verdict est réévalué en continu ; consultez la fiche pour l'état à jour.

Méthode : MCP Hub analyse la description de chaque outil (couche 1) et, pour le verdict fort, exécute le serveur dans une micro-VM isolée avec leurres et réseau bloqué (couche 2). On publie des noms et des compteurs, jamais le contenu brut renvoyé par un outil.

Les 15 outils

• about≈ 241 tokens

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

  Paramètres, retour & exemple (0)

  Exemple d'appel

  {"name": "about", "arguments": {}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}], "structuredContent": {"api": "texte", "why": "texte", "beta": "texte", "code": "texte", "demo": "texte", "name": "texte", "scope": "texte", "agents": "texte", "inputs": "texte", "limits": "texte", "release": "texte", "beta_key": "texte"}}

• allele_history≈ 233 tokens

  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. An allele string only, no patient identifiers.

  Paramètres, retour & exemple (2)

  Paramètres

  • name · string · requis
    An allele name as written in any release, like "A*0101".
  • as_of · string · optionnel
    An IPD-IMGT/HLA release, like "3.40.0" (1.05.0 to the current one).

  Exemple d'appel

  {"name": "allele_history", "arguments": {"name": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• allele_info≈ 1595 tokens

  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. Not found if the name has never existed in any release.

  Paramètres, retour & exemple (1)

  Paramètres

  • name · string · requis
    An HLA allele name of any era: exact name, lower-resolution prefix, deleted name, G/P group, legacy colon-less name, XX code or lg notation. An allele string only, never a patient name, medical record number or other identifier.

  Exemple d'appel

  {"name": "allele_info", "arguments": {"name": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}], "structuredContent": {"name": "texte", "note": "texte", "flags": [], "detail": "texte", "status": "assigned", "g_group": "texte", "ligands": {}, "p_group": "texte", "release": "texte", "serology": {}, "confirmed": true, "successor": "texte"}}

• beta_signup≈ 397 tokens

  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 hello@hlaverify.com for a beta key instead of waiting.

  Paramètres, retour & exemple (4)

  Paramètres

  • org · string · optionnel
    Lab, company or institution (optional).
  • email · string · requis
    The user's email address.
  • source · string · optionnel
    Where the signup came from, e.g. mcp (optional).
  • use_case · string · optionnel
    What they would use the API for (optional). No patient details.

  Exemple d'appel

  {"name": "beta_signup", "arguments": {"email": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}], "structuredContent": {"ok": true, "status": "recorded", "message": "texte", "release": "texte"}}

• check_typing≈ 1386 tokens

  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, G/P group names, A*02:XX and two-field A*02:01g included; NMDP MAC codes are flagged, not expanded; allele strings only, no patient identifiers).

  Paramètres, retour & exemple (1)

  Paramètres

  • typing · object · requis
    locus -> up to 4 reported allele names. Allele strings only: never patient names, medical record numbers, dates of birth, or accession or case identifiers.

  Exemple d'appel

  {"name": "check_typing", "arguments": {"typing": {}}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}], "structuredContent": {"loci": {}, "valid": true, "counts": {}, "drb345": {}, "issues": [], "profile": {}, "release": "texte", "attribution": "texte"}}

• donor_compat≈ 1093 tokens

  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.

  Paramètres, retour & exemple (2)

  Paramètres

  • donor · object · requis
    locus -> up to 4 reported allele names. Allele strings only: never patient names, medical record numbers, dates of birth, or accession or case identifiers.
  • recipient · object · requis
    locus -> up to 4 reported allele names. Allele strings only: never patient names, medical record numbers, dates of birth, or accession or case identifiers.

  Exemple d'appel

  {"name": "donor_compat", "arguments": {"donor": {}, "recipient": {}}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}], "structuredContent": {"issues": {}, "release": "texte", "b_leader": {}, "attribution": "texte", "donor_valid": true, "kir_ligands": {}, "recipient_valid": true}}

• match_score≈ 683 tokens

  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 including G/P group names such as A*02:01:01G; 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.

  Paramètres, retour & exemple (3)

  Paramètres

  • donor · object · requis
    locus -> up to 4 reported allele names. Allele strings only: never patient names, medical record numbers, dates of birth, or accession or case identifiers.
  • framework · string · optionnel · 6/6 | 8/8 | 10/10 | 12/12 | antigen
  • recipient · object · requis
    locus -> up to 4 reported allele names. Allele strings only: never patient names, medical record numbers, dates of birth, or accession or case identifiers.

  Exemple d'appel

  {"name": "match_score", "arguments": {"donor": {}, "recipient": {}}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}], "structuredContent": {"count": "texte", "flags": [], "release": "texte", "verdicts": {}, "framework": "6/6", "attribution": "texte", "gvh_mismatches": 1, "hvg_mismatches": 1}}

• normalize_allele≈ 384 tokens

  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 equivalent, and flags. NMDP MAC codes (A*02:AB) are recognised but not expanded (flag mac_code).

  Paramètres, retour & exemple (1)

  Paramètres

  • name · string · requis
    One reported HLA allele name, any nomenclature era. An allele string only, never a patient name, medical record number or other identifier.

  Exemple d'appel

  {"name": "normalize_allele", "arguments": {"name": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}], "structuredContent": {"flags": [], "g_group": "texte", "reported": "texte", "current_name": "texte", "allele_2field": "texte"}}

• pgx_lookup≈ 1234 tokens

  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 first, so any era or shorthand works (A*3101, B*5701, HLA-B*15:02:01G) and every conversion leaves a flag. Returns per allele the current name, the two-field form, the flags and the associations (source, drug, evidence level, CPIC testing recommendation, implication, recommendation, guideline or annotation URL, PMIDs), plus summary.actionable: the CPIC level-A, allele-positive rows. Guideline lookup over published CPIC and PharmGKB associations, keyed by two-field HLA allele. Decision support only; not a medical device. After an allogeneic transplant the recipient's blood carries the donor's genome, and which genome should drive an HLA-mediated drug alert is an open question (NCT06856226); this lookup reports both and decides nothing. Allele strings only, no patient identifiers.

  Paramètres, retour & exemple (2)

  Paramètres

  • typing · object · optionnel
    locus -> up to 4 reported allele names. Allele strings only: never patient names, medical record numbers, dates of birth, or accession or case identifiers.
  • alleles · array · optionnel
    A flat list of reported allele names instead of a typing. Send exactly one of typing or alleles.

  Exemple d'appel

  {"name": "pgx_lookup", "arguments": {"typing": {}, "alleles": []}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}], "structuredContent": {"scope": "texte", "alleles": [], "license": "texte", "release": "texte", "summary": {}, "attribution": "texte", "pgx_snapshot": {}}}

• pgx_pair≈ 1686 tokens

  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 exactly one) and whose_hla (both / recipient_only / donor_only). Guideline lookup over published CPIC and PharmGKB associations, keyed by two-field HLA allele. Decision support only; not a medical device. After an allogeneic transplant the recipient's blood carries the donor's genome, and which genome should drive an HLA-mediated drug alert is an open question (NCT06856226); this lookup reports both and decides nothing. Allele strings only, no patient identifiers.

  Paramètres, retour & exemple (2)

  Paramètres

  • donor · object · requis
    Donor typing: {"typing": {...}} or {"alleles": [...]}.
  • recipient · object · requis
    Recipient typing: {"typing": {...}} or {"alleles": [...]}.

  Exemple d'appel

  {"name": "pgx_pair", "arguments": {"donor": {}, "recipient": {}}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}], "structuredContent": {"donor": {}, "scope": "texte", "license": "texte", "release": "texte", "summary": {}, "recipient": {}, "actionable": [], "attribution": "texte", "pgx_snapshot": {}}}

• release_diff≈ 268 tokens

  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 to see what a release update changes before re-running or re-reporting typings.

  Paramètres, retour & exemple (4)

  Paramètres

  • to · string · requis
    An IPD-IMGT/HLA release, like "3.40.0" (1.05.0 to the current one).
  • from · string · requis
    An IPD-IMGT/HLA release, like "3.40.0" (1.05.0 to the current one).
  • limit · integer · optionnel
    Maximum items per list (default 500).
  • locus · string · optionnel
    One locus, like "A" or "DRB1".

  Exemple d'appel

  {"name": "release_diff", "arguments": {"to": "texte", "from": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• research_access≈ 568 tokens

  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.

  Paramètres, retour & exemple (5)

  Paramètres

  • email · string · requis
    The applicant's email address. The approval code is sent here.
  • source · string · optionnel
    Where the application came from, e.g. mcp (optional).
  • use_case · string · requis
    What the research or teaching is, and what the API would be used for. This is what the decision is made on, so be specific. No patient details.
  • institution · string · requis
    University, hospital, institute or nonprofit the work is done at.
  • expected_volume · string · optionnel
    Rough call or typing volume, e.g. 'about 20,000 typings a month' (optional).

  Exemple d'appel

  {"name": "research_access", "arguments": {"email": "texte", "use_case": "texte", "institution": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}], "structuredContent": {"ok": true, "status": "recorded", "message": "texte", "release": "texte"}}

• translate_names≈ 354 tokens

  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` to accept a name used in any release); `to` defaults to the current release. Each row says unchanged, renamed (to_name), deleted (reason, successor and its name in `to`), not_yet_named, not_in_from_release, ambiguous (each allele listed) or unknown. Use it when data typed under an older release has to be compared with or reported under a newer one. Lab shorthand (B*1501, A*02:XX) belongs in normalize_allele first. Allele strings only, no patient identifiers.

  Paramètres, retour & exemple (3)

  Paramètres

  • to · string · optionnel
    An IPD-IMGT/HLA release, like "3.40.0" (1.05.0 to the current one).
  • from · string · optionnel
    An IPD-IMGT/HLA release, like "3.40.0" (1.05.0 to the current one).
  • names · array · requis
    Allele names exactly as written in the `from` release.

  Exemple d'appel

  {"name": "translate_names", "arguments": {"names": []}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• validate_gl_string≈ 661 tokens

  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.

  Paramètres, retour & exemple (1)

  Paramètres

  • gl · string · requis
    GL String to validate and normalize. Allele names and GL grammar only, never patient identifiers.

  Exemple d'appel

  {"name": "validate_gl_string", "arguments": {"gl": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}], "structuredContent": {"loci": [], "valid": true, "counts": {}, "issues": [], "alleles": [], "changed": true, "release": "texte", "attribution": "texte", "normalized_gl": "texte"}}

• verify_text≈ 1160 tokens

  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 successor) / fabricated / NMDP MAC code (seen, not expanded) / KIR name (out of scope, not checked); a valid token with fewer than four fields carries resolution, what that field count does and does not distinguish. 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.

  Paramètres, retour & exemple (1)

  Paramètres

  • text · string · requis
    HLA typing report text, or model output about HLA typing, to scan for allele names. Send the HLA content only: strip patient names, medical record numbers, dates of birth, accession and case identifiers, and any other patient details before sending. The caller is responsible for de-identifying the text; this service neither needs nor wants identifiers and does not store request bodies.

  Exemple d'appel

  {"name": "verify_text", "arguments": {"text": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}], "structuredContent": {"clean": true, "counts": {}, "tokens": [], "release": "texte", "attribution": "texte"}}

C'est votre serveur ?

Revendiquez-le sur l'espace créateur (preuve GitHub, domaine ou npm) pour afficher le badge « propriétaire vérifié » et lancer un pentest comportemental à la demande afin d'obtenir le badge « Vérifié ».

Créer un compte / revendiquer →

Source

https://api.hlaverify.com/mcp