MCP Oss Onramp vs Core
A side-by-side look at the MCP Oss Onramp and Core MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
CoreVersion ControlPersonalized GitHub issue finder with multi-strategy search, deep vetting, and viability scoring — CLI, library, MCP server, and Claude Code plugin47FairAuth: not declaredVerdict: choose MCP Oss Onramp for version control work as a local process; choose Core for version control. You can also run both side by side in one mcpServers block.
Which MCP server should you choose?
Choose MCP Oss Onramp when
- You need dedicated capabilities in the Version Control domain.
- You prefer a local stdio subprocess transport.
Choose Core when
- You need dedicated capabilities in the Version Control domain.
- You have the keys it needs:
GITHUB_TOKEN.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | Core | |
|---|---|---|
| Category | Version Control | Version Control |
| Quality signal | 39/100 · Fair | 47/100 · Fair |
| Install command | Confirmed | Not confirmed yet |
| Transport | Local subprocess (stdio) | — |
| Auth | Not declared | Not declared |
| Pricing | Not declared | Not declared |
| Required env vars | None listed | GITHUB_TOKEN |
| Verified owner | Community listing | Community listing |
| GitHub stars | 0 | 2 |
| Directory activity | 0 views 0 installs 0 upvotes | 0 views 0 installs 0 upvotes |
| Tools | Not listed | Not listed |
| Full listing | View MCP Oss Onramp | View Core |
Tools & capabilities
MCP Oss Onramp tools
No tool names declared yet. Check the project README from the listing page.
Core tools
No tool names declared yet. Check the project README from the listing page.
Ready-to-paste client configs
Paste either block (or both) into your client config, e.g. claude_desktop_config.json or ~/.cursor/mcp.json. We only show a config when the install command is confirmed.
MCP Oss Onramp
{
"mcpServers": {
"mcp-oss-onramp": {
"command": "npx",
"args": [
"-y",
"mcp-oss-onramp"
]
}
}
}
Core
No confirmed install command for Core yet — follow the setup steps linked from its listing page rather than a guessed package name.
Frequently asked questions
MCP Oss Onramp is categorized under Version Control and uses a local stdio subprocess. Core belongs to Version Control and uses an install path we have not confirmed yet. Pick MCP Oss Onramp for version control work and Core for version control.
Copy the mcpServers block from the config section on this page into your client's config (for example claude_desktop_config.json or ~/.cursor/mcp.json), then fully restart the client. Core has no confirmed install command yet — follow its own setup instructions.
MCP Oss Onramp has no declared pricing — check the project's own site. Core has no declared pricing — check the project's own site. If a server needs environment variables such as API keys, define them under the env key in your client's MCP config.
Yes. MCP clients support multiple servers: add mcp-oss-onramp and oss-scout-core as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, MCP Oss Onramp has a quality signal of 39/100 (Fair) with 0 views, 0 installs and 0 GitHub stars. Core has 47/100 (Fair) with 0 views, 0 installs and 2 GitHub stars.