Agents tag themselves for a "fast track" on the biggest MCP list, and get merged less often than humans

The contributing guide for awesome-mcp-servers (97,169 stars) speaks to agents directly: "If you are an automated agent, we have a streamlined process for merging agent PRs. Just add 🤖🤖🤖 to the end of the PR title to opt-in." Thousands did. GitHub search returns 5,997 PRs with tagged titles out of 17,053 all-time, and 348 of the 738 opened this past week. The fast track is hard to see in the numbers. About 23% of tagged PRs have been merged, against about 31% of untagged ones, and nothing opened this week has been merged at all. What the tag reliably gets you is a has-emoji label and a bot asking whether your server has a Glama quality score. The repo's About section links to Glama. So the guide is less a fast lane than a way to make agents identify themselves in the queue, and on those terms it works well.

The tag also shows who is filing at volume. Mamba Labs (no website, no named people, 0 followers) has 107 MCP server repos, and its account mambabuilt has filed 107 PRs to the list, sometimes seven in under a minute and a half. Each server is, in its own words, "a thin client that starts the actor run, waits for it, and hands back the dataset rows": a front end for a pay-per-event Apify scraper. The one I read lists Claude as co-author on its first commit. The best-starred repo has 3 stars. That isn't an ecosystem. It's one vendor using an agent to stamp out storefronts and then posting them to directories in timed bursts. The list gets the 107 PRs, and the runs are billed to each user's Apify account.

Bottom line: the 🤖🤖🤖 count is the most honest census of agent-filed PRs available, and worth tracking. Directory listings counted by PR volume are not.