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/phonsteps

NPM · @RENETURCIOS/PHONSTEPS · 2 COMPONENTS

Structured phonics word lists: browse, filter by grade or pattern, placement basis and citations.

68 Trust /100

Last scanned (13 hours ago)

Scores higher than 39% 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
  • 30 of 92 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency45
Schema Quality & AI Usability71
  • AI-judged instruction clarity (good).Pass
  • Tool/resource definitions use about 604 tokens (~100/item across 6 items; 6 tools + 0 resources), lean.Pass
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management0
  • Stability not yet verified: not enough scan history yet (needs a 30-day window).Unverified
Tool Coverage87
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 62% 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 6 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 6 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

Unverified: 1 category

A category scored 0 because we could not verify it: a data source with nothing on this package, evidence we could not reach, or a check we could not run. We only credit what we can confirm.

What we tested

Checks we ran (15)

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

Checks we could not complete (1)

These are gaps on our side, not findings about this package. We only credit what we can confirm, so a category made up entirely of them scores 0.

  • Stability in Stability & Change Management (scores 0 for this)Stability not yet verified: not enough scan history yet (needs a 30-day window).

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.

  • 18 Nov 26 +15
    • Malware scan: unverified → pass ▲ security
  • 17 Nov 26 53

    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/phonsteps@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 30
Tree resolution Complete

Background: SBOMs and build attestations, explained →

MCP tools · 6 exposed · ~604 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
find_words ~109

Finds words in the lists that start with, end with or contain a letter pattern, for example 'sh', 'ck', '-ight' or 'ai'. Returns each match with its list, grade range and page. Case-insensitive.

NameTypeReqDescription
containsstring––
ends_withstring––
gradestring–Only English lists covering this grade.
languagestring––
limitinteger–Default 60.
starts_withstring––

No output schema declared.

No examples provided.

get_citation ~40

License (CC BY 4.0 for the compilation; the Dolch words are public domain), the citation text and the CSV and JSON download addresses.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

get_placement_basis ~58

Explains the source of each grade placement: Dolch's own grade levels (1936, public domain), the Common Core Foundational Skills item that names the skill, or a typical sequence when no standard names it. Includes the limits.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

get_word_list ~93

The full list: every word, its groups (for example -at, -an, -ap families), the grade range, the placement basis, the page URL and the license. Use an id from list_word_lists, e.g. short-a, kindergarten, sh.

NameTypeReqDescription
idstringyesList id, e.g. short-a, kindergarten, vowel-teams, or es:palabras-con-m

No output schema declared.

No examples provided.

get_words_for_grade ~141

Every different English word from the lists that cover a grade, deduplicated, with the lists each word comes from. Optional section filter (for example only sight words or only cvc). A grade is a typical guide, not a rule: programs and standards differ, and it is not an assessment of any child. English lists are placed by grade; lists in other languages follow each language's own curriculum and have no grade.

NameTypeReqDescription
gradestringyespre-k, kindergarten, grade-1, grade-2 or grade-3
limitinteger–Maximum words to return. Default 300.
sectionstring––

No output schema declared.

No examples provided.

list_word_lists ~163

Lists the available word lists with id, title, language, section, grade range, the source of the grade placement and word count. Filter by language, grade (English lists whose grade range includes it) or section. A grade is a typical guide, not a rule: programs and standards differ, and it is not an assessment of any child. English lists are placed by grade; lists in other languages follow each language's own curriculum and have no grade.

NameTypeReqDescription
gradestring–English lists that cover this grade.
languagestring–en, de, es, fr, nl or pt-br. Omit for all.
sectionstring–cvc, families, sight, digraphs, patterns or wordlist (other languages).

No output schema declared.

No examples provided.

Install

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

io.github.CloudCorpRecords/phonsteps runs locally as an npm package, launched with npx -y @reneturcios/phonsteps 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/phonsteps

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

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

io.github.CloudCorpRecords/phonsteps is an MCP server listed in the public MCP registry as io.github.CloudCorpRecords/phonsteps. Structured phonics word lists: browse, filter by grade or pattern, placement basis and citations. This page covers its npm package (@reneturcios/phonsteps).

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

io.github.CloudCorpRecords/phonsteps scores 68 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/phonsteps MCP server expose?

io.github.CloudCorpRecords/phonsteps exposes 6 tools: list_word_lists, get_word_list, get_words_for_grade, find_words, get_placement_basis, get_citation. Their descriptions and schemas cost roughly 604 tokens of context every time the server is loaded.

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

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

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

VerifyMCP ran 15 checks on io.github.CloudCorpRecords/phonsteps, covering Malware scan, Known CVEs, Install scripts, Dependency health and 11 more. One item could not be completed, a gap on our side rather than a finding about io.github.CloudCorpRecords/phonsteps: Stability. One category scores 0 for that reason, because we only credit what we can confirm. 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.