oss-trends-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| GITHUB_TOKEN | No | GitHub token to increase API rate limits. Without it, GitHub allows 10 searches/min and 60 core requests/hour, so star-momentum sampling often degrades to fallback signals. |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| recommend_ossB | Given a task or feature description, recommends trending open-source projects using GitHub star momentum, npm/PyPI download growth and Hacker News buzz. Pass focused github search terms in queries for best results. |
| search_reposC | Raw github repository search with normalized output. Use for ad-hoc exploration. |
| repo_healthA | Deep signals for one github repository: star momentum, maintenance freshness, npm/PyPI adoption, HN buzz, plus a transparent 0-100 score breakdown. |
| compare_reposA | Side-by-side trend comparison of 2-6 github repositories, ranked by composite score. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
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.