About HLA-Verify
HLA nomenclature and match checks against a pinned IPD-IMGT/HLA release. No patient identifiers
Configuration
Remote servers need no local install. Pick your client, then copy the config or install in one click.
https://api.hlaverify.com/mcpclaude mcp add --transport http com-hlaverify-hla-verify https://api.hlaverify.com/mcp{"mcpServers":{"com-hlaverify-hla-verify":{"type":"http","url":"https://api.hlaverify.com/mcp"}}}Open in Cursor{"servers":{"com-hlaverify-hla-verify":{"type":"http","url":"https://api.hlaverify.com/mcp"}}}Open in VS Code{"mcpServers":{"com-hlaverify-hla-verify":{"type":"http","url":"https://api.hlaverify.com/mcp"}}}{"mcpServers":{"com-hlaverify-hla-verify":{"serverUrl":"https://api.hlaverify.com/mcp"}}}Run commands in a terminal; paste JSON into the client’s MCP config and restart. Servers that need sign-in will prompt on first connect.
https://api.hlaverify.com/mcpAuth requiredTools
15| Parameter | Type | Required | Description |
|---|---|---|---|
| text | string | Yes | 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. |
Details
The maintainer has not added details yet. Check the README in the repository.
Comments
New to MCP?
From what the protocol is to installing your first server, these answers cover most first questions.
An open protocol that defines how AI applications connect to external tools and data in a uniform way. Clients talk to the model; MCP servers provide tools, resources and prompt templates. They exchange standard messages, so one server can be reused by many clients.