io.github.starter-series/create-starter
NPM · STARTER-SERIES · SCANNED SEP 20
Scaffold Starter Series projects and check release, deployment, security, and agent instructions.
Available components
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
- 34 of 102 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 8 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 Management37
- Stability observed for 11 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
- 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
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
claude mcp add starter-series-create-starter -- npx -y starter-series
{
"mcpServers": {
"starter-series-create-starter": {
"command": "npx",
"args": [
"-y",
"starter-series"
]
}
}
} {
"servers": {
"starter-series-create-starter": {
"command": "npx",
"args": [
"-y",
"starter-series"
]
}
}
} codex mcp add starter-series-create-starter -- npx -y starter-series
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"starter-series-create-starter": {
"type": "local",
"command": [
"npx",
"-y",
"starter-series"
],
"enabled": true
}
}
} openclaw mcp add starter-series-create-starter --command npx --arg -y --arg starter-series
mcp_servers:
starter-series-create-starter:
command: "npx"
args: ["-y", "starter-series"] {
"McpServers": {
"starter-series-create-starter": {
"Transport": "stdio",
"Command": "npx",
"Arguments": [
"-y",
"starter-series"
]
}
}
} assistant mcp add starter-series-create-starter -t stdio -c npx -a -y starter-series
{
"mcpServers": {
"starter-series-create-starter": {
"command": "npx",
"args": [
"-y",
"starter-series"
]
}
}
} 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.
- 20 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 33 to 37. That category is still filling its 30-day observation window: 10 days of observed history at the previous scan, 11 at this one. The score rises as the window fills, whether or not the server changes.
- 18 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 27 to 30. That category is still filling its 30-day observation window: 8 days of observed history at the previous scan, 9 at this one. The score rises as the window fills, whether or not the server changes.
- 16 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 20 to 23. That category is still filling its 30-day observation window: 6 days of observed history at the previous scan, 7 at this one. The score rises as the window fills, whether or not the server changes.
- 14 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 13 to 17. That category is still filling its 30-day observation window: 4 days of observed history at the previous scan, 5 at this one. The score rises as the window fills, whether or not the server changes.
- 12 Sept 26 +16
- Malware scan: unverified → pass ▲ security
- 11 Sept 26 −14
- Malware scan: pass → unverified ▼ security
- Tool safety: pass → unverified ▼ security
- Stability: Stability not yet verified: we do not have a sandbox capture of the MCP schema this version of the package serves yet. security
- Capabilities: pass → unverified ▼ functional
- Tool coverage: 100 → unverified ▼ functional
- Stability: unverified → 0.07 ▲ functional
- First check of Schema quality: unverified functional
- Package version: 0.5.2 → 0.5.3 functional
- 10 Sept 26 +10
- Known CVEs: unverified → pass ▲ security
- Dependency health: unverified → 0.84 ▲ functional
- 9 Sept 26 71
First indexed and scored.
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 20 Sept 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 | https://slsa.dev/provenance/v1 |
| Subject digest | sha512:228168f8c66612c6cc579a7f9a0cf101c3f4cad3c7b4b9c7f8bfeccdfe10985b873cfafffe31dbd5a276b6f3db61ec7c224306dd3a87eb9ef23c4ba49 |
Background: How many MCP packages publish verified provenance →
Dependencies 102 packages
| Packages resolved | 102 |
|---|---|
| Stale | 34 |
| Tree resolution | Complete |
Background: SBOMs and build attestations, explained →
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 →
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.
| Name | Type | Req | Description |
|---|---|---|---|
| component | string | – | Which group to lift (default: all). |
| dry_run | boolean | – | Preview only (default true). Set false to write the planned files. |
| force | boolean | – | Overwrite files that differ from the starter AND allow applying onto a dirty git tree. Default false. |
| path | string | – | Path to the repo (default: the MCP server's cwd). Use the absolute path of the project the user is working in. |
| starter | string | – | Template id to lift from (see list_templates). Auto-detected from the repo when omitted. |
| Name | Type | Req | Description |
|---|---|---|---|
| component | string | yes | – |
| dryRun | boolean | yes | – |
| plan | array | yes | – |
| repoPath | string | yes | – |
| starter | string | yes | – |
| starterSource | string | yes | – |
| warnings | array | yes | – |
| written | array | yes | – |
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).
| Name | Type | Req | Description |
|---|---|---|---|
| path | string | – | Path to the repo to audit (default: the MCP server's cwd). Use the absolute path of the project the user is working in. |
| Name | Type | Req | Description |
|---|---|---|---|
| destinations | array | yes | – |
| localVersion | string|null | yes | – |
| matchedStarter | object | yes | – |
| overall | object | yes | – |
| repoPath | string | yes | – |
| 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.
| Name | Type | Req | Description |
|---|---|---|---|
| path | string | – | 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_state | boolean | – | Explicitly save the current instruction delta baseline; default false. |
| Name | Type | Req | Description |
|---|---|---|---|
| duplicates | array | yes | – |
| files | array | yes | – |
| overall | object | yes | – |
| repoPath | string | yes | – |
| review | object | yes | – |
| riskSummaries | array | yes | – |
| surfaceOverlaps | array | yes | – |
| topology | object | yes | – |
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.
| Name | Type | Req | Description |
|---|---|---|---|
| path | string | – | Path to the repo to audit (default: the MCP server's cwd). Use the absolute path of the project the user is working in. |
| Name | Type | Req | Description |
|---|---|---|---|
| changelog | object | yes | – |
| matchedStarter | object | yes | – |
| publishWorkflow | object | yes | – |
| repoPath | string | yes | – |
| shipReady | object | yes | – |
| version | object | yes | – |
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.
| Name | Type | Req | Description |
|---|---|---|---|
| path | string | – | Path to the repo to audit (default: the MCP server's cwd). Use the absolute path of the project the user is working in. |
| Name | Type | Req | Description |
|---|---|---|---|
| checks | array | yes | – |
| ecosystem | string | yes | – |
| overall | object | yes | – |
| repoPath | string | yes | – |
| summary | object | yes | – |
No examples provided.
create_project ~106
Scaffold a new project from a Starter Series template
| Name | Type | Req | Description |
|---|---|---|---|
| description | string | – | One-line project description |
| init_git | boolean | – | Initialize a fresh git repo after scaffold (default: true) |
| name | string | yes | Project name (alphanumeric start, '-' or '_' only) |
| output_dir | string | – | Output directory (defaults to ./<name>, relative to the MCP server's cwd) |
| template | string | yes | Template ID (use list_templates to see options) |
| Name | Type | Req | Description |
|---|---|---|---|
| filesExtracted | number | yes | – |
| filesReplaced | number | yes | – |
| gitInitialized | boolean | yes | – |
| path | string | yes | – |
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.
| Name | Type | Req | Description |
|---|---|---|---|
| output_path | string | – | Report file path. Relative paths are resolved inside the target repo. Ignored unless write=true. |
| path | string | – | Path to the repo to audit (default: the MCP server's cwd). Use the absolute path of the project the user is working in. |
| write | boolean | – | Write the Markdown report to disk. Default false. |
| Name | Type | Req | Description |
|---|---|---|---|
| blockers | array | yes | – |
| gates | array | yes | – |
| generatedAt | string | yes | – |
| markdown | string | yes | – |
| outputPath | string|null | yes | – |
| overall | object | yes | – |
| repoPath | string | yes | – |
| warnings | array | yes | – |
No examples provided.
list_templates ~16
List all available Starter Series project templates
Input schema present but exposes no named parameters.
| Name | Type | Req | Description |
|---|---|---|---|
| templates | array | yes | – |
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.
| Name | Type | Req | Description |
|---|---|---|---|
| force | boolean | – | Overwrite an existing claude-security-guidance.md. Default false (returns status='exists' instead). |
| path | string | – | Path to the repo (default: the MCP server's cwd). Use the absolute path of the project the user is working in. |
| Name | Type | Req | Description |
|---|---|---|---|
| bytesWritten | number | yes | – |
| filePath | string | yes | – |
| matchedStarter | string|null | yes | – |
| relativePath | string | yes | – |
| repoPath | string | yes | – |
| status | string | yes | – |
No examples provided.
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 87 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 20 September 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 20 September 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.