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.CloudCorpRecords/courseatlas

NPM · @RENETURCIOS/COURSEATLAS · 2 COMPONENTS

Search and read the free AI School curriculum: lessons, course tracks, full lesson text.

73 Trust /100

Last scanned (18 hours ago)

Scores higher than 46% 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 Security98
  • No malware found by supply-chain analysis.Pass
  • No known CVEs affecting this package version or its production dependencies.Pass
  • No install/post-install scripts declared.Pass
  • 31 of 92 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency45
Schema Quality & AI Usability81
  • AI-judged instruction clarity (excellent).Pass
  • Tool/resource definitions use about 287 tokens (~71/item across 4 items; 4 tools + 0 resources), lean.Pass
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management17
  • Stability observed for 5 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
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • We read all 4 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 4 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.

  • 21 Nov 26 +2
    • Stability: unverified → 0.17 ▲ functional
  • 16 Nov 26 71

    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 21 Nov 2026 · Analysed npm/@reneturcios/courseatlas@0.1.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 →

Dependencies 92 packages
Packages resolved 92
Stale 31
Tree resolution Complete

Background: SBOMs and build attestations, explained →

MCP tools · 4 exposed · ~287 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
get_track ~49

Get one track with its full lesson list, so you can see the structure of a course and pick the right lesson to read.

NameTypeReqDescription
slugstringyesTrack slug, e.g. "rag"

No output schema declared.

No examples provided.

list_tracks ~75

List AI School course tracks, optionally filtered by a substring of the title or slug. Each track is a structured course on one subject. Use this to find the right course before drilling into its lessons.

NameTypeReqDescription
filterstring–Optional substring filter
limitinteger–Max results (default 40, max 200)

No output schema declared.

No examples provided.

read_lesson ~56

Fetch the full text of a lesson by its URL (as returned by search_lessons or get_track). Returns readable markdown-ish text with headings and code blocks.

NameTypeReqDescription
urlstringyesLesson URL on lillytechsystems.com

No output schema declared.

No examples provided.

search_lessons ~107

Search the AI School curriculum (500+ tracks, thousands of free lessons on AI engineering, governance, security, and applied AI by profession). Returns matching lesson titles and URLs. Use this before answering an AI-topic question when a concrete, citable lesson would help, then read_lesson to get the text.

NameTypeReqDescription
limitinteger–Max results (default 10, max 50)
querystringyesWords to search for, e.g. "prompt injection defence"

No output schema declared.

No examples provided.

Install

How do I install the io.github.CloudCorpRecords/courseatlas MCP server?

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

npm · @reneturcios/courseatlas

# add to Claude Code
claude mcp add cloudcorprecords-courseatlas -- npx -y @reneturcios/courseatlas mcp
Common questions

What is the io.github.CloudCorpRecords/courseatlas MCP server?

io.github.CloudCorpRecords/courseatlas is an MCP server listed in the public MCP registry as io.github.CloudCorpRecords/courseatlas. Search and read the free AI School curriculum: lessons, course tracks, full lesson text. This page covers its npm package (@reneturcios/courseatlas).

Is the io.github.CloudCorpRecords/courseatlas MCP server safe to use?

io.github.CloudCorpRecords/courseatlas scores 73 out of 100 on VerifyMCP. We found no known CVEs affecting 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.CloudCorpRecords/courseatlas MCP server expose?

io.github.CloudCorpRecords/courseatlas exposes 4 tools: search_lessons, list_tracks, get_track, read_lesson. Their descriptions and schemas cost roughly 287 tokens of context every time the server is loaded.

Is the io.github.CloudCorpRecords/courseatlas MCP server still maintained?

io.github.CloudCorpRecords/courseatlas 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.CloudCorpRecords/courseatlas MCP server under?

io.github.CloudCorpRecords/courseatlas 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.CloudCorpRecords/courseatlas MCP server?

VerifyMCP ran 16 checks on io.github.CloudCorpRecords/courseatlas, 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.