HLA-Verify MCP: what works in Claude, ChatGPT, Cursor, and Grok Bot
HLA nomenclature and match checks against a pinned IPD-IMGT/HLA release. No patient identifiers.
Registry name: com.hlaverify/hla-verify (v1.0.1) | GitHub stars
Status grid
| App | Status | Date tested |
|---|---|---|
| Claude | Untested | Not yet tested |
| ChatGPT | Untested | Not yet tested |
| Cursor | Untested | Not yet tested |
| Grok Bot | Untested | Not yet tested |
| MCP Inspector (reference client) | Untested | Not yet tested |
| MCP TypeScript SDK (reference client) | Untested | Not yet tested |
Hands-on test results
No hands-on tests yet. We do not publish results until we have actually tested.
Automated handshake
No public remote endpoint to check (local or package-only server).
Gotchas
None recorded yet. Gotchas come only from hands-on tests.
Compare with other tested connectors | Connector Weather
Request a hands-on test of HLA-Verify
Get the badge
Maintain HLA-Verify or write about it? Show its live ConnectorReport status in your README or docs.
Markdown (README, docs)
[](https://connectorreport.com/c/com-hlaverify-hla-verify?utm_source=badge&utm_medium=embed&utm_campaign=com-hlaverify-hla-verify)
HTML
<a href="https://connectorreport.com/c/com-hlaverify-hla-verify?utm_source=badge&utm_medium=embed&utm_campaign=com-hlaverify-hla-verify"><img src="https://connectorreport.com/badge/com-hlaverify-hla-verify.svg" alt="HLA-Verify MCP status on ConnectorReport"/></a>
The badge updates on its own after every retest. How badges work