Top100 ★ 3 on GitHub

Data refreshed 18 November 2026, 13:49 UTC

WebMCP: AI agent tools for this site

Top100 is an ordinary static website — and a WebMCP client-side MCP server for the same content. An AI agent running in the browser can discover 16 tools here and call them directly instead of scraping the tables, with the results the page itself would have produced.

Try the tools in this tab

The fastest way to see WebMCP working is the debug panel on this site: it lists every registered tool with its JSON Schema and lets you call it by hand, through exactly the same validation, rate limiting and output budget an agent's call goes through.

To drive the tools with a real agent, enable WebMCP in your browser:

Security model

WebMCP tools are code the page runs on the agent's behalf, so the interesting questions are what a tool can reach, what it can change, and what a hostile string could do once it is inside a model's context. The answers here are deliberately boring.

What this site does about each WebMCP risk, and where the code lives.
RiskMitigation on this site
Cross-origin reachTools are registered without exposedTo, so only this origin can see or call them. Registration is skipped entirely inside a cross-origin iframe unless the embedder granted allow="tools".
Malformed or hostile argumentsEvery call is validated against the tool's JSON Schema before it runs: types, ranges, enum membership, 200-character string caps, array length caps, four levels of nesting. Unknown arguments are ignored and reported back.
Prototype pollution__proto__, prototype and constructor are rejected anywhere in an argument tree, and validated values are copied into a fresh object.
Runaway agents90 calls per minute per document, 30 per tool, a 100 ms minimum gap, one in-flight call per tool, and an 8-second timeout (15 s for the three tools that read a dataset file) wired to AbortSignal.
Context floodingResults are capped at 1500 characters. Array payloads are shrunk until the envelope fits and the result says exactly how many items were dropped.
Prompt injection from repository textDescriptions, topics and names come from GitHub, so any tool that returns them declares untrustedContentHint: true and every result carries "trust": "untrusted" with a note. Control characters are stripped and every free-text field is length-capped. Nothing on this site asks an agent to run a command, reveal a secret or trust a suggestion.
Data exfiltrationThe only network calls are same-origin GETs of files under data/, with credentials omitted, redirects refused and a 4 MB ceiling. No cookies, no analytics, no third-party requests, no sendBeacon.
Injection into the pageTool results and tool names are rendered with textContent; innerHTML and eval are never used anywhere in the WebMCP code, and the build fails a test if they appear.
Silent automationTools act on the visible page and report what they did: a live region announces every call, and the tools that change the page (filter_repository_table, open_page) are the only two that are not read-only. Both are annotated accordingly.

Every tool

Annotations follow the WebMCP annotations object: readOnlyHint means the tool does not change anything, untrustedContentHint means its result contains third-party text, and consequentialHint — never set here, because nothing on this site books, buys or deletes anything — would ask for user confirmation.

Discover the site

get_site_info

Describe the Top100 site: what it publishes, how fresh the data is, how many languages and repositories it ranks, where the raw JSONL lives, and which pages exist. Call this first when you need to know what this site can answer or how current its numbers are.

read-only · available on: all

No arguments.

get_page_context

Return where the user is right now: page type, canonical URL, the language this page covers (if any), how many repository rows are on the page, and the timestamp of the data being shown. Use it to resolve deictic prompts such as "this list" or "the table here".

read-only, untrusted content · available on: all

No arguments.

list_languages

List the languages Top100 ranks, with each one's most-starred repository, the star count to reach 100th place, the median inside the top 100 and how many repositories GitHub reports for it. Paged: five rows per call, use offset to page through the full language list. Every row's page URL is base_url + /languages/<slug>.html.

read-only, untrusted content · available on: all

get_language_stats

Statistics for one language's top 100: the leading repository and its stars, the entry bar for 100th place, the median star count, the most common licence and how many of the 100 use it, the JSONL download with its record count and SHA-256 checksum, and a one-line description of the list. Accepts a language key such as python, c++, c# or objective-c.

read-only, untrusted content · available on: all

List every file this site publishes for machine use, with its URL: the JSONL dataset (one file per language), the Markdown lists, feed.xml, sitemap.xml, robots.txt, llms.txt, llms-full.txt, README.md, LISTS.md, the search index and the WebMCP manifest that carries every dataset checksum. Pass language=<key> for one file's size and SHA-256; pass family=dataset for the per-language URLs.

