“Tools indexed” beats star count for MCP servers
A quiet 200-star server with a clean tools/list often beats a famous repo with zero indexed tools — agents call capabilities, not GitHub popularity.
Source: Influzer.ai
GitHub stars still dominate how people browse MCP lists. Agents do not care. They call tool names — scrape_url, run_query, create_issue — and fail loudly when the server exposes nothing useful via tools/list.
In Influzer’s registry, the useful signal is whether tools are indexed and re-validated, not whether the repo is famous:
- Star count → social proof for humans
- Tool index → runtime proof for agents
- Transport + auth notes → whether you can actually connect from Claude, ChatGPT, or Cursor
A smaller server with three crisp tools and a remote URL often wins a coding-agent stack over a viral local demo with an empty or undocumented tool surface.
Why it matters: search and recommend flows (including Influzer MCP Discovery) rank by capability. Authors who ship discoverable tools get found; authors who only ship a README get starred and skipped.
Start with the Top 100 (curated, tools-first) or search the full directory by tool name. Audit any server before production with the questions in our deeper guide: seven questions before you connect another tool.