io.github.ryotaro-tanaka/mcp-oss-onramp
mcp-oss-onramp
Is the io.github.ryotaro-tanaka/mcp-oss-onramp MCP server down? No. It answered initialize and tools/list in the probe of 2026-10-30.
MCP server to scout beginner-friendly OSS issues with high precision using GitHub GraphQL
alive probed 2026-11-15 · unchanged since 2026-10-30
- Run it
- npx -y mcp-oss-onramp@0.1.3 (stdio, probed in a container with the network off)
- Host
- npmjs.com
- Reports itself as
- mcp-oss-onramp 0.1.1
- Capabilities
- tools
- Instructions
- none
- Of a 1M window
- <0.1 % of a 1M context window
- Count
- 191 tokens in Claude Opus 5.5, exact, measured 2026-10-16. With the Claude Code prefix mcp__…__ on each tool name: 206. The o200k_base estimate is 106. Counted again when the tool definitions change. Method.
- Repository
- https://github.com/ryotaro-tanaka/mcp-oss-onramp.git
- Registry
- active, updated 2026-05-16 · registry entry
Most expensive tools
The Claude column scales the o200k estimate of each tool by this server's ratio of exact to estimate, 1.80×.
| Tool | ≈ Claude tokens | o200k estimate | Share of this server |
|---|---|---|---|
| scout_issues | 191 | 106 | 100 % |
Compare this server with others.
More servers
Other registry entries on npmjs.com, the ones next to this name; all of them.
- io.github.ryanbaumann/platform-ai · alive
- io.github.ryanbihai/oceanbus-mcp-server · alive
- io.github.ryanthegentry/402index · alive
- io.github.rynald0cst0ltziam/warden · crashed on start
- io.github.ryudi84/api · alive
- io.github.ryudi84/api-tester · alive
- io.github.ryudi84/base64 · alive
- io.github.ryudi84/base64-forge-mcp · alive
Servers that mention onramp.
- com.mudko/onramperx · alive
- io.github.codespar/mcp-unblockpay · alive
- io.github.onrampbtc/proof-of-custody · alive
- io.github.codespar/mcp-moonpay · alive
Badge for the README
The result of the latest probe, the tool count and the token cost. The feed has an entry for every probe that changed them.
A mail when this server changes
Stops answering, comes back, tool set or cost changes. One confirmation mail first, a stop link in every mail.
For the publisher
- The server answers initialize and tools/list. Nothing to fix.