HLA-Verify

warnings

api.hlaverify.com

HLA nomenclature and match checks against a pinned IPD-IMGT/HLA release. No patient identifiers.

https://api.hlaverify.com/mcpWebsiteOAuthMCP 2025-11-25v1.0.1last checked 16 Sep 2026spoke MCP on 1 of 1 check (30 days)initialize in 66 ms

Will my client connect?

Decided from what the probe found at the endpoint, and from what each client's own documentation says it can complete. Every row carries the day that documentation was read.

✓Claude CodeConnects

The authorization server advertises RFC 7591 registration, so Claude Code can register itself and sign you in through the browser.

claude mcp add --transport http hla-verify https://api.hlaverify.com/mcp

Claude Code docs · read on 2026-08-30

✓Claude (claude.ai & Desktop)Connects

The authorization server advertises RFC 7591 registration, so Claude (claude.ai & Desktop) can register itself and sign you in through the browser.

Settings → Connectors → Add custom connector, then paste https://api.hlaverify.com/mcp.

Claude (claude.ai & Desktop) docs · read on 2026-08-30

✓ChatGPTConnects

The authorization server advertises RFC 7591 registration, so ChatGPT can register itself and sign you in through the browser.

Settings → Apps → Advanced settings → Developer mode, then create a connector pointing at https://api.hlaverify.com/mcp.

ChatGPT docs · read on 2026-08-30

✓CursorConnects

The authorization server advertises RFC 7591 registration, so Cursor can register itself and sign you in through the browser.

{
  "mcpServers": {
    "hla-verify": {
      "url": "https://api.hlaverify.com/mcp"
    }
  }
}

Cursor docs · read on 2026-08-30

✓VS Code (Copilot)Connects

The authorization server advertises RFC 7591 registration, so VS Code (Copilot) can register itself and sign you in through the browser.

{
  "servers": {
    "hla-verify": {
      "type": "http",
      "url": "https://api.hlaverify.com/mcp"
    }
  }
}

VS Code (Copilot) docs · read on 2026-08-30

How to authenticate

Checked against the endpoint by our probe on 16 Sep 2026. These are the capabilities the server advertises, not a prediction about any particular client.

Scheme	OAuth
Issuer	https://api.hlaverify.com
Dynamic client registration	✓Advertised (RFC 7591)
Client ID Metadata Document	✓Supported A client identifies itself by a URL to its own metadata, so no registration step is required.
PKCE	✓S256
Grant types	authorization_code, refresh_token
Scopes	mcp
Protected-resource metadata	✓Published (RFC 9728)
Anonymous access	Handshake succeeds; 9 tools listable
Credentials demanded in prose	✕beta_signup These tools are listed anonymously and their own descriptions ask for an account or key, but no challenge is issued — so a client has nothing to act on and the refusal arrives as a tool error.
Documentation	https://api.hlaverify.com/docs

What the probe found

warningTools needing credentials are listed without a challenge

1 of the 9 tools listed anonymously say in their own descriptions that they need an account or a key (beta_signup), but the endpoint issued no WWW-Authenticate challenge. The requirement is stated only in prose, so a call reaches the tool and comes back as a tool error instead of an authorization step.

9 tools usable without signing in

The server exposes a public surface before authorization: verify_text, normalize_allele, allele_info, match_score, check_typing, donor_compat, validate_gl_string, beta_signup, about.

Tools

aboutallele_infobeta_signupcheck_typingdonor_compatmatch_scorenormalize_allelevalidate_gl_stringverify_text

Contract history

16 Sep 2026v1.0.1first recorded contract

Watch this server

Save its public contract as a baseline and manage breaking-change email alerts.

Set up a watch

Own this server?

Status badge

Status for a README, from the last probe — cached an hour, so up to seven hours behind the endpoint. Links back to this page.

[![MCP status](https://mcpi.app/servers/hla-verify/badge.svg)](https://mcpi.app/servers/hla-verify)