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

io.github.aissablk1/mcp-roadmapsh

NPM · MCP-ROADMAPSH

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

Available components

0 this week 78 Trust /100

Last scanned (13 hours ago)

Scores higher than 59% of npm servers

Category Education and Research

Trust breakdown (7 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 → Why this is hard to score →

Supply Chain Security81
  • No malware found by supply-chain analysis.Pass
  • CVE check failed: a known high-severity CVE affects zod 3.25.76, a direct dependency. A fixed version is available. View diagnostics → Fail
  • No install/post-install scripts declared.Pass
  • 31 of 93 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency45
Schema Quality & AI Usability76
  • 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 Management100
  • No destabilizing schema changes in the last 30 days.Pass
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
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • We read all 16 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 16 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
  • Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
What we tested

Checks we ran (16)

  • Malware scan
  • Known CVEs
  • Install scripts
  • Dependency health
  • Source repository
  • Provenance
  • License
  • Maintenance
  • Security disclosure
  • Schema quality
  • Stability
  • Tool coverage
  • Injection markers
  • Destructive annotations
  • Judged manipulation
  • MCP protocol

Does not apply to this package (2)

  • Endpoint SecurityScored on hosted endpoints only. A package has no live endpoint of its own for us to probe.
  • Transport & ReachabilityScored on hosted endpoints only. A package has no live endpoint of its own for us to probe.

The score does not measure everything. What the score does not measure →

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.

  • 19 Nov 26 0
    • Stability: 0.97 → pass security
  • 18 Nov 26 0
    • Stability: pass → 0.97 functional
  • 12 Nov 26 0
    • Stability: 0.97 → pass security
  • 11 Nov 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 93 to 97. That category is still filling its 30-day observation window: 28 days of observed history at the previous scan, 29 at this one. The score rises as the window fills, whether or not the server changes.

  • 9 Nov 26 +4
    • Source repository: unverified → pass ▲ security
    • Stability: pass → 0.90 functional
  • 8 Nov 26 −5
    • Provenance: pass → unverified ▼ security
  • 4 Nov 26 0
    • Security disclosure: unverified → fail ▼ functional
  • 3 Nov 26 0
    • Stability: 0.97 → pass security
    • Security disclosure: fail → unverified ▼ functional
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 21 Nov 2026 · Analysed npm/mcp-roadmapsh@0.2.0

Provenance No attestation

The registry publishes no build provenance for this version, so there is nothing to verify.

Result No attestation
Ecosystem npm

Background: How many MCP packages publish verified provenance →

Vulnerabilities 1 finding
ID CVE Severity Vector Fix available
GHSA-mrhx-c7xc-m3w5 CVE-2023-54404 high CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H yes

Background: What a vulnerability scan can and cannot prove →

Dependencies 93 packages
Packages resolved 93
Stale 31
Tree resolution Complete

Background: SBOMs and build attestations, explained →

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. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →

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
formatstring–Output format: markdown (default) or plain text for LLM ingestion
includeContentboolean–Fetch each topic's markdown; false returns structure only
maxTopicsinteger–Cap 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
nodeIdstring–Exact node id from the outline
querystring–Topic 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.

Install

How do I install the io.github.aissablk1/mcp-roadmapsh server?

io.github.aissablk1/mcp-roadmapsh runs locally as an npm package, launched with npx -y mcp-roadmapsh. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

npm · mcp-roadmapsh

# add to Claude Code
claude mcp add aissablk1-mcp-roadmapsh -- npx -y mcp-roadmapsh
Common questions

What is the io.github.aissablk1/mcp-roadmapsh server?

io.github.aissablk1/mcp-roadmapsh is listed in the public MCP registry as io.github.aissablk1/mcp-roadmapsh. MCP server for roadmap.sh: roadmaps, best practices, interview questions, projects & progress. This page covers its npm package (mcp-roadmapsh).

Is the io.github.aissablk1/mcp-roadmapsh server safe to use?

io.github.aissablk1/mcp-roadmapsh scores 78 out of 100 on VerifyMCP. We recorded 1 known advisory against it as of 21 November 2026. It declares no install or post-install scripts. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

What tools does the io.github.aissablk1/mcp-roadmapsh server expose?

io.github.aissablk1/mcp-roadmapsh exposes 16 tools: roadmap_diagnose, roadmap_list, roadmap_get, roadmap_topic, roadmap_search, and 11 more. Their descriptions and schemas cost roughly 663 tokens of context every time the server is loaded.

Is the io.github.aissablk1/mcp-roadmapsh server still maintained?

io.github.aissablk1/mcp-roadmapsh is still listed as active in the MCP registry. We last reached this channel on 21 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

What licence is the io.github.aissablk1/mcp-roadmapsh server under?

io.github.aissablk1/mcp-roadmapsh declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.

What did VerifyMCP test on the io.github.aissablk1/mcp-roadmapsh server?

VerifyMCP ran 16 checks on io.github.aissablk1/mcp-roadmapsh, covering Malware scan, Known CVEs, Install scripts, Dependency health and 12 more. Endpoint Security and Transport & Reachability do not apply to an npm package, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.