HK Racing AI
REMOTE · HKRACING.LIVE
Hong Kong horse racing: race cards, AI win chances, odds, results, form and stats.
Available components
Last scanned (17 hours ago)
Scores higher than 92% of remote servers
Reachable. Last reached 7 Nov 2026.
Category Finance and Payments
How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →
Endpoint Security80
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- No authorisation is required to call this server. Nothing on it is marked destructive, but we can't show that an anonymous caller can only read: full credit needs the server to list at least one tool and every tool to be verifiably read-only. We use a best-effort check of tool names and descriptions to tell read-only tools from tools that change things, so some genuinely read-only tools may not get full credit. Names that start with a read verb (get, list, read, search and similar) and accurate readOnlyHint annotations help. Meet that to earn full credit, or require authorisation. See how to fix → View diagnostics → Partial
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability72
- AI-judged instruction clarity (good).Pass
- Context-footprint check failed: tool/resource definitions use about 1284 tokens (~128/item across 10 items; 10 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management100
- No destabilizing schema changes in the last 30 days.Pass
Tool Coverage92
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 75% of tool parameters carry a description.Partial
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 10 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 11 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a current MCP spec version (2026-07-28).Pass
Checks we ran (13)
- TLS certificate
- Authorization
- HTTPS
- HSTS header
- DNSSEC
- Transport
- Schema quality
- Stability
- Tool coverage
- Injection markers
- Destructive annotations
- Judged manipulation
- MCP protocol
Does not apply to this hosted endpoint (2)
- Supply Chain SecurityScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
- Provenance & TransparencyScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
The score does not measure everything. What the score does not measure →
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 6 Nov 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 31 Oct 26 0
- Stability: 0.97 → pass security
- 30 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 93 to 97. That category is still filling its 30-day observation window: 28 days of observed history at the previous scan, 29 at this one. The score rises as the window fills, whether or not the server changes.
- 27 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 83 to 87. That category is still filling its 30-day observation window: 25 days of observed history at the previous scan, 26 at this one. The score rises as the window fills, whether or not the server changes.
- 25 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 77 to 80. That category is still filling its 30-day observation window: 23 days of observed history at the previous scan, 24 at this one. The score rises as the window fills, whether or not the server changes.
- 23 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 70 to 73. That category is still filling its 30-day observation window: 21 days of observed history at the previous scan, 22 at this one. The score rises as the window fills, whether or not the server changes.
- 21 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 63 to 67. That category is still filling its 30-day observation window: 19 days of observed history at the previous scan, 20 at this one. The score rises as the window fills, whether or not the server changes.
- 19 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 57 to 60. That category is still filling its 30-day observation window: 17 days of observed history at the previous scan, 18 at this one. The score rises as the window fills, whether or not the server changes.
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 7 Nov 2026 · Probed https://hkracing.live/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=hkracing.live | CN=YE2,O=Let's Encrypt,C=US | 12 Oct 2026 | 10 Jan 2027 | ECDSA 256 | ECDSA-SHA384 | 6b0682b2f993359a6312f15f252a6c315e1 |
| SANs: *.hkracing.live, hkracing.live | ||||||
| CN=YE2,O=Let's Encrypt,C=US (CA) | CN=Root YE,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | ECDSA 384 | ECDSA-SHA384 | 4df3b15dd6c0784c507cd37b58e6f115 |
| CN=Root YE,O=ISRG,C=US (CA) | CN=ISRG Root X2,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | ECDSA-SHA384 | 872165fc34b6e5fba8add5b3705fb53a |
| CN=ISRG Root X2,O=Internet Security Research Group,C=US (CA) | CN=ISRG Root X1,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | SHA256-RSA | 6c8f1dc727c7117f7baf853ac980f9cd |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of hkracing.live. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | Trust anchor | 20326, 38696 | 8, 8 | Verified |
| live. | DS published | 4724 | 8 | Verified |
| hkracing.live. | No DS | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 200 |
| Header | Value |
|---|---|
| strict-transport-security | max-age=63072000; includeSubDomains; preload |
| x-content-type-options | nosniff |
| x-frame-options | DENY |
| referrer-policy | strict-origin-when-cross-origin |
| permissions-policy | camera=(), microphone=(), geolocation=() |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://hkracing.live/mcp | Verified | 200 | |
| http (plaintext) | http://hkracing.live/mcp | HTTPS enforced | 308 | https://hkracing.live/mcp |
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
get_draw_stats Draw (barrier) statistics ~160
Win and place rates by draw for a Hong Kong course: venue, distance and rail position (A, A+3, B, B+2, C, C+3, or AWT for Sha Tin all-weather).
| Name | Type | Req | Description |
|---|---|---|---|
| course | string | yes | Rail/course, e.g. A, B+2, C+3, AWT |
| distance_m | integer | yes | – |
| lang | string | – | Output language: en (English) or zh (Traditional Chinese). Horse and people names are given in both where available. |
| venue | string | yes | Sha Tin or Happy Valley: 'sha-tin' / 'ST' / '沙田' or 'happy-valley' / 'HV' / '跑馬地' |
No output schema declared.
No examples provided.
get_horse Horse profile and form ~126
A Hong Kong racehorse: trainer, rating, age, pedigree, career record, the last 10 runs (class, distance, draw, jockey, finishing position, odds, AI rank) and a written form summary. Accepts a Chinese or English name, brand number or id.
| Name | Type | Req | Description |
|---|---|---|---|
| horse | string | yes | Horse name (中文 or English), brand number like H464, or id like h464-robot-knight |
| lang | string | – | Output language: en (English) or zh (Traditional Chinese). Horse and people names are given in both where available. |
No output schema declared.
No examples provided.
get_meeting Race meeting overview ~157
Hong Kong horse racing meeting at Sha Tin or Happy Valley: every race with post time, class, distance, course, status, the AI top pick and, after the race, the first three. Without a date it returns the next upcoming meeting (or the latest one if none is scheduled).
| Name | Type | Req | Description |
|---|---|---|---|
| date | string | – | Meeting date, YYYY-MM-DD (Hong Kong time) |
| lang | string | – | Output language: en (English) or zh (Traditional Chinese). Horse and people names are given in both where available. |
| venue | string | – | Sha Tin or Happy Valley: 'sha-tin' / 'ST' / '沙田' or 'happy-valley' / 'HV' / '跑馬地' |
No output schema declared.
No examples provided.
get_partnership Jockey–trainer partnership ~80
How a Hong Kong jockey and trainer have done together over the last two seasons: rides, wins, placings and recent rides together.
| Name | Type | Req | Description |
|---|---|---|---|
| jockey | string | yes | – |
| lang | string | – | Output language: en (English) or zh (Traditional Chinese). Horse and people names are given in both where available. |
| trainer | string | yes | – |
No output schema declared.
No examples provided.
get_person Jockey or trainer statistics ~106
Season statistics for a Hong Kong jockey or trainer: rides, wins/seconds/thirds, rank, win rate, most frequent partners and recent rides. Accepts a Chinese or English name or id.
| Name | Type | Req | Description |
|---|---|---|---|
| lang | string | – | Output language: en (English) or zh (Traditional Chinese). Horse and people names are given in both where available. |
| name | string | yes | Name (中文 or English) or id like z-purton |
| role | string | yes | – |
No output schema declared.
No examples provided.
get_race Race card and result ~160
One Hong Kong race: full field with draw, jockey, trainer, weight, rating, latest win odds, the AI model's win probability and rank for every runner; after the race also finishing positions, margins and HKJC dividends.
| Name | Type | Req | Description |
|---|---|---|---|
| date | string | yes | Meeting date, YYYY-MM-DD (Hong Kong time) |
| lang | string | – | Output language: en (English) or zh (Traditional Chinese). Horse and people names are given in both where available. |
| race_no | integer | yes | Race number, 1–14 |
| venue | string | yes | Sha Tin or Happy Valley: 'sha-tin' / 'ST' / '沙田' or 'happy-valley' / 'HV' / '跑馬地' |
No output schema declared.
No examples provided.
get_standings Jockey or trainer standings ~88
This season's Hong Kong jockey or trainer championship table: rank, rides, 1st/2nd/3rd, win rate and the last 30 days.
| Name | Type | Req | Description |
|---|---|---|---|
| lang | string | – | Output language: en (English) or zh (Traditional Chinese). Horse and people names are given in both where available. |
| role | string | yes | – |
| top | integer | – | – |
No output schema declared.
No examples provided.
get_tips AI tips for a meeting ~141
AI top four for every race at a Hong Kong meeting, ranked by the model's win probability, with how the AI top pick was settled once the race is run. Without a date: the next upcoming meeting.
| Name | Type | Req | Description |
|---|---|---|---|
| date | string | – | Meeting date, YYYY-MM-DD (Hong Kong time) |
| lang | string | – | Output language: en (English) or zh (Traditional Chinese). Horse and people names are given in both where available. |
| venue | string | – | Sha Tin or Happy Valley: 'sha-tin' / 'ST' / '沙田' or 'happy-valley' / 'HV' / '跑馬地' |
No output schema declared.
No examples provided.
get_track_record AI public track record ~79
The public, pre-race-sealed record of every AI top pick ($10 win + $10 place at HKJC dividends), compared with backing the favourite in the same races. Losses included.
| Name | Type | Req | Description |
|---|---|---|---|
| lang | string | – | Output language: en (English) or zh (Traditional Chinese). Horse and people names are given in both where available. |
No output schema declared.
No examples provided.
search Find a horse, jockey or trainer ~82
Search Hong Kong racehorses, jockeys and trainers by Chinese name, English name or brand number (e.g. H464). Returns ids usable with get_horse / get_person.
| Name | Type | Req | Description |
|---|---|---|---|
| lang | string | – | Output language: en (English) or zh (Traditional Chinese). Horse and people names are given in both where available. |
| query | string | yes | – |
No output schema declared.
No examples provided.
How do I install the HK Racing AI MCP server?
HK Racing AI is a hosted endpoint at https://hkracing.live/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
remote · hkracing.live
claude mcp add --transport http live-hkracing-mcp 'https://hkracing.live/mcp'
What is the HK Racing AI MCP server?
HK Racing AI is an MCP server listed in the public MCP registry as live.hkracing/mcp. Hong Kong horse racing: race cards, AI win chances, odds, results, form and stats. This page covers its hosted endpoint (https://hkracing.live/mcp).
Is the HK Racing AI MCP server safe to use?
HK Racing AI scores 86 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the HK Racing AI MCP server expose?
HK Racing AI exposes 10 tools: get_meeting, get_race, get_tips, get_track_record, search, and 5 more. Their descriptions and schemas cost roughly 1,179 tokens of context every time the server is loaded.
Does the HK Racing AI MCP server require authentication?
No. We connected to HK Racing AI without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the HK Racing AI MCP server still maintained?
HK Racing AI is still listed as active in the MCP registry. We last reached this channel on 7 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.
What did VerifyMCP test on the HK Racing AI MCP server?
VerifyMCP ran 13 checks on HK Racing AI, covering TLS certificate, Authorization, HTTPS, HSTS header and 9 more. Supply Chain Security and Provenance & Transparency do not apply to a hosted endpoint, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.