Leaderboard
leaderboard: 10 operations.
Also for this capability: API · CLI · MCP · SDKs
leaderboard: 10 operations. Name one in "op" and pass that operation's own arguments in "input". describe returns an operation's input schema.
| Tool | leaderboard |
| Address | https://api.hanzo.ai/v1/mcp |
| Method | tools/call (JSON-RPC 2.0) |
| Arguments | 2, 1 required |
| Operation | GET /v1/leaderboard/activity · GET /v1/leaderboard/beta · GET /v1/leaderboard/bounty · GET /v1/leaderboard/galaxy · GET /v1/leaderboard/optin · GET /v1/leaderboard/pulse · GET /v1/leaderboard/standing |
| Product | leaderboard |
Arguments
| Field | Type | Required | Default | Values | Description |
|---|---|---|---|---|---|
input | object | — | — | — | arguments for the chosen op |
op | string | yes | — | — | — |
tools/list declares a type, a description, which fields are required and an enumerated value set for each field and nothing further, and every column above is MCP's own. This tool takes an operation name and that operation's arguments, so what the document constrains is what goes inside input, field by field, on the operation you name — ask describe for that. A — means MCP does not constrain the field.
Call it
A tools/call carries every argument in one flat object — nothing binds to a path or a query string. This call carries exactly the arguments the operation requires, so it is the smallest one that can run.
curl -X POST https://api.hanzo.ai/v1/mcp \
-H "Authorization: Bearer $HANZO_API_KEY" \
-H "Content-Type: application/json" \
-d '{
"jsonrpc": "2.0",
"id": 1,
"method": "tools/call",
"params": {
"name": "leaderboard",
"arguments": {
"op": "list_leaderboards"
}
}
}'Values are the operation's own defaults and enumerated values where it declares them, and a <placeholder> where neither source declares one. tools/list needs no credential; tools/call does — called without one MCP answers HTTP 200 with a JSON-RPC result whose isError is set and whose text says what was missing. How to get a key →
The operation behind it
leaderboard dispatches to 10 operations. 7 of them MCP names exactly as the document ids them, and those are below; for the rest MCP has its own verb, which describe resolves.
| Operation | Route | Product | Summary |
|---|---|---|---|
get_leaderboard_activity | GET /v1/leaderboard/activity | leaderboard | Returns the per-day usage series for ONE authorized subject — the points a contribution heatmap and a timeline are drawn from, gap-filled so every day in the range is present. |
get_leaderboard_beta | GET /v1/leaderboard/beta | leaderboard | Ranks everyone on the hanzo.ai/beta waitlist by one score: 1 per star on GitHub verified for the record and 1 per founder link followed, plus 1 per org that signed up with its referral code, plus 20 per such org that has made metered spend, plus 1 per 100,000 tokens the person used, all time. |
get_leaderboard_bounty | GET /v1/leaderboard/bounty | leaderboard | Returns the ranked bug hunters and bounty contributors, and the recent bug and bounty awards. |
get_leaderboard_galaxy | GET /v1/leaderboard/galaxy | leaderboard | Returns every ranked org as a star, for a page to draw the community as a galaxy: each star holds its band in the reward program's level table, a coarse size (a factor of two), the star of the org that referred it, if any, and, only for the ranks the reader has earned a view of, its exact points and the name the standing shows for it. |
get_leaderboard_optin | GET /v1/leaderboard/optin | leaderboard | Returns the caller's own public-listing preference and their org's, each with whether the caller may change it. |
get_leaderboard_pulse | GET /v1/leaderboard/pulse | leaderboard | Returns how fast the platform is being used and is spreading, as counts by day for thirty days and by hour for the last day: tokens used, orgs active, orgs signed up, orgs that came through a referral link, orgs using a model for the first time (with the models most tried), and how many different models were in use (variety). |
get_leaderboard_standing | GET /v1/leaderboard/standing | leaderboard | Returns the public board of who has used and built the most on Hanzo, shown as a window around the reader. |
The same capability over plain HTTP is in the leaderboard API reference, on https://api.hanzo.ai.
All 127 tools · MCP · API reference
Generated from tools/list on https://api.hanzo.ai/v1/mcp — 127 tools captured 2026-11-10.