mcp-oss-onramp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| MCP_OSS_ONRAMP_GITHUB_TOKEN | No | GitHub token for higher rate limits and better precision. Alternatively, authenticate via GitHub CLI. |
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 | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| scout_issuesA | Scout a GitHub repository to discover truly available, beginner-friendly issues. This tool uses GitHub GraphQL for high-precision PR cross-referencing. IMPORTANT FOR AI AGENTS: To avoid rate limits and enable high-precision scouting, ensure the |
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 possibility of confusion or overlap. The tool's purpose is distinct and well-defined.
The single tool name 'scout_issues' follows a clear verb_noun pattern. Consistency is inherently maintained with one tool.
Having only one tool is too few for the apparent scope of an OSS onboarding server. It feels thin and limits functionality.
The server covers only scouting for issues, missing other essential operations like fetching issue details or interacting with issues. This leaves significant gaps for a comprehensive tool set.