read-only · available on: all

Query the data

get_top_repositories

Return a ranked slice of the repository table on the current page: rank, name, stars, forks, licence, last push and a short description. On a language page this is that language's top 100; on the homepage it is the overall top 10. Five rows by default, up to 25 (larger requests are trimmed to the result budget and say so). Use get_repository for the full record of one row.

read-only, untrusted content · available on: repos

search_repositories

Search the full repository dataset by keyword (matched against name, description and topics) with optional filters for language, star range, SPDX licence and topic. Returns ranked matches with stars, forks, licence and page links. Sorting is deterministic: relevance, stars, forks, issues or recency.

read-only, untrusted content · available on: repos, home, languages

get_repository

Look up one repository by its full name (owner/name), or by its rank within a language's top 100. Returns stars, forks, open issues, licence, last push date, topics and description, plus links to its GitHub page and to the language list it appears in.

read-only, untrusted content · available on: repos, home

compare_repositories

Compare two to five repositories side by side: stars, forks, open issues, stars per fork, licence, last push and shared topics. Accepts owner/name strings and returns them in the order given, with a one-line verdict naming the leader by stars.

read-only, untrusted content · available on: repos, home

Act on the page

filter_repository_table

Act on the visible page: filter the repository table by keyword, licence, topic or minimum stars, then scroll it into view. Use reset to show every row again. Returns how many rows matched, and the page visibly updates so the human sees exactly what was filtered.

untrusted content · available on: table

open_page

Navigate the current tab to one of this site's own pages: home, the language index, a specific language list, methodology, dataset reference, comparison, FAQ or the WebMCP tools page. Only same-site pages can be opened; the user sees the navigation happen.

no annotations · available on: all

Read the documentation

get_methodology

Explain how the data is produced: the GitHub Search API query, the hourly schedule, rate-limit handling, the fields the Search API omits, and the known limitations. Called without arguments it returns the section ids, their titles and the overview; call it again with one of those ids to read that section in full.

read-only · available on: all

get_dataset_schema

Document the JSONL dataset: one file per language, one complete GitHub Search API repository object per line. Called without arguments it lists the field names and types; call it with field=<name> to read what one field means, or with language=<key> to get that file's download URL, size and SHA-256 checksum.

read-only · available on: all

get_comparison

Explain how Top100 differs from other GitHub ranking sources — GitHub Trending, gitstar-ranking.com, EvanLi/Github-Ranking, OSS Insight, Star History, GH Archive and BigQuery — including where each one is the better tool. Called without arguments it lists the sources; pass one to read its full comparison.

read-only · available on: all

answer_question

Answer a question about this project from the site's own FAQ: refresh cadence, licensing, whether it needs an API key, how to download the data, how to add a language, why some fields are missing. Returns the closest matches with their answers, ranked deterministically.

read-only · available on: all

Diagnostics

run_webmcp_self_test

Run this page's own WebMCP checks: page data present, tools registered, character budgets respected, prototype pollution rejected, output budget enforced, and every registered tool answering a call with a structured envelope. Intended for developers and test harnesses.

read-only, debugging only · available on: all

No arguments.

How the runtime works

assets/webmcp-core.js does three things, in this order:

  1. Use what the browser has. If document.modelContext exists (or the older navigator.modelContext from the origin-trial builds), the tools are registered there, unchanged.
  2. Otherwise install a polyfill. A dependency-free implementation of the same surface — registerTool, getTools, executeTool, provideContext, the toolchange, toolactivated and toolcancel events, and unregistration through an AbortSignal — is installed on document.modelContext. It never replaces a real implementation, and it refuses to install on an insecure origin or in a cross-origin frame without permission.
  3. Wrap every tool in the same guard. The validation, rate limiting, timeouts, output budget and envelope formatting live inside each tool's execute(), so an agent that calls the native executeTool gets exactly the same guarantees as one that calls the polyfill.

Two URL parameters exist for testing, and neither is read by anything else: ?webmcp_debug=1 opens the debug panel, and ?webmcp_polyfill=1 forces the polyfill even where the browser has native support.

Tools are registered per page. A language page registers the tools that make sense for its 100 rows; the FAQ page registers the documentation tools; nothing registers a tool it cannot answer. The manifest of what is available where is published as data/webmcp-manifest.json.

For agents that never open the page

