MCP server report

HLA-Verify MCP server

com.hlaverify/hla-verify

We checked this server on 2 November 2026 with McpStamp Check engine 1.2.0. It scored 94 of 100 (grade A), higher than 70.5% of the 33,003 registry servers that responded over HTTPS that day. Ready for Gemini and MCP Registry. Not ready for Claude and ChatGPT.

Score: 94A
Sign-in: OAuth
Tools listed: 15
Protocol version: 2025-11-25

Stores

Store readiness

Store	Status	Reason
Claude Connectors Directory	Not ready	Blocked by Human-readable title on every tool.
ChatGPT app directory	Not ready	Blocked by Explicit readOnlyHint, destructiveHint and openWorldHint (ChatGPT) and Human-readable title on every tool.
Gemini Connected Apps	Ready	No blocking check failed.
Official MCP Registry	Ready	No blocking check failed.

MCP Registry ready means a valid public remote for the registry, not that the server is listed in a store.

Fixes

2 checks to fix

Fails
Explicit readOnlyHint, destructiveHint and openWorldHint (ChatGPT)
tool_open_world

Blocks ChatGPT.

Measured 15/15 tools miss an explicit hint: verify_text, normalize_allele, allele_info, match_score, check_typing and 10 more

Set readOnlyHint, destructiveHint and openWorldHint to explicit true/false on every tool (OpenAI app review requires all three).
Fails
Human-readable title on every tool
tool_titles

Blocks Claude and ChatGPT.

Measured 15/15 without title: verify_text, normalize_allele, allele_info, match_score, check_typing and 10 more

Add a short human-readable "title" to every tool (shown in store UIs and consent screens).

24 checks passed, 1 did not run

Passed. Served over HTTPS, initialize over Streamable HTTP, Supported protocol version negotiated, JSON or SSE response Content-Type, JSON-RPC error for unknown method, GET answers SSE or 405, initialize latency, serverInfo name and version, Server instructions, tools capability declared, Sign-in method the store supports (OAuth or none), Protected resource metadata (RFC 9728), Resource metadata "resource" equals the server URL, Authorization server metadata (RFC 8414 / OIDC), First metadata URL Gemini tries answers 200 with the required fields, issuer equals the authorization_servers entry; token_endpoint_auth_methods_supported (ChatGPT), PKCE S256 advertised, Client registration (DCR or Client ID Metadata Documents), refresh_token grant advertised, tools/list returns tools, inputSchema is an object schema, Tool names are valid and portable, readOnlyHint or destructiveHint on every tool, Tool descriptions.

Not run. 401 carries WWW-Authenticate resource_metadata. These need an OAuth sign-in flow the check could not reach.

Run a fresh check

This page is the 2 November 2026 snapshot. If you maintain this server and have shipped fixes since then, re-check it. The live check and the badge show the current result, and the next snapshot will pick up the change.

Re-check now

Badge

README badge

The badge shows the latest score for this URL and links to this report.

Markdown

[![McpStamp score](https://www.mcpstamp.com/badge?url=https%3A%2F%2Fapi.hlaverify.com%2Fmcp)](https://www.mcpstamp.com/r/com-hlaverify-hla-verify/)

HTML

<a href="https://www.mcpstamp.com/r/com-hlaverify-hla-verify/"><img src="https://www.mcpstamp.com/badge?url=https%3A%2F%2Fapi.hlaverify.com%2Fmcp" alt="McpStamp score" height="20"></a>

Registry entry

About this server

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

Registry name: com.hlaverify/hla-verify
Remote URL: https://api.hlaverify.com/mcp
Version: 1.0.1
Source: github.com/jasonbrelsford/verifiable-science-envs
Website: hlaverify.com
Checked: 2 November 2026, engine 1.2.0, no credentials

The description above is the server's own text from the official MCP Registry. If a result looks wrong, run a fresh check and email support@zovo.one with the report link.

More grade A servers

All grade A servers · All server reports · State of MCP readiness, November 2026