๐Ÿ“ก MCP Radar

How MCP Radar works

Full transparency: every number on this site is reproducible from the open-source pipeline.

Discovery

Every day, a GitHub Actions job searches GitHub for repositories created in the last 7 days matching MCP-related queries (topic:mcp-server, topic:model-context-protocol, "mcp server" in name/description). No submissions, no human curation โ€” if you publish an MCP server and it earns a few stars, the radar picks it up automatically.

Filtering

Forks, archived repositories and repos below a minimum star threshold are dropped. This removes the vast majority of noise: of the ~2,500 MCP-related repos created in a typical week, roughly 2% survive the filter.

Ranking โ€” the momentum score

score = stars รท age_in_days ร— 10 + forks ร— 2

Stars-per-day rewards velocity over accumulation: a 3-day-old server gaining 20 stars a day outranks a famous one coasting on history. Forks add a smaller signal of real developer adoption. The formula is deliberately simple and public โ€” if you think it can be gamed or improved, open an issue.

The data

Currently tracking 60 servers across 1 weekly snapshot(s). Everything is committed to the repo as JSON โ€” download it, build on it, no API key required. The git history is the full time series.

Updates

Daily at 02:17 UTC. The website redeploys automatically when data changes, and the RSS feed carries the newest arrivals.