WebMCP's own discoverability limit is that a client has to visit a page to know what it offers. Two static artifacts cover the gap:

Every data file with its checksum, for download verification.
LanguageFileRecords SizeSHA-256
TypeScriptdata/JSONL/typescript.jsonl100560.1 KB1db48b7dd8ce7380…
Pythondata/JSONL/python.jsonl100589.0 KBa5525902c812f944…
JavaScriptdata/JSONL/javascript.jsonl100564.9 KB2061e567139461fc…
Javadata/JSONL/java.jsonl100563.1 KB734263fb7258c68e…
C#data/JSONL/c#.jsonl100567.6 KB60821a91b0d6f268…
C++data/JSONL/c++.jsonl100556.3 KB26a84586a623a8ab…
PHPdata/JSONL/php.jsonl100554.1 KB519959709aeca4f5…
Shelldata/JSONL/shell.jsonl100562.6 KBa3e5fe36df37b632…
Cdata/JSONL/c.jsonl100546.3 KBf1b2e4723cced173…
Godata/JSONL/go.jsonl100548.6 KB9d7fcfd04e60ea4a…
Rustdata/JSONL/rust.jsonl100547.6 KB2da87b898fc23f09…
Rubydata/JSONL/ruby.jsonl100546.9 KB19568671a4b242ba…
Kotlindata/JSONL/kotlin.jsonl100556.3 KBedf2ba93cca36a29…
Swiftdata/JSONL/swift.jsonl100557.3 KB46b67e088559552a…
Dartdata/JSONL/dart.jsonl100568.6 KB61bb9ca140b0895e…
HTMLdata/JSONL/html.jsonl100574.6 KBc75c4e33f23bf6da…
CSSdata/JSONL/css.jsonl100562.9 KBfe5b010273481340…
SQLdata/JSONL/sql.jsonl100588.0 KBaf891d9e070310d5…
Scaladata/JSONL/scala.jsonl100549.9 KBbb6bd17e91b2d4db…
Luadata/JSONL/lua.jsonl100555.7 KBb4dcf5d811b7496a…
Groovydata/JSONL/groovy.jsonl100577.3 KB00159e3d31ed465d…
Objective-Cdata/JSONL/objective-c.jsonl100559.8 KBe4df8fa3a7a64814…
Perldata/JSONL/perl.jsonl100549.9 KBb818738e9a9659ab…
Haskelldata/JSONL/haskell.jsonl100546.1 KB55682a7cf683b279…
Assemblydata/JSONL/assembly.jsonl100709.7 KBc8aadad0e43ed7b5…
Rdata/JSONL/r.jsonl100546.0 KBc1bc773e4603b2b4…
Juliadata/JSONL/julia.jsonl100567.3 KB2ecb6130d389483f…
Elixirdata/JSONL/elixir.jsonl100550.1 KBf52dfca453e6e8e6…
PowerShelldata/JSONL/powershell.jsonl100578.1 KBcf833bc6c261ee79…
Nixdata/JSONL/nix.jsonl100552.6 KB235281400af542dd…
Zigdata/JSONL/zig.jsonl100536.0 KB08a32e0555cd1a20…
Clojuredata/JSONL/clojure.jsonl100542.4 KBf4a69f59d78bbc23…
Erlangdata/JSONL/erlang.jsonl100532.1 KBee23b4ce91447d35…
OCamldata/JSONL/ocaml.jsonl100546.4 KBe587ef7202a3bebd…
Soliditydata/JSONL/solidity.jsonl100567.4 KBcc8929103d70eea6…
Fortrandata/JSONL/fortran.jsonl100550.9 KB2eea33c565924f88…
Vim Scriptdata/JSONL/vim script.jsonl100545.0 KB8f6724cf50ed3d1e…
F#data/JSONL/f#.jsonl100558.1 KBe01913668bf5058c…

Limitations, stated plainly

Questions about the tools

Do I need a browser extension?

No. Any browser with WebMCP support exposes these tools to whatever agent is running there; the extension is only a convenient way to test.

Does this change how the site works for people?

No. Every page is complete HTML before any script runs, the WebMCP code adds a small collapsible panel and nothing else, and with JavaScript off the site is byte-for-byte the site it was.

Is anything tracked?

No cookies, no analytics, no third-party requests. The only network traffic the tools generate is this site fetching its own data files.