Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, email [email protected] and we’ll put it right.

io.github.ryotaro-tanaka/mcp-oss-onramp

NPM · MCP-OSS-ONRAMP · SCANNED AUG 3

MCP server to scout beginner-friendly OSS issues with high precision using GitHub GraphQL

Available components

npm · mcp-oss-onramp 63
+23 this week 63 Trust /100
Trust breakdown (6 categories)

How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score →

Supply Chain Security86
  • No malware found by supply-chain analysis.Pass
  • Only part of the dependency tree could be resolved (94 of 98), so this covers what we could see, not the whole tree.Partial
  • No install/post-install scripts declared.Pass
  • Only part of the dependency tree could be resolved (94 of 98), so this covers what we could see, not the whole tree. View diagnostics → Partial
Provenance & Transparency19
Schema Quality & AI Usability77
  • AI-judged instruction clarity (excellent).Pass
  • Tool/resource definitions use about 86 tokens (~86/item across 1 items; 1 tools + 0 resources), lean.Pass
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management23
  • Stability observed for 7 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 100% of tool parameters carry a description.Pass
Capabilities100
  • Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Install

Add this component to your MCP client. Where a client-specific snippet is available, pick your client below and copy it straight into your config; otherwise use the connection detail shown.

npm · mcp-oss-onramp

# add to Claude Code
claude mcp add ryotaro-tanaka-mcp-oss-onramp -- npx -y mcp-oss-onramp
# add to Codex CLI
codex mcp add ryotaro-tanaka-mcp-oss-onramp -- npx -y mcp-oss-onramp
// opencode.json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "ryotaro-tanaka-mcp-oss-onramp": {
      "type": "local",
      "command": [
        "npx",
        "-y",
        "mcp-oss-onramp"
      ],
      "enabled": true
    }
  }
}
# add to OpenClaw
openclaw mcp add ryotaro-tanaka-mcp-oss-onramp --command npx --arg -y --arg mcp-oss-onramp
# ~/.hermes/config.yaml
mcp_servers:
  ryotaro-tanaka-mcp-oss-onramp:
    command: "npx"
    args: ["-y", "mcp-oss-onramp"]
// mcp.json
{
  "mcpServers": {
    "ryotaro-tanaka-mcp-oss-onramp": {
      "command": "npx",
      "args": [
        "-y",
        "mcp-oss-onramp"
      ]
    }
  }
}
Changelog

Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.

  • 2 Aug 26 +39
    • Provenance: fail → unverified ▼ security
    • Install scripts: pass → unverified ▼ security
    • Known CVEs: unverified → partial ▲ security
    • Stability: Stability not yet verified: not enough scan history yet (needs a 30-day window). security
    • Maintenance: pass → unverified ▼ functional
    • Dependency health: partial → unverified ▼ functional
    • License: pass → unverified ▼ functional
    • Stability: unverified → 0.20 ▲ functional
    • MCP protocol: unverified → pass ▲ functional
    • Tool coverage: unverified → 100 ▲ functional
    • Licence: MIT functional
  • 1 Aug 26 −1

    No change was recorded against any check on this day. Supply Chain Security went from 70 to 66.

  • 31 Jul 26 −18
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 30 Jul 26 −31
    • Known CVEs: partial → unverified ▼ security
    • Malware scan: pass → unverified ▼ security
    • Dependency health: partial → unverified ▼ functional
  • 29 Jul 26 +55
    • Provenance: unverified → fail ▼ security
    • Known CVEs: unverified → partial ▲ security
    • Install scripts: unverified → pass ▲ security
    • Maintenance: unverified → pass ▲ functional
    • License: unverified → pass ▲ functional
    • Tool coverage: unverified → 100 ▲ functional
    • Schema quality: unverified → excellent ▲ functional
    • Licence: MIT functional
  • 28 Jul 26 −21
    • Tool coverage: 100 → unverified ▼ functional
    • Dependency health: unverified → partial ▲ functional
    • First check of Schema quality: unverified functional
  • 27 Jul 26 40

    First indexed and scored.

Diagnostics

Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.

Captured 3 Aug 2026 · Analysed npm/[email protected]

Provenance none

Ecosystem: npm · Outcome: none

Dependencies 94 packages

94 packages in the resolved dependency tree · 94 deprecated · 29 stale.

The dependency tree was only partially resolved, so these counts may be incomplete.

MCP tools — 1 exposed · ~86 tokens

The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability.

Tool Tokens
scout_issues ~86

Scout a GitHub repository to discover truly available, beginner-friendly issues. Use this when a user wants to start contributing to OSS, needs a 'good first issue', or wants to verify if an issue is genuinely unassigned by cross-referencing linked Pull Requests (detecting 'ghost' tasks).

NameTypeReqDescription
repositorystringyesFull repository name (e.g., 'owner/repo')

No output schema declared.

No examples provided.