Health · Remote MCP server
HLA-Verify
HLA nomenclature and match checks against a pinned IPD-IMGT/HLA release. No patient identifiers.
What the MCP Registry states
The entry as published to the official MCP Registry (read 2026-10-04), latest version.
- Registry name
com.hlaverify/hla-verify- Version
- 1.0.1
- Status
- Active
- Category
- health
- Transport
- Streamable HTTP
- Published
- 2026-09-16
- Updated
- 2026-09-16
- Publisher
- com.hlaverify
- Namespace
- Namespace verified by the MCP Registry via the domain hlaverify.com · how
- Website
- hlaverify.com
- Repository
- github.com/jasonbrelsford/verifiable-science-envs (folder edge)
- Source
- Registry API entry
Remote endpoints
| Transport | URL | Headers declared |
|---|---|---|
| Streamable HTTP | https://api.hlaverify.com/mcp | X-API-Key (secret) |
Live check
This directory connected to each remote endpoint and asked for its list of tools. The check connects and lists tools only; it doesn't run tools, sign in or test security.
- Reachable
- Yes (HTTP 200)
- Handshake
- hla-verify 1.0.1 · protocol 2025-06-18
- Tools discovered
- 10:
verify_text,normalize_allele,allele_info,match_score,check_typing,donor_compat,validate_gl_string,beta_signup,research_access,about - Checked on
- 2026-10-05
How to connect HLA-Verify
HLA-Verify is a remote MCP server: there is nothing to install. Its endpoint is https://api.hlaverify.com/mcp, served over Streamable HTTP. In an assistant that accepts remote MCP servers (often under a setting named connectors, integrations or tools), add a new server and give it this URL; in a client configured by file, add it as a remote (HTTP) server with the same URL.
The registry entry declares an HTTP header for the connection: X-API-Key (secret). A secret header usually carries an API key or token issued by the service; clients that accept custom headers set it with the server's URL.
Derived from the registry entry; the live check above only shows whether the endpoint answered. What the server does, and on what terms, is set by its publisher; check its repository or website before giving it access to your accounts or files. How to add an MCP server to an assistant · Before you connect
More health servers
| Server | Runs |
|---|---|
| HerStackRead-only UK women's midlife health guidance: search, PubMed-backed evidence, Solgar UK picks. | Remote · HTTPLive check: ✓ handshake |
| Hevy MCP (Remote)Hosted/gateway-ready Hevy fitness MCP: workouts, routines, templates. | Local · HTTP |
| Hevy MCP ServerMCP server for managing workouts, routines, and exercise data through the Hevy API. | Local · stdio |
| Hl7 Fhir Bridge MCPHL7 v2 / FHIR healthcare bridge - parse, map, validate, govern PHI (HIPAA/MDR). | Local · stdio |
| Hormonaly Clinical Intelligence24 tools for evidence-graded clinical queries, hormones, peptides, longevity & drug interactions. | Remote · HTTP, SSELive check: sign-in required |
| hypokratesPharmacovigilance hypothesis generation from 15 public drug safety databases. | Local · stdio |
| Icf MCPWHO ICF codes: lookup, search, hierarchy, qualifiers, and 11 scored clinical assessment instruments. | Remote · HTTPLive check: ✓ handshake |
| IdkRxReport pharmacy stock, and post a pharmacy's verified status, from your AI assistant. | Remote · HTTPLive check: sign-in required |