io.github.qwertymuzaffar/udacity-commit
NPM · MCP-UDACITY-COMMIT
Validate & format git commit messages per the Udacity Git Commit Message Style Guide.
Available components
Last scanned (18 hours ago)
Scores higher than 66% of npm servers
Category Version Control
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 Security81
- No malware found by supply-chain analysis.Pass
- CVE check failed: a known high-severity CVE affects zod 3.25.76, a direct dependency. A fixed version is available. View diagnostics → Fail
- No install/post-install scripts declared.Pass
- 30 of 93 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency45
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Provenance check failed: no build-provenance attestation is published. See how to fix → View diagnostics → Fail
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 54 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability84
- 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
- AI-judged instruction clarity (good).Pass
- Tool/resource definitions use about 275 tokens (~55/item across 5 items; 3 tools + 2 resources), lean.Pass
- 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 Coverage95
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 83% of tool parameters carry a description.Partial
- 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 3 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
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.
- 4 Nov 26 0
- Security disclosure: unverified → fail ▼ functional
- 3 Nov 26 0
- Stability: 0.97 → pass security
- Security disclosure: fail → unverified ▼ functional
- 2 Nov 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.
- 1 Nov 26 −1
- Stability: pass → 0.93 functional
- 28 Oct 26 0
- Security disclosure: unverified → fail ▼ functional
- 27 Oct 26 0
- Security disclosure: fail → unverified ▼ functional
- 24 Oct 26 −5
- CVE-2023-54404 affects this package: high ▼ security
- Known CVEs: pass → fail ▼ security
- 20 Oct 26 0
- Stability: 0.97 → pass security
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/mcp-udacity-commit@1.2.2
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 →
Vulnerabilities 1 finding
| ID | CVE | Severity | Vector | Fix available |
|---|---|---|---|---|
| GHSA-mrhx-c7xc-m3w5 | CVE-2023-54404 | high | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H | yes |
Background: What a vulnerability scan can and cannot prove →
Dependencies 93 packages
| Packages resolved | 93 |
|---|---|
| Stale | 30 |
| 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 →
format_commit_message Format a Udacity-style commit message ~103
Compose a compliant commit message from its parts. The subject is capitalized, a trailing period is removed, and the body is wrapped at 72 characters.
| Name | Type | Req | Description |
|---|---|---|---|
| body | string | – | What & why; auto-wrapped at 72 chars |
| footer | string | – | Issue refs, e.g. "Resolves: #123" |
| subject | string | yes | Imperative subject; auto-capitalized, trailing period removed |
| type | string | yes | – |
| Name | Type | Req | Description |
|---|---|---|---|
| message | string | yes | – |
| problems | array | yes | – |
| valid | boolean | yes | – |
| warnings | array | yes | – |
No examples provided.
validate_branch_name Validate a git branch name ~79
Check a git branch name against the companion type/kebab-case convention (e.g. "feat/add-dark-mode"). Returns whether it is compliant plus any problems (violations) and warnings (hints). Base branches like main/master are exempt.
| Name | Type | Req | Description |
|---|---|---|---|
| name | string | yes | The branch name to check, e.g. "feat/add-dark-mode" |
| Name | Type | Req | Description |
|---|---|---|---|
| problems | array | yes | – |
| valid | boolean | yes | – |
| warnings | array | yes | – |
No examples provided.
validate_commit_message Validate a commit message ~54
Check a commit message against the Udacity Git Commit Message Style Guide. Returns whether it is compliant plus any problems (violations) and warnings (hints).
| Name | Type | Req | Description |
|---|---|---|---|
| message | string | yes | The full commit message to check |
| Name | Type | Req | Description |
|---|---|---|---|
| problems | array | yes | – |
| valid | boolean | yes | – |
| warnings | array | yes | – |
No examples provided.
How do I install the io.github.qwertymuzaffar/udacity-commit MCP server?
io.github.qwertymuzaffar/udacity-commit runs locally as an npm package, launched with npx -y mcp-udacity-commit. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
npm · mcp-udacity-commit
claude mcp add qwertymuzaffar-udacity-commit -- npx -y mcp-udacity-commit
What is the io.github.qwertymuzaffar/udacity-commit MCP server?
io.github.qwertymuzaffar/udacity-commit is an MCP server listed in the public MCP registry as io.github.qwertymuzaffar/udacity-commit. Validate & format git commit messages per the Udacity Git Commit Message Style Guide. This page covers its npm package (mcp-udacity-commit).
Is the io.github.qwertymuzaffar/udacity-commit MCP server safe to use?
io.github.qwertymuzaffar/udacity-commit scores 80 out of 100 on VerifyMCP. We recorded 1 known advisory against it as of 4 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.qwertymuzaffar/udacity-commit MCP server expose?
io.github.qwertymuzaffar/udacity-commit exposes 3 tools: validate_commit_message, format_commit_message, validate_branch_name. Their descriptions and schemas cost roughly 236 tokens of context every time the server is loaded.
Is the io.github.qwertymuzaffar/udacity-commit MCP server still maintained?
io.github.qwertymuzaffar/udacity-commit 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.qwertymuzaffar/udacity-commit MCP server under?
io.github.qwertymuzaffar/udacity-commit declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.