Standup from your activity
NPM · STANDUP-MCP
Generate your daily standup from real GitHub, Jira, Linear, and Slack activity.
Available components
Last scanned (21 hours ago)
Scores higher than 66% of npm servers
Category Productivity and Notes
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 139 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability82
- AI-judged instruction clarity (excellent).Pass
- Tool/resource definitions use about 514 tokens (~102/item across 5 items; 5 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
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 5 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 5 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
- 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
- 19 Oct 26 0
- Stability: pass → 0.97 functional
- 17 Oct 26 +2
- Stability: 0.87 → 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/standup-mcp@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 →
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 →
activity_digest Activity Digest ~108
A chronological digest of everything you did in a window across the configured tools, newest first, grouped by day. Use it to reconstruct what actually happened, separate from the opinionated standup framing.
| Name | Type | Req | Description |
|---|---|---|---|
| days | integer | – | Look back this many days from now instead of the default window. |
| since | string | – | ISO date/time start of the window, e.g. 2026-06-16. Overrides the default. Default covers the last working day (Monday reaches back to Friday). |
No output schema declared.
No examples provided.
blocker_scan Blocker Scan ~128
Surface what is blocking you across GitHub, Jira, Linear, and Slack, ranked by severity. Detects blockers from signals, not self-report: explicit 'blocked / waiting on / stuck' language, PRs awaiting review, in-progress tickets that have not moved, and requests for help.
| Name | Type | Req | Description |
|---|---|---|---|
| days | integer | – | Look back this many days from now instead of the default window. |
| since | string | – | ISO date/time start of the window, e.g. 2026-06-16. Overrides the default. Default covers the last working day (Monday reaches back to Friday). |
No output schema declared.
No examples provided.
list_sources List Sources ~52
Show which activity sources (GitHub, Jira, Linear, Slack) are configured, or that the server is running on demo data. Does not hit the network; run the server with --check to verify live connections.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
standup_draft Standup Draft ~149
Generate your daily standup, what should I say at standup today, from your real activity across the configured tools (GitHub, Jira, Linear, Slack). Returns Yesterday / Today / Blockers grouped by work item, not by tool, in concrete deltas. Defaults to the last working day (Monday reaches back across the weekend). Only reports observed activity; never invents work.
| Name | Type | Req | Description |
|---|---|---|---|
| days | integer | – | Look back this many days from now instead of the default window. |
| since | string | – | ISO date/time start of the window, e.g. 2026-06-16. Overrides the default. Default covers the last working day (Monday reaches back to Friday). |
No output schema declared.
No examples provided.
weekly_summary Weekly Summary ~77
Roll up a week (or any N days) of your real activity into accomplishments, grouped by work item as Shipped vs In progress, with reviews and totals. For 1:1s, weekly status, and self-reviews. Only reports observed work.
| Name | Type | Req | Description |
|---|---|---|---|
| days | integer | – | How many days to summarize. Default 7. |
No output schema declared.
No examples provided.
How do I install the Standup from your activity MCP server?
Standup from your activity runs locally as an npm package, launched with npx -y standup-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 · standup-mcp
claude mcp add sathvic-kollu-standup-mcp -- npx -y standup-mcp
What is the Standup from your activity MCP server?
Standup from your activity is an MCP server listed in the public MCP registry as io.github.sathvic-kollu/standup-mcp. Generate your daily standup from real GitHub, Jira, Linear, and Slack activity. This page covers its npm package (standup-mcp).
Is the Standup from your activity MCP server safe to use?
Standup from your activity 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 Standup from your activity MCP server expose?
Standup from your activity exposes 5 tools: standup_draft, blocker_scan, weekly_summary, activity_digest, list_sources. Their descriptions and schemas cost roughly 514 tokens of context every time the server is loaded.
Is the Standup from your activity MCP server still maintained?
Standup from your activity 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 Standup from your activity MCP server under?
Standup from your activity declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.