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.aissablk1/mcp-roadmapsh

NPM · MCP-ROADMAPSH · SCANNED AUG 3

MCP server for roadmap.sh: roadmaps, best practices, interview questions, projects & progress

Available components

+22 this week 67 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 Security87
  • No malware found by supply-chain analysis.Pass
  • Only part of the dependency tree could be resolved (95 of 99), 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 (95 of 99), so this covers what we could see, not the whole tree. View diagnostics → Partial
Provenance & Transparency45
Schema Quality & AI Usability70
  • AI-judged instruction clarity (good).Pass
  • Tool/resource definitions use about 663 tokens (~41/item across 16 items; 16 tools + 0 resources), lean.Pass
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management27
  • Stability observed for 8 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage89
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 67% of tool parameters carry a description.Partial
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-roadmapsh

# add to Claude Code
claude mcp add aissablk1-mcp-roadmapsh -- npx -y mcp-roadmapsh
# add to Codex CLI
codex mcp add aissablk1-mcp-roadmapsh -- npx -y mcp-roadmapsh
// opencode.json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "aissablk1-mcp-roadmapsh": {
      "type": "local",
      "command": [
        "npx",
        "-y",
        "mcp-roadmapsh"
      ],
      "enabled": true
    }
  }
}
# add to OpenClaw
openclaw mcp add aissablk1-mcp-roadmapsh --command npx --arg -y --arg mcp-roadmapsh
# ~/.hermes/config.yaml
mcp_servers:
  aissablk1-mcp-roadmapsh:
    command: "npx"
    args: ["-y", "mcp-roadmapsh"]
// mcp.json
{
  "mcpServers": {
    "aissablk1-mcp-roadmapsh": {
      "command": "npx",
      "args": [
        "-y",
        "mcp-roadmapsh"
      ]
    }
  }
}
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.

  • 3 Aug 26 +4
    • Stability: unverified → 0.27 functional
  • 2 Aug 26 +43
    • Provenance: unverified → fail security
    • Install scripts: unverified → pass security
    • Known CVEs: unverified → partial security
    • Malware scan: unverified → pass security
    • Stability: Stability not yet verified: not enough scan history yet (needs a 30-day window). security
    • Security disclosure: fail → unverified functional
    • Tool coverage: 100 → unverified functional
    • License: unverified → pass functional
    • Dependency health: unverified → partial functional
    • Maintenance: unverified → pass functional
    • MCP protocol: unverified → pass functional
    • Schema quality: unverified → good functional
    • First check of Schema quality: unverified functional
    • Licence: MIT functional
  • 31 Jul 26 −7
    • 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 −18
    • Malware scan: pass → unverified security
  • 27 Jul 26 45

    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 95 packages

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

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

MCP tools — 16 exposed · ~663 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
best_practices_get ~48

Get a best-practice guide by slug (outline or raw graph).

NameTypeReqDescription
formatstring
slugstringyesroadmap.sh slug, e.g. 'frontend'

No output schema declared.

No examples provided.

best_practices_list ~19

List all best-practice slugs.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

progress_mark ~61

Mark a roadmap topic as learning, done, or skip (stored locally).

NameTypeReqDescription
labelstring
nodeIdstringyes
roadmapstringyesroadmap.sh slug, e.g. 'frontend'
statusstringyes

No output schema declared.

No examples provided.

progress_next ~39

Recommend the next unlearned topic for a roadmap based on local progress.

NameTypeReqDescription
roadmapstringyesroadmap.sh slug, e.g. 'frontend'

No output schema declared.

No examples provided.

progress_status ~36

Get local progress for a roadmap: counts and completion percent.

NameTypeReqDescription
roadmapstringyesroadmap.sh slug, e.g. 'frontend'

No output schema declared.

No examples provided.

project_get ~35

Get the markdown brief for one practice project by slug.

NameTypeReqDescription
slugstringyesroadmap.sh slug, e.g. 'frontend'

No output schema declared.

No examples provided.

projects_list ~15

List all practice-project slugs.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

questions_get ~35

Get the interview questions markdown for a question-group slug.

NameTypeReqDescription
slugstringyesroadmap.sh slug, e.g. 'frontend'

No output schema declared.

No examples provided.

questions_list ~16

List all interview question-group slugs.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

roadmap_diagnose ~25

Check connectivity to roadmap.sh and GitHub, and report cache/state status.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

roadmap_export ~111

Export an entire roadmap as a single markdown document (all topics' content concatenated). includeContent=false returns structure only; maxTopics caps the count.

NameTypeReqDescription
formatstringOutput format: markdown (default) or plain text for LLM ingestion
includeContentbooleanFetch each topic's markdown; false returns structure only
maxTopicsintegerCap the number of topics fetched (default: all)
slugstringyesroadmap.sh slug, e.g. 'frontend'

No output schema declared.

No examples provided.

roadmap_get ~58

Get a roadmap by slug. format=outline returns a readable topic plan with node ids; format=raw returns the full graph JSON.

NameTypeReqDescription
formatstring
slugstringyesroadmap.sh slug, e.g. 'frontend'

No output schema declared.

No examples provided.

roadmap_list ~21

List all available roadmap slugs (role-based and skill-based).

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

roadmap_search ~49

Search roadmap.sh slugs by keyword within a scope (roadmaps, best-practices, question-groups, projects, videos).

NameTypeReqDescription
querystringyes
scopestring

No output schema declared.

No examples provided.

roadmap_topic ~80

Get the markdown content and curated links for one topic of a roadmap (by nodeId from the outline, or by query).

NameTypeReqDescription
nodeIdstringExact node id from the outline
querystringTopic title substring, used if nodeId is unknown
slugstringyesroadmap.sh slug, e.g. 'frontend'

No output schema declared.

No examples provided.

videos_list ~15

List all video resource slugs.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.