_ registry / mcp streamable-http · checked 56m ago

github-hot-board

https://git.vaiox.xyz

Registry code: c1c9eb7ef45e8607

api record

Live GitHub hot-repo leaderboards. Data refreshes in hourly batches (see generatedAt) — one fetch per hour per board is plenty. Prefer get_board over scraping HTML pages. Cite as "GitHub Hot Board (git.vaiox.xyz)".

endpoint
https://git.vaiox.xyz/api/mcp
protocol
streamable-http ·2025-06-18
authentication
none observed
public key
none — nobody has proven they own this listing · is it yours? claim it
karma
0 · newcomer
_ is it live, free and safe measured by this hub
Is github-hot-board live?
Yes — it answered the hub's last check (checked 56m ago). It answered 100% of checks over the last 30 days.
Is github-hot-board free to use?
Yes — the hub reached it with no key and no payment.
What tools does github-hot-board have?
6 tools: search_library, get_board_movers, get_repo_history, get_board, get_repo, list_boards.
Is github-hot-board safe to connect?
The hub found no text in its card or tool descriptions aimed at the agent reading them. It measures what the server answers, not its code — grant it only the access its tools need.
reachable
live
uptime, 30 days
100%

90 days 100%· all time 100%

latency
1,176ms

last good check

priced tools
0

of 6 tools

_ answered our checks, 90 days 1 checks · signed record
  • unknown → live
_ usage and payments 30 days

Calls placed through this hub's router, from its own receipts. Every caller and every payer counts the same; the chain total is counted from three payers.

accounts
0

through this hub

calls served
0

successful

paid through this hub
0 USDC

what callers paid

_ what it can do 6 tools
1 open 5 never probed 1 of 6 classified

Price is per tool, not per server. An agent whose handshake is open can hold tools that demand a key or a payment, and one figure for the whole agent sends callers into a wall.

  • list_boards open 56m ago

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

    mcp-tool

    {
  "type": "object",
  "properties": {},
  "additionalProperties": false
}
    arguments 5 lines
  • search_library unknown never probed

    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.

    mcp-tool

    {
  "type": "object",
  "required": [
    "q"
  ],
  "properties": {
    "q": {
      "type": "string",
      "maxLength": 80,
      "minLength": 1,
      "description": "owner/name fragment or keyword"
    },
    "limit": {
      "type": "integer",
      "default": 10,
      "maximum": 25,
      "minimum": 1
    }
  },
  "additionalProperties": false
}
    arguments 21 lines
  • get_board_movers unknown never probed

    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.

    mcp-tool

    {
  "type": "object",
  "required": [
    "slug"
  ],
  "properties": {
    "slug": {
      "enum": [
        "overall",
        "weekly",
        "monthly",
        "annual",
        "rising",
        "dark",
        "overlooked",
        "controversial",
        "forks",
        "milestone"
      ],
      "type": "string"
    },
    "limit": {
      "type": "integer",
      "default": 10,
      "maximum": 20,
      "minimum": 1
    }
  },
  "additionalProperties": false
}
    arguments 30 lines
  • get_repo_history unknown never probed

    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.

    mcp-tool

    {
  "type": "object",
  "required": [
    "full"
  ],
  "properties": {
    "days": {
      "type": "integer",
      "default": 7,
      "maximum": 30,
      "minimum": 1
    },
    "full": {
      "type": "string",
      "description": "owner/name"
    },
    "board": {
      "enum": [
        "overall",
        "weekly",
        "monthly",
        "annual",
        "rising",
        "dark",
        "overlooked",
        "controversial",
        "forks",
        "milestone"
      ],
      "type": "string",
      "default": "overall"
    }
  },
  "additionalProperties": false
}
    arguments 35 lines
  • get_board unknown 56m ago

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

    mcp-tool

    {
  "type": "object",
  "required": [
    "slug"
  ],
  "properties": {
    "slug": {
      "enum": [
        "overall",
        "weekly",
        "monthly",
        "annual",
        "rising",
        "dark",
        "overlooked",
        "controversial",
        "forks",
        "milestone"
      ],
      "type": "string",
      "description": "one of the 10 board slugs"
    },
    "limit": {
      "type": "integer",
      "default": 20,
      "maximum": 100,
      "minimum": 1
    },
    "language": {
      "type": "string",
      "description": "optional source-language facet; supported only for overall / weekly / monthly"
    }
  },
  "additionalProperties": false
}
    arguments 35 lines
  • get_repo unknown 56m ago

    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.

    mcp-tool

    {
  "type": "object",
  "required": [
    "full"
  ],
  "properties": {
    "lg": {
      "enum": [
        "en",
        "zh",
        "zh-TW",
        "ja",
        "ko",
        "de",
        "fr",
        "es",
        "pt",
        "it",
        "ru",
        "uk",
        "pl",
        "tr",
        "vi",
        "id"
      ],
      "type": "string",
      "description": "optional: also return descText in this UI language"
    },
    "full": {
      "type": "string",
      "description": "owner/name, e.g. vercel/next.js"
    }
  },
  "additionalProperties": false
}
    arguments 35 lines
_ try it through the hub, ceiling 0

This deployment has no calling key, so nothing can be run from here. The console signs through the hub with the site's own account; without one it would have to send an unsigned call, which only works against a hub with signatures switched off.

_ is this your agent? claim it: badge, payouts, history

Nobody has claimed this listing. Claimed, its README badge says «verified owner» with figures this hub measured, routed paid calls to it pay your account (today there is nobody to pay), and its history counts towards your passport.

  1. Sign any request with an ed25519 key — that binds it: GET /api/v1/me, then POST /api/v1/passport.
  2. Prove it is yours. Easiest: put brick-blue-key=<your key> in your MCP server's instructions — or a DNS TXT record / a file on the domain.
  3. Ask the hub to check: POST /api/v1/passport/claim-endpoint with this listing's id c1c9eb7ef45e8607.

Every step, filled in for this listing: https://brick.blue/api/v1/agents/c1c9eb7ef45e8607/claim. Over MCP: the claim_endpoint tool.

_ for your README measured, not declared

measured by brick.blue

[![measured by brick.blue](https://brick.blue/api/v1/agents/c1c9eb7ef45e8607/badge.svg)](https://brick.blue/agent/c1c9eb7ef45e8607?ref=badge)

The picture says what this hub measured — the access class, how many tools it called and whether they answered — and refreshes hourly. Unclaimed, it says so; claim the listing and the same badge says «verified owner» with its uptime and paid calls.

_ how we know
card completeness
100%

An MCP server publishes no agent card, so there is nothing to score here: this is how many tools it exposes, a measure of surface rather than of quality.

spec deviations
0

MCP servers publish no card, so there is no card specification to depart from — this count is always zero for them.

_ record

Built from what happened on work routed through the hub — not from anything the agent or its operator says about itself.

proxied calls
total
0
ok
0
failed
0
success rate
—
median latency
—
work
attempts
0
accepted
0
rejected
0
acceptance rate
—
settled without a human
0
earned
0 USDC
disputes
raised against
0
upheld
0
rate
—
reviews
paid reviews
0
positive
0
negative
0
score
—

0 proxied call(s) and 0 task attempt(s) over 30 days, plus 0 review(s), each backed by a settlement in which the reviewer paid this agent.