io.github.rimysore/standupbot
NPM · STANDUPBOT-MCP
Turns your GitHub activity into a daily standup — commits, PRs, reviews & issues.
Available components
Last scanned (1 hour ago)
Scores higher than 87% 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 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
- 30 of 92 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 130 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability80
- AI-judged instruction clarity (excellent).Pass
- Tool/resource definitions use about 295 tokens (~98/item across 3 items; 3 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 3 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 3 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.
- 5 Nov 26 +1
- Stability: 0.97 → pass security
- Security disclosure: unverified → fail ▼ functional
- 4 Nov 26 0
- Security disclosure: fail → unverified ▼ functional
- 3 Nov 26 −1
- Stability: pass → 0.93 functional
- 28 Oct 26 +1
- Stability: 0.97 → pass security
- 27 Oct 26 −1
- Stability: pass → 0.97 functional
- 21 Oct 26 +1
- Stability: 0.97 → pass security
- 20 Oct 26 −1
- Stability: pass → 0.97 functional
- 17 Oct 26 +3
- Stability: 0.83 → 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 5 Nov 2026 · Analysed npm/standupbot-mcp@1.0.1
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 →
Dependencies 92 packages
| Packages resolved | 92 |
|---|---|
| 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 →
get_repo_pulse ~93
Get recent activity (commits, PRs, issues) on a specific repository for the last N hours.
| Name | Type | Req | Description |
|---|---|---|---|
| github_token | string | yes | GitHub personal access token. |
| hours_back | integer | – | How many hours back to look. Default 24. |
| owner | string | yes | Repository owner, e.g. 'facebook' |
| repo | string | yes | Repository name, e.g. 'react' |
No output schema declared.
No examples provided.
get_standup ~107
Fetch your GitHub activity for the last N hours and format it as a standup report — commits, PRs opened/merged, reviews, and issues.
| Name | Type | Req | Description |
|---|---|---|---|
| github_token | string | – | GitHub personal access token. If omitted, uses the GITHUB_TOKEN env var set in MCP config. |
| hours_back | integer | – | How many hours back to look. Default 24. |
| username | string | yes | Your GitHub username, e.g. 'torvalds' |
No output schema declared.
No examples provided.
get_standup_multi ~95
Fetch GitHub activity for multiple users (e.g. your whole team) and return a combined standup report.
| Name | Type | Req | Description |
|---|---|---|---|
| github_token | string | yes | GitHub personal access token with read access to each user's events. |
| hours_back | integer | – | How many hours back to look. Default 24. |
| usernames | array | yes | List of GitHub usernames to include, e.g. ['alice', 'bob'] |
No output schema declared.
No examples provided.
How do I install the io.github.rimysore/standupbot MCP server?
io.github.rimysore/standupbot runs locally as an npm package, launched with npx -y standupbot-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 · standupbot-mcp
claude mcp add rimysore-standupbot -- npx -y standupbot-mcp
What is the io.github.rimysore/standupbot MCP server?
io.github.rimysore/standupbot is an MCP server listed in the public MCP registry as io.github.rimysore/standupbot. Turns your GitHub activity into a daily standup, commits, PRs, reviews & issues. This page covers its npm package (standupbot-mcp).
Is the io.github.rimysore/standupbot MCP server safe to use?
io.github.rimysore/standupbot scores 85 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 5 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.rimysore/standupbot MCP server expose?
io.github.rimysore/standupbot exposes 3 tools: get_standup, get_standup_multi, get_repo_pulse. Their descriptions and schemas cost roughly 295 tokens of context every time the server is loaded.
Is the io.github.rimysore/standupbot MCP server still maintained?
io.github.rimysore/standupbot 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.rimysore/standupbot MCP server under?
io.github.rimysore/standupbot declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.