repo-scout
Related Servers
Alternatives to repo-scout
No user-submitted related servers found.
Related Servers
- AlicenseAqualityBmaintenanceEnables AI agents to analyze public GitHub repositories directly through tools for repo health scoring, recent commit summaries, good first issue discovery, and semantic Q&A over docs and issues.440 npm1MIT
- 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
- AlicenseAqualityCmaintenanceEnables AI agents to prospect across GitHub, PyPI, and npm, searching repositories, packages, and code patterns with read-only tools.777 PyPI5MIT
- AlicenseAqualityAmaintenanceEnables AI coding agents to discover and verify current open-source libraries and models using live GitHub activity, PyPI adoption, license checks, and hardware VRAM estimates before generating code.71Apache 2.0
- AlicenseNot gradedqualityBmaintenanceEnables AI coding agents to discover, evaluate, and select the best existing open-source implementations by assessing license compatibility, extracting only the needed symbols and dependencies, and producing integration or adaptation plans.Apache 2.0
- AlicenseAqualityCmaintenanceEnables AI builders to discover trending open-source projects for a given task by ranking repos based on GitHub momentum, npm/PyPI growth, and Hacker News buzz, with tools to recommend, search, assess health, and compare repositories.4MIT
TDQS
Scored across 3 tools
Each tool has a clearly distinct purpose: retrieving details for a specific known repo, searching by keywords, and generating a shortlist from a natural-language description. No overlap in functionality or target resource.
All tool names follow a consistent verb_noun pattern in snake_case: get_repo_details, search_repos, suggest_stack. This is a predictable and uniform convention.
With only 3 tools, the server is tightly scoped to the 'repo scout' purpose: discovery (search), semantic suggestion (suggest), and evaluation (get details). Each tool earns its place, and the count is within the ideal 3-15 range.
The tool surface covers the full workflow for scouting repositories: finding candidates (search_repos, suggest_stack) and inspecting them (get_repo_details). No obvious gaps or dead ends for the stated purpose.