Skip to content

GitHub Hot Board MCP server

io.github.JKWY01/github-hot-boardJKWY01streamable-httpv2.1.0Scanned

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

6 tools: 6 only read.

Tools: 0 delete, 0 irreversible, 0 write, 6 read.
  • Reads private data · 4
  • Reads text others write · 2
  • Can send data out · 0
  • No findings

The remote endpoint did not answer the last look. Remote posture

Anlyon alternative

Everything your agent needs in GitHub. None of the key.

Anlyon has its own GitHub integration. Every write runs under a limit you set and comes back with a receipt read from the provider.

Anlyon Radar does not run, proxy or govern this MCP server. A tool your own code calls directly is not routed through Anlyon and is not governed by it.

See the GitHub integration →

What the GitHub Hot Board MCP server can do

The GitHub Hot Board MCP server is published by the GitHub account JKWY01. It has 6 tools. Every one of them only reads: going by their definitions, none of them creates, changes, sends or deletes anything.

4 tools read private data (get_board_movers, get_repo, search_library and 1 more); 2 tools bring in text other people can write (list_boards and get_board).

None of the fixed checks matched anything in its tool definitions. That is not a safety guarantee.

Last scanned Oct 24, 2026, version 2.1.0.

Tools

Grouped by what each tool does, most consequential first. Open one for its reasons and full description; descriptions are the publisher's own words.

6 tools

Only reads 6Show 6 read-only tools
  • get_boardTop-N rows of one leaderboard (rank, stars, forks, issues, language, description).Reads text others writeNo findings

    Why it is in this group

    • The name "get_board" says "get": a word for reading.

    What it can reach

    • untrusted-inputThe description's first sentence says "issue": it reads issues, which other people can write.
    Description, as the server wrote it
    Top-N rows of one leaderboard (rank, stars, forks, issues, language, description). Refreshes in hourly batches; generatedAt is the batch stamp (fetch once per hour).

    Annotations the server declares

    • readOnlyHint: true
  • get_board_moversRepositories that genuinely moved rank on a board within the last 24 hours, from our own hourly snapshot series (the same data as the on-site movers strip).Reads private dataNo findings

    Why it is in this group

    • The name "get_board_movers" says "get": a word for reading.

    What it can reach

    • private-dataThe description's first sentence says "repository": it reads repositories.
    Description, as the server wrote it
    Repositories that genuinely moved rank on a board within the last 24 hours, from our own hourly snapshot series (the same data as the on-site movers strip). Positive climb = went up.

    Annotations the server declares

    • readOnlyHint: true
  • get_repoLibrary 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 st…Reads private dataNo findings

    Why it is in this group

    • The name "get_repo" says "get": a word for reading.

    What it can reach

    • private-dataThe name "get_repo" says "get" and "repo": it reads repositories.
    • private-dataThe description's first sentence says "repository": it reads repositories.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • readOnlyHint: true
  • get_repo_historyTime series of one repository on one board (default overall): hourly rank + star points from our own snapshot series.Reads private dataNo findings

    Why it is in this group

    • The name "get_repo_history" says "get": a word for reading.

    What it can reach

    • private-dataThe name "get_repo_history" says "get" and "repo": it reads repositories.
    • private-dataThe description's first sentence says "repository": it reads repositories.
    Description, as the server wrote it
    Time series of one repository on one board (default overall): hourly rank + star points from our own snapshot series. Our unique moat — this data exists on no other service. Empty result means the repo was not tracked in the window.

    Annotations the server declares

    • readOnlyHint: true
  • list_boardsThe 10 leaderboards on GitHub Hot Board: what each ranks, its canonical page URL and its JSON API endpoint.Reads text others writeNo findings

    Why it is in this group

    • The name "list_boards" says "list": a word for reading.

    What it can reach

    • untrusted-inputThe description's first sentence says "url": it reads web pages, which anyone can write.
    Description, as the server wrote it
    The 10 leaderboards on GitHub Hot Board: what each ranks, its canonical page URL and its JSON API endpoint.

    Annotations the server declares

    • readOnlyHint: true
  • search_librarySearch repositories tracked by this site, by owner/name (exact wins) or by keyword over descriptions (16 languages).Reads private dataNo findings

    Why it is in this group

    • The name "search_library" says "search": a word for reading.

    What it can reach

    • private-dataThe description's first sentence says "search" and "repository": it reads repositories.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • readOnlyHint: true

This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.

Exfil surface

Which tools read private data, which read text someone else can write, and which can send data out. One of each is a path a prompt injection can use.

No private-data, untrusted-input, outbound path in this server alone: no tool is tagged outbound.

Reads private data4
Reads files, mail, messages, databases, secrets, calendars or repositories.
Reads text others write2
Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
Can send data out0
Can carry data to people or systems: it sends, posts or publishes, or takes a recipient, channel or URL.

Other servers in the same agent add their own tools to these paths. Audit your whole setup to see them together.

Remote posture

