oss-trends-mcp
Related Servers
Alternatives to oss-trends-mcp
No user-submitted related servers found.
Related Servers
- AlicenseAqualityCmaintenanceEnables AI assistants to scout GitHub for existing open-source projects, libraries, and frameworks before building from scratch, offering tools for stack suggestions, repository searches, and detailed repo evaluation.31MIT
- AlicenseBqualityDmaintenanceEnables AI agents to search an index of open source repos and tools by what they do, their callable interface (MCP, CLI, SDK, API, etc.) and OG score, plus fetch repo details, category listings, and weekly trending projects.401MIT
- AlicenseAqualityAmaintenanceEnables coding agents to receive scored, verified library recommendations, compare repositories side by side, and list trending GitHub repositories by day, week, or month.3MIT
- AlicenseNot gradedqualityFmaintenanceOpen source intelligence for AI agents — GitHub project-health scoring, package dependency-risk analysis, trending repositories, license checks, and side-by-side package comparison.MIT
- AlicenseNot gradedqualityCmaintenanceDiscover, rank, and compare GitHub repositories from any MCP-compatible AI client. Enables searching, filtering, ranking, and evaluating open-source repositories by topic, language, stars, license, activity, and relevance.MIT
- AlicenseAqualityCmaintenanceEnables AI assistants to search, inspect, compare, and evaluate GitHub repositories using read-only tools, including topic discovery, repository health scoring, security advisories, dependency audits, and supply-chain risk checks. It returns concise, readable results and can work without a token, with optional authentication for higher rate limits and code search.16814 npmMIT
TDQS
Scored across 4 tools
Each tool serves a distinct purpose: recommendation, raw search, in-depth single-repo health, and multi-repo comparison. There is no overlap in functionality, so an agent can easily select the right tool for the task.
Three tools follow a verb_noun pattern (recommend_oss, search_repos, compare_repos) while repo_health is noun_noun. The style is uniform in lowercase with underscores, and the one deviation is minor and still intuitive.
With 4 tools, the server is tightly scoped to its purpose of OSS trend analysis. Each tool covers a distinct aspect without bloat, making the set manageable and well-focused.
The surface covers the core workflow: discover via search, get recommendations, deep-dive into one repo, and compare multiple. Missing features like historical trend charts or per-repo dependency analysis are minor gaps that don't block primary use cases.