io.github.muba00/gitstandup
NPM · GITSTANDUP-MCP
Generate daily standup notes from git commits across multiple repositories with AI summaries.
Available components
Last scanned (1 hour ago)
Scores higher than 0% of npm servers
Category Version Control
Recent critical change
CVE-2026-102828 affects this package (11 Oct 2026). See the changelog before you install this server.
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 Security73
- No malware found by supply-chain analysis.Pass
- CVE check failed: an unpatched critical CVE affects this package; the score is capped at 0. See how to fix → View diagnostics → Fail
- No install/post-install scripts declared.Pass
- 32 of 98 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency44
- 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 275 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability79
- AI-judged instruction clarity (excellent).Pass
- Tool/resource definitions use about 122 tokens (~30/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 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 Safety75
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- 0 of 1 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation; "remove_repos" implies "remove" and declares no destructiveHint at all, which the MCP spec reads as destructive by default. See how to fix → Fail
- 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.
- 3 Nov 26 0
- Stability: 0.97 → pass security
- 2 Nov 26 0
- Stability: pass → 0.97 functional
- 27 Oct 26 0
- Stability: 0.97 → pass security
- 26 Oct 26 0
- Stability: pass → 0.97 functional
- 20 Oct 26 0
- Stability: 0.97 → pass security
- 19 Oct 26 0
- Stability: pass → 0.97 functional
- 17 Oct 26 0
- Stability: 0.87 → pass security
- 14 Oct 26 0
- Stability: pass → 0.80 functional
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 5 Nov 2026 · Analysed npm/gitstandup-mcp@1.0.6
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 5 findings
| ID | CVE | Severity | Vector | Fix available |
|---|---|---|---|---|
| GHSA-v5rq-49vh-5v5c | CVE-2026-102829 | critical | yes | |
| GHSA-858h-whjf-mvg5 | CVE-2026-102827 | high | CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H | yes |
| GHSA-g4wm-2vf7-vfgr | CVE-2026-102826 | high | CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H | yes |
| GHSA-x6jw-m9v5-85vh | CVE-2026-102828 | critical | yes | |
| 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 98 packages
| Packages resolved | 98 |
|---|---|
| Stale | 32 |
| 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_repos Add Repositories ~28
Add repository paths to the configuration
| Name | Type | Req | Description |
|---|---|---|---|
| paths | array | yes | Absolute paths to git repositories |
| Name | Type | Req | Description |
|---|---|---|---|
| added | array | yes | – |
| repos | array | yes | – |
No examples provided.
generate_standup Generate Standup Notes ~53
Generate standup notes from git commits in configured repositories
| Name | Type | Req | Description |
|---|---|---|---|
| hours | number | – | Hours to look back (default: 24) |
| repos | array | – | Specific repo paths to use instead of configured ones |
| Name | Type | Req | Description |
|---|---|---|---|
| repos | array | yes | – |
| summary | object | yes | – |
No examples provided.
list_repos List Repositories ~14
List currently configured repositories
Input schema present but exposes no named parameters.
| Name | Type | Req | Description |
|---|---|---|---|
| count | number | yes | – |
| repos | array | yes | – |
No examples provided.
remove_repos Remove Repositories ~27
Remove repository paths from the configuration
| Name | Type | Req | Description |
|---|---|---|---|
| paths | array | yes | Repository paths to remove |
| Name | Type | Req | Description |
|---|---|---|---|
| removed | array | yes | – |
| repos | array | yes | – |
No examples provided.
How do I install the io.github.muba00/gitstandup MCP server?
io.github.muba00/gitstandup runs locally as an npm package, launched with npx -y gitstandup-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 · gitstandup-mcp
claude mcp add muba00-gitstandup -- npx -y gitstandup-mcp
What is the io.github.muba00/gitstandup MCP server?
io.github.muba00/gitstandup is an MCP server listed in the public MCP registry as io.github.muba00/gitstandup. Generate daily standup notes from git commits across multiple repositories with AI summaries. This page covers its npm package (gitstandup-mcp).
What tools does the io.github.muba00/gitstandup MCP server expose?
io.github.muba00/gitstandup exposes 4 tools: generate_standup, add_repos, list_repos, remove_repos. Their descriptions and schemas cost roughly 122 tokens of context every time the server is loaded.
Is the io.github.muba00/gitstandup MCP server still maintained?
io.github.muba00/gitstandup is still listed as active in the MCP registry. We last reached this channel on 5 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.muba00/gitstandup MCP server under?
io.github.muba00/gitstandup declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.