What anyone on the internet sees at the remote endpoint: an anonymous initialize and tools/list, and the public OAuth metadata.

The remote endpoint did not answer the last look

Looked at Nov 15, 2026, 13:22 UTC, unchanged since Nov 8, 2026. No credentials were sent and no tool was called. What is looked at.

Reachable
no
HTTP status of an anonymous initialize
not observed
tools/list served without credentials
no
Tools that change things, listed without credentials
0
Protocol version
not observed
WWW-Authenticate on 401
not observed
resource_metadata in WWW-Authenticate
not observed
RFC 9728 protected resource metadata
not observed
Authorization servers
not observed
Legacy HTTP+SSE transport
no
Dynamic client registration
not observed
Client ID metadata documents
not observed

The probe stopped: The server redirected a POST to a different request.

Posture changes

  1. Nov 8, 2026
    • Reachable: yes to no
    • HTTP status of an anonymous initialize: 200 to none
    • tools/list served without credentials: yes to no
    • Protocol version: 2025-06-18 to none

Findings

Matches of fixed checks, with the text they matched.

No check matched anything in these tool definitions. That is not a safety guarantee.

History

Changes to its tool definitions and to its remote endpoint, newest first.

  1. PostureRemote posture changed. Reachable: yes -> no; HTTP status of an anonymous initialize: 200 -> none; tools/list served without credentials: yes -> no (and 1 more).View diff
    • Reachable: yes to no
    • HTTP status of an anonymous initialize: 200 to none
    • tools/list served without credentials: yes to no
    • Protocol version: 2025-06-18 to none

Install

Pinned to version 2.1.0. Values in angle brackets are yours to fill in.

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

Run in a terminal.

Claude Code permissions

Allow the reads, ask before a change or a way out, deny the deletes. Paste into .claude/settings.json.

.claude/settings.json
{
  "permissions": {
    "allow": [
      "mcp__github-hot-board__list_boards",
      "mcp__github-hot-board__get_board",
      "mcp__github-hot-board__get_board_movers",
      "mcp__github-hot-board__get_repo",
      "mcp__github-hot-board__search_library",
      "mcp__github-hot-board__get_repo_history"
    ],
    "ask": [],
    "deny": []
  }
}

Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. A read that can send data out (it takes a URL, say) asks first too. It assumes the server is installed as github-hot-board. Review it before you use it.

Capability tags behind 6 rules
  • mcp__github-hot-board__list_boards untrusted-input
  • mcp__github-hot-board__get_board untrusted-input
  • mcp__github-hot-board__get_board_movers private-data
  • mcp__github-hot-board__get_repo private-data
  • mcp__github-hot-board__search_library private-data
  • mcp__github-hot-board__get_repo_history private-data

Pin

Keep the decision: fail CI when the tools change, follow every change, or show a badge.

Pin in CI

Fail a build when the tools you reviewed are not the tools the server serves today.

curl -s "https://radar.anlyon.com/api/v1/servers/io.github.JKWY01/github-hot-board/verify?hash=08801c52da625bddd8f63665245b4edaf74ad9937627983fd031595700a7379c" | jq -e '.changed == false'

Pinned hash 08801c52da62, from Oct 24, 2026, 12:18 UTC.

Watch

Get told when its tools change: a new tool, a new description, a new class.

https://radar.anlyon.com/servers/io.github.JKWY01/github-hot-board/changes.xml

An Atom feed. Works in any feed reader or Slack's RSS app.

Badge

Anlyon Radar badge for io.github.JKWY01/github-hot-board
[![Anlyon Radar](https://radar.anlyon.com/badge/io.github.JKWY01/github-hot-board.svg)](https://radar.anlyon.com/servers/io.github.JKWY01/github-hot-board)

Source: MCP Registry · repository. Synced Oct 24, 2026, 12:17 UTC.

GitHub Hot Board MCP server: questions and answers

Answered from the scan above, not from the publisher's description.

Is the GitHub Hot Board MCP server safe?

No scan can promise that. What its definitions show: 6 tools, all of which only read, and 0 findings from fixed checks. Read-only tools can still pass private data to a model.

Can the GitHub Hot Board MCP server delete data?

No tool is classed as destructive: going by their definitions, none of them deletes, cancels or revokes anything.

Can the GitHub Hot Board MCP server do things that cannot be undone?

No tool is classed as irreversible: none of them sends, pays, publishes or merges, going by their definitions.

What tools does the GitHub Hot Board MCP server have?

6 tools: 6 read. list_boards, get_board, get_board_movers, get_repo, search_library and get_repo_history.

Does the GitHub Hot Board MCP server need sign-in or OAuth?

Its remote endpoint did not answer the last anonymous look.

Does the GitHub Hot Board MCP server send data to outside services?

None of its tools sends, posts or publishes, or takes a recipient, channel or URL.

Has the GitHub Hot Board MCP server changed its tools?

Not since Anlyon Radar started tracking it. Last scanned Oct 24, 2026.