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.starter-series/create-starter

NPM · STARTER-SERIES

Scaffold Starter Series projects and check release, deployment, security, and agent instructions.

Available components

0 this week 95 Trust /100

Last scanned (21 hours ago)

Scores higher than 98% of npm servers

Category CI/CD and DevOps

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
  • 33 of 99 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency100
  • Source repository is publicly reachable at the declared URL. View diagnostics → Pass
  • Cryptographically verified build provenance (signed, bound to starter-series/create-starter). View diagnostics → Pass
  • Clear OSI-approved license (MIT).Pass
  • Actively maintained (last published 53 days ago).Pass
  • Publishes a security disclosure policy (SECURITY.md).Pass
Schema Quality & AI Usability78
  • AI-judged instruction clarity (excellent).Pass
  • Context-footprint check failed: tool/resource definitions use about 1081 tokens (~120/item across 9 items; 9 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
  • 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 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
  • Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • We read all 9 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 9 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
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.

  • 1 Nov 26 0
    • Stability: 0.97 → pass security
  • 31 Oct 26 0
    • Stability: pass → 0.97 functional
  • 25 Oct 26 0
    • Stability: 0.97 → pass security
  • 24 Oct 26 0
    • Stability: pass → 0.97 functional
  • 18 Oct 26 0
    • Stability: 0.97 → pass security
  • 17 Oct 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.

  • 14 Oct 26 +1

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

  • 12 Oct 26 −2
    • Stability: pass → 0.80 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 4 Nov 2026 · Analysed npm/starter-series@0.5.3

Provenance Verified

A signed build attestation was found and verified, binding this exact artifact to the source repository it claims to come from.

Result Verified
Ecosystem npm
Reason Verified
Discovered via Registry attestation endpoint
Source repo starter-series/create-starter
Certificate issuer https://token.actions.githubusercontent.com
Certificate SAN https://github.com/starter-series/create-starter/.github/workflows/publish.yml@refs/tags/v0.5.3
Rekor log index 2795154222
Predicate type SLSA build provenance https://slsa.dev/provenance/v1
Subject digest sha512:228168f8c66612c6cc579a7f9a0cf101c3f4cad3c7b4b9c7f8bfeccdfe10985b873cfafffe31dbd5a276b6f3db61ec7c224306dd3a87eb9ef23c4ba49

Background: How many MCP packages publish verified provenance →

Dependencies 99 packages
Packages resolved 99
Stale 33
Tree resolution Complete

Background: SBOMs and build attestations, explained →

MCP tools · 9 exposed · ~1,081 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
add_component ~279

Lift a starter's CI/CD layer into an EXISTING repo without re-scaffolding — the remediation half of the audit loop (audit_security/audit_release diagnose; this installs the missing files from the matching starter). Components: ci (.github/workflows/ci.yml), security (codeql.yml + SECURITY.md), dependabot (dependabot.yml + auto-merge), maintenance (stale + weekly health check), or all. DRY-RUN BY DEFAULT: returns a per-file plan (create / identical / skip-exists / overwrite) and writes nothing until dry_run is false. Existing-but-different files are skipped unless force — so the dry-run plan doubles as a drift report against the starter. Never touches app code or secrets-bearing CD workflows.

NameTypeReqDescription
componentstring–Which group to lift (default: all).
dry_runboolean–Preview only (default true). Set false to write the planned files.
forceboolean–Overwrite files that differ from the starter AND allow applying onto a dirty git tree. Default false.
pathstring–Path to the repo (default: the MCP server's cwd). Use the absolute path of the project the user is working in.
starterstring–Template id to lift from (see list_templates). Auto-detected from the repo when omitted.
NameTypeReqDescription
componentstringyes–
dryRunbooleanyes–
planarrayyes–
repoPathstringyes–
starterstringyes–
starterSourcestringyes–
warningsarrayyes–
writtenarrayyes–

No examples provided.

audit_cd ~110

Check whether the local repo's version has been published to its destination registries (npm, PyPI, Open VSX, VS Marketplace, AMO, GitHub Releases). Makes outbound HTTPS requests to public registry APIs; never mutates. Reports per-destination drift (in-sync / needs-publish / local-stale / not-found).

NameTypeReqDescription
pathstring–Path to the repo to audit (default: the MCP server's cwd). Use the absolute path of the project the user is working in.
NameTypeReqDescription
destinationsarrayyes–
localVersionstring|nullyes–
matchedStarterobjectyes–
overallobjectyes–
repoPathstringyes–
versionSource–yes–

No examples provided.

audit_instructions ~105

Check local instruction discovery, source topology, exact duplicates/overlap, owner decisions and previous-run delta. Read-only by default; update_state explicitly saves the baseline, never source instructions. No semantic or safety enforcement.

NameTypeReqDescription
pathstring–Path to the repo to audit (default: the MCP server's cwd). Use the absolute path of the project the user is working in.
update_stateboolean–Explicitly save the current instruction delta baseline; default false.
NameTypeReqDescription
duplicatesarrayyes–
filesarrayyes–
overallobjectyes–
repoPathstringyes–
reviewobjectyes–
riskSummariesarrayyes–
surfaceOverlapsarrayyes–
topologyobjectyes–

No examples provided.

audit_release ~90

Audit a local repo for release-readiness against the Starter Series quality bar. Detects matched starter, CHANGELOG drift vs merged PRs, version-bump status, and publish-workflow presence. Read-only; never mutates the repo.

NameTypeReqDescription
pathstring–Path to the repo to audit (default: the MCP server's cwd). Use the absolute path of the project the user is working in.
NameTypeReqDescription
changelogobjectyes–
matchedStarterobjectyes–
publishWorkflowobjectyes–
repoPathstringyes–
shipReadyobjectyes–
versionobjectyes–

No examples provided.

audit_security ~102

Audit a local repo for baseline security CI hygiene against the Starter Series quality bar: gitleaks, CodeQL, dependency audit, license check, --ignore-scripts, Dependabot, secret-scanning hints, claude-code-security-review Action, and claude-security-guidance.md. Read-only.

NameTypeReqDescription
pathstring–Path to the repo to audit (default: the MCP server's cwd). Use the absolute path of the project the user is working in.
NameTypeReqDescription
checksarrayyes–
ecosystemstringyes–
overallobjectyes–
repoPathstringyes–
summaryobjectyes–

No examples provided.

create_project ~106

Scaffold a new project from a Starter Series template

NameTypeReqDescription
descriptionstring–One-line project description
init_gitboolean–Initialize a fresh git repo after scaffold (default: true)
namestringyesProject name (alphanumeric start, '-' or '_' only)
output_dirstring–Output directory (defaults to ./<name>, relative to the MCP server's cwd)
templatestringyesTemplate ID (use list_templates to see options)
NameTypeReqDescription
filesExtractednumberyes–
filesReplacednumberyes–
gitInitializedbooleanyes–
pathstringyes–

No examples provided.

generate_launch_proof_report ~135

Run audit_release, audit_cd, audit_security, and audit_instructions together, then return a client-ready Markdown Launch Proof Report. Read-only by default; set write=true to write launch-proof-report.md or output_path inside the target repo.

NameTypeReqDescription
output_pathstring–Report file path. Relative paths are resolved inside the target repo. Ignored unless write=true.
pathstring–Path to the repo to audit (default: the MCP server's cwd). Use the absolute path of the project the user is working in.
writeboolean–Write the Markdown report to disk. Default false.
NameTypeReqDescription
blockersarrayyes–
gatesarrayyes–
generatedAtstringyes–
markdownstringyes–
outputPathstring|nullyes–
overallobjectyes–
repoPathstringyes–
warningsarrayyes–

No examples provided.

list_templates ~16

List all available Starter Series project templates

Input schema present but exposes no named parameters.

NameTypeReqDescription
templatesarrayyes–

No examples provided.

seed_security_guidance ~138

Generate a starter `claude-security-guidance.md` at the repo root, tailored to the detected Starter Series template. The file is consumed in-session by Anthropic's Claude Code Security Guidance Plugin (released 2026-05-26) as a guard while Claude writes code. Use `force: true` to overwrite an existing file.

NameTypeReqDescription
forceboolean–Overwrite an existing claude-security-guidance.md. Default false (returns status='exists' instead).
pathstring–Path to the repo (default: the MCP server's cwd). Use the absolute path of the project the user is working in.
NameTypeReqDescription
bytesWrittennumberyes–
filePathstringyes–
matchedStarterstring|nullyes–
relativePathstringyes–
repoPathstringyes–
statusstringyes–

No examples provided.

Install

How do I install the io.github.starter-series/create-starter MCP server?

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

npm · starter-series

# add to Claude Code
claude mcp add starter-series-create-starter -- npx -y starter-series
Common questions

What is the io.github.starter-series/create-starter MCP server?

io.github.starter-series/create-starter is an MCP server listed in the public MCP registry as io.github.starter-series/create-starter. Scaffold Starter Series projects and check release, deployment, security, and agent instructions. This page covers its npm package (starter-series).

Is the io.github.starter-series/create-starter MCP server safe to use?

io.github.starter-series/create-starter scores 95 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 4 November 2026. It declares no install or post-install scripts. Its build provenance is signed and verified. 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.starter-series/create-starter MCP server expose?

io.github.starter-series/create-starter exposes 9 tools: list_templates, create_project, audit_release, audit_cd, audit_security, and 4 more. Their descriptions and schemas cost roughly 1,081 tokens of context every time the server is loaded.

Is the io.github.starter-series/create-starter MCP server still maintained?

io.github.starter-series/create-starter is still listed as active in the MCP registry. We last reached this channel on 4 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.starter-series/create-starter MCP server under?

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