hla-verify bronze
api.hlaverify.com
“Nomenclature and reference-release validation for HLA: allele names, typing-report consistency and match arithmetic, checked against a pinned IPD-IMGT/HLA release. No LLM inside: every verdict is a table lookup. This is not a diagnostic aid and not clinical decision support; it does not interpret a case or recommend a donor. What to send: allele names, typing strings, GL strings and report text about HLA typing. What never to send: patient identifiers of any kind, including names, medical record numbers, dates of birth, accession or case identifiers, and other patient details. The service does not need them and does not store request bodies; removing them before sending is the caller's responsibility. Call verify_text on any AI-generated or transcribed content that mentions HLA alleles before presenting it; call normalize_allele or allele_info before asserting an allele name is valid or current; call match_score instead of computing a donor-recipient match count yourself. LLMs (including you) fabricate allele
https://api.hlaverify.com/mcp its cardwe checked this the operator says this
Verified by agenttru.st
Everything here is a check agenttru.st performed itself. Assurance, protocol, hosting and freshness are in the card above and are not repeated.
- Certificate
-
Issued by Google Trust Services
domain-validated
Valid until 6 Feb 2027 as of our check on 12 Nov 2026. A wildcard certificate: its other hosts are invisible here, because CT logs the wildcard, not them.Control of the hostname was checked; nothing about who operates it.Key ECDSA P-256, signed ECDSA-SHA256, issued via WE1 under GTS Root R4 — classical, as every publicly trusted certificate is today.
Names on this certificate (3)
hlaverify.com,api.hlaverify.com,*.api.hlaverify.com. - Connection
- TLS 1.3 · X25519MLKEM768 — post-quantum hybrid key exchange, agreed with our checker on 12 Nov 2026. What this means
- DANE / TLSA
- Not verified (TLSA query returned RCodeNameError)
- Discovery
-
Well-known document
This host also publishes an ARD catalog (
/.well-known/ai-catalog.json) declaring 1 resource. The catalog's entries are the publisher's claims, not something agenttru.st verified. - First seen
- 22 Oct 2026
View verification details
- Assurance
- bronze Bronze — agent card fetched over HTTPS with a valid certificate
- Protocols
- MCP verified by handshake or card fetch, not merely advertised
- Hosted in
-
? Unknown
·
Cloudflare, Inc.
(AS13335)
The address did not geolocate — usually anycast hosting, where one address answers from many places at once.
- Last checked
- 4d ago
What this agent says it can do
Declared in the agent's own card. agenttru.st has not tested whether it completes any of these tasks — the operator of api.hlaverify.com controls every word below.
This card declares no skills. That is not a fault — the field is optional, and an agent can be perfectly functional without describing itself.
What kind of listing
- No skills declared: Its card declares no skills, or, for an MCP server, listed no tools.
Checked by agenttru.st against this listing's hostname and card — facts about a name or an address, not about what the agent does. How kinds are decided.
What its catalog declares
From the ARD catalog this host publishes at
/.well-known/ai-catalog.json. The operator controls every entry; agenttru.st
verified that the catalog exists and parses, and nothing about what the entries say.
urn:air:hlaverify.com:mcp:hla-verify
https://api.hlaverify.com/mcp/server-cardTechnical agent card
Copied from the agent's card. The operator controls these values; agenttru.st has not verified them.
- Protocol
- mcp
- Version
- 1.0.1
View all card details
- Capabilities
- tools
- Agent card
- https://api.hlaverify.com/mcp
Operate this agent and would rather not be listed? Request removal.