# GitHub Hot Board (remote · git.vaiox.xyz)

GitHub hot-repo leaderboards: snapshots, movers, rank history. Read-only JSON, hourly batches.

- Trust score: 74/100 (medium)
- Change this week: 0
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-05

## Components

- remote · `git.vaiox.xyz`: 74/100 (this document), [markdown](https://verifymcp.io/servers/jkwy01-github-hot-board/api-mcp.md), [page](https://verifymcp.io/servers/jkwy01-github-hot-board/api-mcp)

## Channel facts

- Endpoint: `https://git.vaiox.xyz/api/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `2.1.0`

## Trust breakdown

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. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-11-05.

- **Endpoint Security**: 57/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - Authorisation not yet verified: we couldn't confirm whether this endpoint requires it.
  - HTTPS is enforced; there's no plaintext access path.
  - HSTS not yet verified: we couldn't read the response headers to check for it.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
- **Transport & Reachability**: 0/100
  - Transport check failed: declared streamable-http, but we couldn't connect to verify it.
- **Schema Quality & AI Usability**: 0/100
  - Schema not yet verified: we couldn't read the endpoint's schema, or could read only part of its tool list.
- **Stability & Change Management**: 0/100
  - Stability not yet verified: not enough scan history yet (needs a 30-day window).
- **Tool Coverage**: 0/100
  - Tool coverage not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.
- **Tool Safety**: 0/100
  - Tool safety not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.
- **Capabilities**: 0/100
  - Capabilities not yet verified: we couldn't read the endpoint's capabilities.

**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.

## Install

### 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.

### Claude

```bash
claude mcp add --transport http jkwy01-github-hot-board 'https://git.vaiox.xyz/api/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "jkwy01-github-hot-board": {
      "url": "https://git.vaiox.xyz/api/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "jkwy01-github-hot-board": {
      "type": "http",
      "url": "https://git.vaiox.xyz/api/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.jkwy01-github-hot-board]
url = "https://git.vaiox.xyz/api/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "jkwy01-github-hot-board": {
      "type": "remote",
      "url": "https://git.vaiox.xyz/api/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add jkwy01-github-hot-board --url 'https://git.vaiox.xyz/api/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  jkwy01-github-hot-board:
    url: "https://git.vaiox.xyz/api/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "jkwy01-github-hot-board": {
      "Transport": "http",
      "Url": "https://git.vaiox.xyz/api/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add jkwy01-github-hot-board -t streamable-http -u 'https://git.vaiox.xyz/api/mcp'
```

### Other

```json
{
  "mcpServers": {
    "jkwy01-github-hot-board": {
      "type": "http",
      "url": "https://git.vaiox.xyz/api/mcp"
    }
  }
}
```

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-11-05 (score 74, 0)

- [security regression] Endpoint reachability: reachable → unreachable
- [security regression] Stability: 0.37 → unverified
- [security regression] HSTS header: fail → unverified
- [security regression] Authorization: partial → unverified
- [security regression] Tool safety: pass → unverified
- [security regression] Transport: pass → fail
- [functional regression] Capabilities: pass → unverified
- [functional regression] Tool coverage: 100 → unverified
- [functional] First check of Schema quality: unverified

### 2026-11-04 (score 74, +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.

### 2026-11-01 (score 73, +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.

### 2026-10-30 (score 72, −2)

- [security regression] HSTS header: pass → fail

### 2026-10-29 (score 74, +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.

### 2026-10-27 (score 73, +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.

### 2026-10-26 (score 72, 0)

- [security] 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

### 2026-10-25 (score 72, +1)

- [functional improvement] Stability: unverified → 0.03

## MCP tools (6)

### `list_boards` (~34 tokens)

List boards

The 10 leaderboards on GitHub Hot Board: what each ranks, its canonical page URL and its JSON API endpoint.

Output parameters:

- `boards` (array)
- `site` (string)

### `get_board` (~89 tokens)

Get board snapshot

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).

Input parameters:

- `language` (string): optional source-language facet; supported only for overall / weekly / monthly
- `limit` (integer)
- `slug` (string, required): one of the 10 board slugs

Output parameters:

- `batchSize` (integer)
- `degraded` (boolean): 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)
- `items` (array)
- `language` (string|null)
- `slug` (string)
- `source` (string): github-search | github-trending | github-search-fallback — which upstream produced this batch

### `get_board_movers` (~62 tokens)

Get 24h movers

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.

Input parameters:

- `limit` (integer)
- `slug` (string, required)

Output parameters:

- `count` (integer)
- `movers` (array)
- `slug` (string)
- `window` (string)

### `get_repo` (~105 tokens)

Get repository record

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.

Input parameters:

- `full` (string, required): owner/name, e.g. vercel/next.js
- `lg` (string): optional: also return descText in this UI language

Output parameters:

- `asOf` (string)
- `desc` (object)
- `descText` (string)
- `forks` (integer)
- `fullName` (string)
- `overallRank` (integer)
- `pushedAt` (string)
- `source` (string)
- `stars` (integer)

### `search_library` (~69 tokens)

Search the library

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.

Input parameters:

- `limit` (integer)
- `q` (string, required): owner/name fragment or keyword

Output parameters:

- `count` (integer)
- `query` (string)
- `results` (array)

### `get_repo_history` (~83 tokens)

Get rank history

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.

Input parameters:

- `board` (string)
- `days` (integer)
- `full` (string, required): owner/name

Output parameters:

- `board` (string)
- `cadence` (string)
- `days` (integer)
- `fullName` (string)
- `pointCount` (integer)
- `points` (array)

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/jkwy01-github-hot-board/api-mcp#diagnostics

## Score history

- 2026-11-05: 74
- 2026-11-04: 74
- 2026-11-03: 73
- 2026-11-02: 73
- 2026-11-01: 73
- 2026-10-31: 72
- 2026-10-30: 72
- 2026-10-29: 74
- 2026-10-28: 73
- 2026-10-27: 73
- 2026-10-26: 72
- 2026-10-25: 72
- 2026-10-24: 71

## Common questions

### 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.

## Links

- Remote endpoint: https://git.vaiox.xyz/api/mcp
- Repository: https://github.com/JKWY01/github-hot-board
- Changelog RSS feed: https://verifymcp.io/servers/jkwy01-github-hot-board/api-mcp.xml
- Changelog JSON feed: https://verifymcp.io/servers/jkwy01-github-hot-board/api-mcp.json
- HTML version of this page: https://verifymcp.io/servers/jkwy01-github-hot-board/api-mcp