ToolsMCP
mcp-oss-onramp
Listed in the official MCP Registry with an installable npm package. Capabilities below are the publisher’s own description.
- Type
- MCP server
- Publisher
- ryotaro-tanaka (GitHub)
- Prerequisites
- Install mcp-oss-onramp from npm (stdio transport). Inspect it before installing; AgentsByTask never installs discovered packages.
- Current version
- 0.1.3 · updated
- Official links
Publisher’s description
MCP server to scout beginner-friendly OSS issues with high precision using GitHub GraphQL
Evidence
Each record keeps its own date and scope. Labels are independent: documentation does not imply a checked connection, and a connection does not imply a passed task.
-
Listed in the official MCP Registry
Version 0.1.3, registry status active. 1 package (npm)
Publisher-supplied registry metadata. Not a checked connection, a safe package or a completed task.
- Source publisher
- ryotaro-tanaka (GitHub)
- Version observed
- 0.1.3
- Source
- registry.modelcontextprotocol.io/v0.1/servers/io.github.ryotaro-tanaka%2Fmcp-oss-onramp/versions/0.1.3
Listed for these tasks
| Task | Documented for this task | Unknowns | Why it is listed |
|---|---|---|---|
| Work with issues and pull requests | Publisher description mentions “github”, “issues”. | No connection check or task run. Capability is as described by the publisher. | Rule code-repositories matched: “github”, “issues”. Rule code-repositories. |
Published pricing
No published price recordedCost per completed task is only shown on a task page when a comparable run recorded metered spend and verified completions.
Registry record
- Packages
mcp-oss-onramp(npm, stdio)- Registry entry
- Official MCP Registry record (JSON)
- Namespace
io.github.ryotaro-tanaka/mcp-oss-onramp
AgentsByTask never installs discovered packages or connects to discovered endpoints during discovery. An endpoint string in a registry record is not a checked connection.