GitHub Hot Board
REMOTE · GIT.VAIOX.XYZ
GitHub hot-repo leaderboards: snapshots, movers, rank history. Read-only JSON, hourly batches.
Available components
Last scanned (8 hours ago)
Scores higher than 61% of remote servers
Unreachable for 1 day in a row. Last reached 4 Nov 2026.
Category News and Social
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 Security57
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation not yet verified: we couldn't confirm whether this endpoint requires it. View diagnostics → Unverified
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- HSTS not yet verified: we couldn't read the response headers to check for it. View diagnostics → Unverified
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability0
- Transport check failed: declared streamable-http, but we couldn't connect to verify it. See how to fix → View diagnostics → Fail
Schema Quality & AI Usability0
- Schema not yet verified: we couldn't read the endpoint's schema, or could read only part of its tool list.Unverified
Stability & Change Management0
- Stability not yet verified: not enough scan history yet (needs a 30-day window).Unverified
Tool Coverage0
- Tool coverage not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.Unverified
Tool Safety0
- Tool safety not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.Unverified
Capabilities0
- Capabilities not yet verified: we couldn't read the endpoint's capabilities.Unverified
Unverified: 5 categories
Categories scored 0 because we could not verify them: authentication we do not have, an unreachable endpoint, or not enough scan history. We only credit what we can confirm.
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.
- 5 Nov 26 0
- Endpoint reachability: reachable → unreachable ▼ security
- Stability: 0.37 → unverified ▼ security
- HSTS header: fail → unverified ▼ security
- Authorization: partial → unverified ▼ security
- Tool safety: pass → unverified ▼ security
- Transport: pass → fail ▼ security
- Capabilities: pass → unverified ▼ functional
- Tool coverage: 100 → unverified ▼ functional
- First check of Schema quality: unverified functional
- 4 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 33 to 37. That category is still filling its 30-day observation window: 10 days of observed history at the previous scan, 11 at this one. The score rises as the window fills, whether or not the server changes.
- 1 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 23 to 27. That category is still filling its 30-day observation window: 7 days of observed history at the previous scan, 8 at this one. The score rises as the window fills, whether or not the server changes.
- 30 Oct 26 −2
- HSTS header: pass → fail ▼ security
- 29 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 13 to 17. That category is still filling its 30-day observation window: 4 days of observed history at the previous scan, 5 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 7 to 10. That category is still filling its 30-day observation window: 2 days of observed history at the previous scan, 3 at this one. The score rises as the window fills, whether or not the server changes.
- 26 Oct 26 0
- The server rewrote its instructions, which are the text every model session reads security
- Tool “get_board” rewrote its description, which is the text the model reads security
- Tool “get_board_movers” rewrote its description, which is the text the model reads security
- Tool “get_repo_history” rewrote its description, which is the text the model reads security
- 25 Oct 26 +1
- Stability: unverified → 0.03 ▲ functional
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 5 Nov 2026 · Probed https://git.vaiox.xyz/api/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=git.vaiox.xyz | CN=YE1,O=Let's Encrypt,C=US | 21 Oct 2026 | 19 Jan 2027 | ECDSA 256 | ECDSA-SHA384 | 54d83541848f0f13d676a09d21ad4858ad5 |
| SANs: git.vaiox.xyz | ||||||
| CN=YE1,O=Let's Encrypt,C=US (CA) | CN=Root YE,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | ECDSA 384 | ECDSA-SHA384 | 5ddd70dd31f801c85c186a7a04b80afe |
| 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 git.vaiox.xyz. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| xyz. | present | 3599, 18130 | 8, 8 | Verified |
| vaiox.xyz. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication Inconclusive
We could not reach the endpoint well enough to judge its authorisation posture.
| Result | Inconclusive |
|---|
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://git.vaiox.xyz/api/mcp | Unreachable | ||
| http (plaintext) | http://git.vaiox.xyz/api/mcp | HTTPS enforced | 301 | https://git.vaiox.xyz/api/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_board Get board snapshot ~89
Top-N rows of one leaderboard (rank, stars, forks, issues, language, description). Refreshes every ~6 hours; generatedAt is the batch stamp (fetch once per sync cycle).
| Name | Type | Req | Description |
|---|---|---|---|
| language | string | – | optional source-language facet; supported only for overall / weekly / monthly |
| limit | integer | – | – |
| slug | string | yes | one of the 10 board slugs |
| Name | Type | Req | Description |
|---|---|---|---|
| batchSize | integer | yes | – |
| degraded | boolean | yes | true = the official Trending scrape failed and a Search-based fallback methodology was served; cite with care (HTML pages show the same warning) |
| generatedAt | string | yes | – |
| items | array | yes | – |
| language | string|null | yes | – |
| slug | string | yes | – |
| source | string | yes | github-search | github-trending | github-search-fallback — which upstream produced this batch |
No examples provided.
get_board_movers Get 24h movers ~62
Repositories that genuinely moved rank on a board within the last 24 hours, from our own snapshot series (the same data as the on-site movers strip). Positive climb = went up.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | – |
| slug | string | yes | – |
| Name | Type | Req | Description |
|---|---|---|---|
| count | integer | yes | – |
| movers | array | yes | – |
| slug | string | yes | – |
| window | string | yes | – |
No examples provided.
get_repo Get repository record ~105
Library record for one repository: stars, forks, description in up to 16 UI languages (keys are locale codes), current overall-board rank if listed, pushedAt, and asOf freshness stamps. Served from our own dataset (no live GitHub API call); repos outside the library return not-in-library.
| Name | Type | Req | Description |
|---|---|---|---|
| full | string | yes | owner/name, e.g. vercel/next.js |
| lg | string | – | optional: also return descText in this UI language |
| Name | Type | Req | Description |
|---|---|---|---|
| asOf | string | yes | – |
| desc | object | – | – |
| descText | string | – | – |
| forks | integer | – | – |
| fullName | string | yes | – |
| overallRank | integer | – | – |
| pushedAt | string | – | – |
| source | string | yes | – |
| stars | integer | – | – |
No examples provided.
get_repo_history Get rank history ~83
Time series of one repository on one board (default overall): rank + star points at our sync cadence (~6h) from our own snapshot series — denser than the daily archives others publish. Empty result means the repo was not tracked in the window.
| Name | Type | Req | Description |
|---|---|---|---|
| board | string | – | – |
| days | integer | – | – |
| full | string | yes | owner/name |
| Name | Type | Req | Description |
|---|---|---|---|
| board | string | yes | – |
| cadence | string | yes | – |
| days | integer | yes | – |
| fullName | string | yes | – |
| pointCount | integer | yes | – |
| points | array | yes | – |
No examples provided.
list_boards List boards ~34
The 10 leaderboards on GitHub Hot Board: what each ranks, its canonical page URL and its JSON API endpoint.
Input schema present but exposes no named parameters.
| Name | Type | Req | Description |
|---|---|---|---|
| boards | array | yes | – |
| site | string | yes | – |
No examples provided.
search_library Search the library ~69
Search repositories tracked by this site, by owner/name (exact wins) or by keyword over descriptions (16 languages). Library-only: repos never listed on a board are not here. No live GitHub calls.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | – |
| q | string | yes | owner/name fragment or keyword |
| Name | Type | Req | Description |
|---|---|---|---|
| count | integer | yes | – |
| query | string | yes | – |
| results | array | yes | – |
No examples provided.
How do I install the GitHub Hot Board MCP server?
GitHub Hot Board is a hosted endpoint at https://git.vaiox.xyz/api/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 · git.vaiox.xyz
claude mcp add --transport http jkwy01-github-hot-board 'https://git.vaiox.xyz/api/mcp'
What is the GitHub Hot Board MCP server?
GitHub Hot Board is an MCP server listed in the public MCP registry as io.github.JKWY01/github-hot-board. GitHub hot-repo leaderboards: snapshots, movers, rank history. Read-only JSON, hourly batches. This page covers its hosted endpoint (https://git.vaiox.xyz/api/mcp).
Is the GitHub Hot Board MCP server safe to use?
GitHub Hot Board scores 74 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 GitHub Hot Board MCP server expose?
GitHub Hot Board exposes 6 tools: list_boards, get_board, get_board_movers, get_repo, search_library, get_repo_history. Their descriptions and schemas cost roughly 442 tokens of context every time the server is loaded.
Does the GitHub Hot Board MCP server require authentication?
Its publisher declares no required credentials for GitHub Hot Board. We have not been able to confirm that against the live endpoint, and a server can require authorisation without declaring it here.
Is the GitHub Hot Board MCP server still maintained?
GitHub Hot Board is still listed in the MCP registry, though our most recent checks did not reach this channel. We last reached this channel on 4 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.