Verifiable-reward RL environments and evals for scientific domains, starting wit
Verifiable-reward RL environments and evals for scientific domains, starting with HLA/immunogenetics
active Production-safe Score 95/100 http no auth
At a glance
| Endpoint | https://api.hlaverify.com/mcp |
|---|---|
| Source | https://github.com/jasonbrelsford/verifiable-science-envs |
| Transport | http |
| Tools | 15 |
| Auth | none |
| First seen | 2026-10-05 22:48:58 |
| Last checked | 2026-11-17 21:52:10 |
Observed reliability
| 7-day uptime | 100% |
|---|---|
| 24-hour uptime | 100% |
| Handshake success | 100% |
| Latency p50 / p95 | 284 / 479 ms |
| Last successful check | 2026-11-17 21:52:10 |
Measured by Arclan's validator via repeated live MCP handshakes. How this is computed →
Tools (15)
verify_text— Scan HLA typing report text, or model output about HLA, for allele-shaped tokens and classify each one: valid / legacy spelling such as A*02normalize_allele— 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-fiallele_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 flagmatch_score— Count a donor-recipient HLA match by the published counting rules (R1-R6): allele arithmetic over chromosomes, not a donor recommendation. rcheck_typing— QC-check one HLA typing (all loci) against the pinned release: resolves every reported allele, flags unresolvable/outdated/locus-mismatched/donor_compat— Donor/recipient immunogenetic compatibility under two published rule sets: HLA-B leader match (-21 M/T, Petersdorf 2020) for a single HLA-Bvalidate_gl_string— Validate and normalize a GL String (Genotype List, ^ | + ~ / grammar): resolves every allele token, flags outdated/unresolvable names and stpgx_lookup— Which drugs an HLA typing carries a published pharmacogenomic association for. Looks each allele up in hla-pgx-open (CPIC guidelines + Pharmpgx_pair— For a donor-recipient pair, which genome carries each actionable HLA-drug association. Screens both typings as pgx_lookup does and marks evetranslate_names— Translate HLA allele names from one IPD-IMGT/HLA release to another, through each allele's HLA ID, using the official Allelelist_history.txtrelease_diff— Which HLA allele names were added, removed (with the deletion reason and successor) and renamed between two IPD-IMGT/HLA releases, optionallallele_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 lastbeta_signup— Put a user on the beta notification list: one email when anything about early access changes. Ask before calling: it records the address theresearch_access— Get the user a free HLA-Verify API key, instantly. HLA-Verify is free for anyone: the key comes back in this result (status issued, field keabout— What this server is and is not, what to send it, benchmark evidence for why to use it, the beta state, and terms.
Validation history
| Checked | Reachable | Handshake | Latency | Score | State |
|---|---|---|---|---|---|
| 2026-11-17 21:52:10 | ✓ | ✓ | 308 ms | 91 | active |
| 2026-11-17 21:36:57 | ✓ | ✓ | 359 ms | 91 | active |
| 2026-11-17 21:21:43 | ✓ | ✓ | 248 ms | 94 | active |
| 2026-11-17 21:06:34 | ✓ | ✓ | 204 ms | 94 | active |
| 2026-11-17 20:51:23 | ✓ | ✓ | 169 ms | 94 | active |
| 2026-11-17 20:36:22 | ✓ | ✓ | 244 ms | 94 | active |
| 2026-11-17 20:21:21 | ✓ | ✓ | 213 ms | 94 | active |
| 2026-11-17 20:06:19 | ✓ | ✓ | 332 ms | 91 | active |
| 2026-11-17 19:50:32 | ✓ | ✓ | 419 ms | 91 | active |
| 2026-11-17 19:35:23 | ✓ | ✓ | 401 ms | 91 | active |
| 2026-11-17 19:20:05 | ✓ | ✓ | 251 ms | 94 | active |
| 2026-11-17 19:04:47 | ✓ | ✓ | 442 ms | 91 | active |
| 2026-11-17 18:49:33 | ✓ | ✓ | 321 ms | 91 | active |
| 2026-11-17 18:34:23 | ✓ | ✓ | 305 ms | 91 | active |
| 2026-11-17 18:19:15 | ✓ | ✓ | 1039 ms | 87 | active |
Query this programmatically
Agents can pull this record live over the MCP protocol or REST:
get_server("https://api.hlaverify.com/mcp") # via the Arclan MCP endpoint https://arclan.ai/mcp
GET https://arclan.ai/api/registry/api-hlaverify-com-mcp # JSON