repohunt
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| GITHUB_TOKEN | Yes | GitHub personal access token (read-only) for higher rate limits. |
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 |
|---|---|
| find_reposA | Search GitHub for repositories matching a development intent and return structured EVIDENCE (not a verdict) for you to rank. IMPORTANT — before calling this tool you MUST expand the user's single intent into 4-8 VARIED keyword queries: synonyms, likely library/package names, and problem restatements. Do not pass one raw phrase; keyword recall depends on the variety you supply. The server fires every query against GitHub's live search (README body included), dedupes, pre-ranks, and returns the strongest candidates each with a trimmed README excerpt + metadata. You then rank them and decide fork / study / avoid. Example — intent "rate limiting middleware for express": queries: [ "express rate limit middleware", "express-rate-limit", "api throttling node", "request throttling express", "leaky bucket rate limiter node", "ddos protection express middleware" ] |
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 1 tool
With only one tool, there is no ambiguity; the tool's purpose is clearly distinct.
Single tool uses snake_case, consistent with common MCP naming conventions.
One tool is appropriate for a focused 'repo hunting' purpose, though a slightly broader set might be expected for a complete search experience.
The tool covers the primary domain of searching GitHub repos with keyword expansion and ranking, leaving no obvious gaps for its stated purpose.