io.github.aissablk1/mcp-roadmapsh

MCPcommunity
v0.2.0io.github.aissablk1UnknownUpdated 4mo agonpmGitHub

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

MCP server for roadmap.sh — developer roadmaps, best practices, interview questions, project ideas, videos, and local progress tracking. Built on the official (TypeScript / stdio). All data comes from official, public sources — no scraping, no mock data: — rendered roadmap graphs GitHub contents API — dynamic slug listings Node.js 20 or newer ( to check). That is the only requirement — (bundled…

Works in
ClaudeCursorCopilotGemini

Inferred from the transports this listing declares (stdio). A client not listed here hasn’t been ruled out — it just isn’t something Forge can confirm.

Automatically indexed from public sources. Not yet verified by the developer on Forge.Claim this listing →
2GitHub stars
4mo agoLast update
Package
Authorio.github.aissablk1
LicenseUnknown
Version0.2.0
Sourcemcp-registry
Trust Status
B
60/100Good
✓Listed in Forge index+10/10
—Publisher identity verified+0/20
→ Publisher: run `forge publish` from the package repo to claim ownership
—Ed25519 publish signature+0/5
→ Included automatically when the publisher runs `forge publish`
—Domain verification+0/5
→ Publisher: host /.well-known/forge.json on the package homepage with { "publisher": "<github-login>" }
—npm Trusted Publishing (Sigstore)+0/5
→ Publish from GitHub Actions with --provenance so the attestation binds this package to this repo
—npm maintainer match+0/5
→ Earned once your identity is verified above and that login is an npm maintainer of this package
✓CVE scan · clean+30/30
✓Static analysis · clean+20/20
Paste into Claude Code, Cursor, or any AI assistant to fix all gaps
StatusCommunity-indexed
PublisherUnverified
SignatureUnsigned
Domain—
Provenance—
Dependencies✓ 60 resolved+ · none vulnerable
Tool surface1 tool · none privileged
Security scan✓ Cleanv0.2.0 · 3mo agoHow well does this scan work?
EvalsNone
IndexedJun 13, 2026

Verification confirms publisher identity (repo ownership), not code safety. The security scan covers known CVEs and suspicious install scripts.

Tools

1 tool · none privileged
Statically extracted from the published packagev0.2.0 · 3mo ago

Read out of the source npm actually ships, at scan time. The package was never executed. Tools registered dynamically at runtime, or hidden inside bundled or minified code, can be missed — so this is a floor on the tool surface, not a complete census of it.

progress_markNo description published

This tool published no description. Forge does not invent one.

0 of 1 tools published a description.

Tool names and descriptions are written by the publisher and shown verbatim as inert text. They are the strings an MCP client passes to a model, so Forge scans them for prompt-injection patterns — any finding appears with the security scan above. “Privileged” is a keyword match on the tool name, not an audit of what the tool does: a benign-sounding name can still do anything.

About

MCP server for roadmap.sh — developer roadmaps, best practices, interview questions, project ideas, videos, and local progress tracking. Built on the official (TypeScript / stdio). All data comes from official, public sources — no scraping, no mock data: — rendered roadmap graphs GitHub contents API — dynamic slug listings Node.js 20 or newer ( to check). That is the only requirement — (bundled with Node) handles the rest, no manual clone or build needed. Replace with to run the latest GitHub…

Keywords
mcp
Alternatives
Comparing tool surfaces…

No dependency coverage

This package was last scanned before Forge began storing the resolved tree. The next scan will record it.