# io.github.Jubstaaa/standup-mr (npm · standup-mr)

Standup notes from merge request state, with the failed job's error lines.

- Trust score: 78/100 (medium)
- Change this week: +3
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-09-20

## Components

- npm · `standup-mr`: 78/100 (this document), [markdown](https://verifymcp.io/servers/jubstaaa-standup-mr/standup-mr.md), [page](https://verifymcp.io/servers/jubstaaa-standup-mr/standup-mr)

## Channel facts

- Registry: `npm`
- Package: `standup-mr`
- Version: `0.6.1`
- Transport: `stdio`

## Trust breakdown

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. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-09-20.

- **Supply Chain Security**: 98/100
  - No malware found by supply-chain analysis.
  - No known CVEs affecting this package version or its production dependencies.
  - No install/post-install scripts declared.
  - 31 of 95 dependencies flagged as unhealthy.
- **Provenance & Transparency**: 48/100
  - Source repository is publicly reachable at the declared URL.
  - Provenance check failed: no build-provenance attestation is published.
  - Clear OSI-approved license (MIT).
  - Actively maintained (last published 17 days ago).
  - Publishes a security disclosure policy (SECURITY.md).
- **Schema Quality & AI Usability**: 68/100
  - AI-judged instruction clarity (excellent).
  - Context-footprint check failed: tool/resource definitions use about 789 tokens (~263/item across 3 items; 3 tools + 0 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 63/100
  - Stability observed for 19 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% of tool parameters carry a description.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 3 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 3 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.

## Install

### How do I install the io.github.Jubstaaa/standup-mr MCP server?

io.github.Jubstaaa/standup-mr runs locally as an npm package, launched with npx -y standup-mr. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

### Claude

```bash
claude mcp add jubstaaa-standup-mr -- npx -y standup-mr
```

### Cursor

```json
{
  "mcpServers": {
    "jubstaaa-standup-mr": {
      "command": "npx",
      "args": [
        "-y",
        "standup-mr"
      ]
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "jubstaaa-standup-mr": {
      "command": "npx",
      "args": [
        "-y",
        "standup-mr"
      ]
    }
  }
}
```

### Codex

```bash
codex mcp add jubstaaa-standup-mr -- npx -y standup-mr
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "jubstaaa-standup-mr": {
      "type": "local",
      "command": [
        "npx",
        "-y",
        "standup-mr"
      ],
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add jubstaaa-standup-mr --command npx --arg -y --arg standup-mr
```

### Hermes

```yaml
mcp_servers:
  jubstaaa-standup-mr:
    command: "npx"
    args: ["-y", "standup-mr"]
```

### Netclaw

```json
{
  "McpServers": {
    "jubstaaa-standup-mr": {
      "Transport": "stdio",
      "Command": "npx",
      "Arguments": [
        "-y",
        "standup-mr"
      ]
    }
  }
}
```

### Vellum

```bash
assistant mcp add jubstaaa-standup-mr -t stdio -c npx -a -y standup-mr
```

### Other

```json
{
  "mcpServers": {
    "jubstaaa-standup-mr": {
      "command": "npx",
      "args": [
        "-y",
        "standup-mr"
      ]
    }
  }
}
```

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-09-19 (score 78, +1)

No change was recorded against any check on this day. Stability & Change Management went from 57 to 60. That category is still filling its 30-day observation window: 17 days of observed history at the previous scan, 18 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-09-17 (score 77, +1)

No change was recorded against any check on this day. Stability & Change Management went from 50 to 53. That category is still filling its 30-day observation window: 15 days of observed history at the previous scan, 16 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-09-15 (score 76, +1)

No change was recorded against any check on this day. Stability & Change Management went from 43 to 47. That category is still filling its 30-day observation window: 13 days of observed history at the previous scan, 14 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-09-13 (score 75, +1)

No change was recorded against any check on this day. Stability & Change Management went from 37 to 40. That category is still filling its 30-day observation window: 11 days of observed history at the previous scan, 12 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-09-11 (score 74, +1)

No change was recorded against any check on this day. Stability & Change Management went from 30 to 33. That category is still filling its 30-day observation window: 9 days of observed history at the previous scan, 10 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-09-09 (score 73, +1)

No change was recorded against any check on this day. Stability & Change Management went from 23 to 27. That category is still filling its 30-day observation window: 7 days of observed history at the previous scan, 8 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-09-06 (score 72, +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.

### 2026-09-04 (score 71, +1)

No change was recorded against any check on this day. Stability & Change Management went from 7 to 10. That category is still filling its 30-day observation window: 2 days of observed history at the previous scan, 3 at this one. The score rises as the window fills, whether or not the server changes.

## MCP tools (3)

### `get_standup_data` (~426 tokens)

Collect merge-request-based standup data from GitLab or GitHub. Returns one JSON object: `today`, `previousDays[]` with the events of each, `todayEvents[]`, `myMrs[]` bucketed ready / blocked / draft / stale, `reviews[]` waiting on you, and `blockers[]` carrying the error lines read out of each failed pipeline job log.

Call it once at the start of a working day, to write a standup note. It is a snapshot, not a search API: it cannot fetch one named merge request, reach further back than the previous working day, or filter by project.

Read-only, and credentials never come from an argument — they come from the environment or a logged-in gh / glab session. A rejected token, a refused resource or a rate limit fails the call with the host's own message, after two retries on transient server errors. A blocker whose diagnosis could not be fetched is still returned, with `job: "unknown"`, so a red pipeline is never silently dropped.

Input parameters:

- `host` (string): Self-hosted host, without a scheme, e.g. gitlab.example.com or github.example.com. Required for GitLab, which has no default host; optional for GitHub, which defaults to github.com. A recognisable ho…
- `lang` (string): Language for the date labels inside the returned JSON: en (default) or tr. It relabels dates and nothing else — no field is translated, and the standup note itself is written by the caller, in whatev…
- `provider` (string): Which provider to read. Omit to auto-detect, in this order: a recognisable host, STANDUP_PROVIDER, a GITHUB_*/GITLAB_* environment pair, then whichever of the gh / glab CLIs is logged in. Pass it whe…

### `post_standup_note` (~268 tokens)

Posts a finished standup note to a chat webhook. This one has a side effect: it sends a message other people will see, so only call it on a note the user has agreed to send.

The webhook URL is read from STANDUP_WEBHOOK_URL, never from an argument — a webhook URL is a credential, since anyone holding it can post to the channel. Slack and Discord payload shapes are supported; the shape is inferred from the URL host, and `kind` is only needed for a proxied or self-hosted endpoint whose host gives nothing away — Mattermost and Rocket.Chat take the slack shape. A missing URL, an unrecognised host, or a webhook that rejects the message comes back as an error rather than a silent success.

Input parameters:

- `kind` (string): Which payload shape to send: slack and google-chat post {"text"}, discord posts {"content"}. Omit it — the shape is inferred from the webhook host. Pass it only when the host is not recognisable, e.g…
- `text` (string, required): The note to post, as the chat should render it. Slack and Discord both take Markdown, so send the written note rather than the raw JSON from get_standup_data.

### `get_note_instructions` (~95 tokens)

Returns the note-writing rules — the playbook for turning get_standup_data output into a standup note a person would actually say out loud: how to group the previous day by theme, how to derive today from open merge requests, and how to report a blocker from its job log. Read-only, no arguments, no network. Call it once before writing the first note; the rules do not change between calls.

## Diagnostics

Captured diagnostic sections: Provenance, Dependencies. The full working is on the page: https://verifymcp.io/servers/jubstaaa-standup-mr/standup-mr#diagnostics

## Score history

- 2026-09-20: 78
- 2026-09-19: 78
- 2026-09-18: 77
- 2026-09-17: 77
- 2026-09-16: 76
- 2026-09-15: 76
- 2026-09-14: 75
- 2026-09-13: 75
- 2026-09-12: 74
- 2026-09-11: 74
- 2026-09-10: 73
- 2026-09-09: 73
- 2026-09-08: 72
- 2026-09-07: 72
- 2026-09-06: 72
- 2026-09-05: 71
- 2026-09-04: 71
- 2026-09-03: 70
- 2026-09-02: 44
- 2026-09-01: 56

## Common questions

### What is the io.github.Jubstaaa/standup-mr MCP server?

io.github.Jubstaaa/standup-mr is an MCP server listed in the public MCP registry as io.github.Jubstaaa/standup-mr. Standup notes from merge request state, with the failed job's error lines. This page covers its npm package (standup-mr).

### Is the io.github.Jubstaaa/standup-mr MCP server safe to use?

io.github.Jubstaaa/standup-mr scores 78 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. 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.Jubstaaa/standup-mr MCP server expose?

io.github.Jubstaaa/standup-mr exposes 3 tools: get_standup_data, post_standup_note, get_note_instructions. Their descriptions and schemas cost roughly 789 tokens of context every time the server is loaded.

### Is the io.github.Jubstaaa/standup-mr MCP server still maintained?

io.github.Jubstaaa/standup-mr 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.Jubstaaa/standup-mr MCP server under?

io.github.Jubstaaa/standup-mr declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.

## Links

- npm package: https://www.npmjs.com/package/standup-mr
- Socket report: https://socket.dev/npm/package/standup-mr
- Repository: https://github.com/Jubstaaa/standup-mr
- Changelog RSS feed: https://verifymcp.io/servers/jubstaaa-standup-mr/standup-mr.xml
- Changelog JSON feed: https://verifymcp.io/servers/jubstaaa-standup-mr/standup-mr.json
- HTML version of this page: https://verifymcp.io/servers/jubstaaa-standup-mr/standup-mr