Skip to content

Standup Mr MCP server

io.github.Jubstaaa/standup-mrJubstaaastreamable-httpv1.1.3Scanned

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

3 tools: 1 change things and 2 only read.

Tools: 0 delete, 0 irreversible, 1 write, 2 read.
  • Reads private data · 1
  • Reads text others write · 2
  • Can send data out · 1
  • 1 finding

Sign-in required, OAuth metadata published. Remote posture

With Anlyon

1 tool here changes things. Govern it.

  • Anlyon lists the tools and adopts none.
  • Each tool you adopt gets approvals and receipts.
  • Your agent never holds the key.
Govern this server →

A tool your agent calls directly is not routed through Anlyon and is not governed by it. Anlyon Radar only lists and labels, and these labels are the same either way.

What the Standup Mr MCP server can do

The Standup Mr MCP server is published by the GitHub account Jubstaaa. It has 3 tools. It can create or change data (1 tool: post_standup_note), but cannot delete data. 2 tools only read.

1 tool reads private data (get_note_instructions); 2 tools bring in text other people can write (get_standup_data and post_standup_note); 1 tool can send data out of your system (post_standup_note). On its own it has all three parts of a prompt-injection exfiltration path: private data, text others write, and a way out.

The fixed checks matched 1 finding (credentials-mention). Each one comes with the text it matched.

Its remote endpoint asks for sign-in and publishes OAuth metadata.

Last scanned Nov 13, 2026, version 1.1.3.

Tools

Grouped by what each tool does, most consequential first. Open one for its reasons and full description; descriptions are the publisher's own words.

3 tools

Changes things 1Claude Code: ask
  • post_standup_notePosts a finished standup note to the chat webhook the user saved on the connect page (Slack, Discord or Google Chat).Reads text others writeCan send data outNo findings

    Why it is in this group

    • The name "post_standup_note" says "post": a word for a change.

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
    • outboundThe name "post_standup_note" says "post": it sends or publishes something to other people.
    Description, as the server wrote it
    Posts a finished standup note to the chat webhook the user saved on the connect page (Slack, Discord or Google Chat). 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 never an argument. If none is saved, the call fails and says how to add one.

    Annotations the server declares

    • readOnlyHint: false
    • destructiveHint: false
    • idempotentHint: false
    • openWorldHint: true
Only reads 2Show 2 read-only tools
  • get_note_instructionsReturns 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, …Reads private dataNo findings

    Why it is in this group

    • The name "get_note_instructions" says "get": a word for reading.

    What it can reach

    • private-dataThe name "get_note_instructions" says "get" and "note": it reads notes.
    • private-dataThe description's first sentence says "return" and "note": it reads notes.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
  • get_standup_dataCollect merge-request-based standup data from the GitLab or GitHub account the user linked to this connector.Reads text others write1 finding

    Why it is in this group

    • The name "get_standup_data" says "get": a word for reading.

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.

    Findings

    • Info

      The description mentions "Credentials".

      Matched text

      description: "...day, or filter by project. Read-only. Credentials come from the accounts linked on the co..."

      What this check looks for
    Description, as the server wrote it
    Collect merge-request-based standup data from the GitLab or GitHub account the user linked to this connector. Returns one JSON object: `today`, `previousDays[]` with the events of each, `todayEvents[]`, `myMrs[]` bucketed ready / blocked / draft / stale, `reviews[]` waiting on the user, 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. Credentials come from the accounts linked on the connect page, never from an argument. With one linked account no argument is needed; with several, pass `provider` or `host` — an ambiguous call fails and lists the linked accounts, so ask the user which one they mean. An expired login fails with a request to reconnect the connector.

    Annotations the server declares

    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: true

This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.

Exfil surface

Which tools read private data, which read text someone else can write, and which can send data out. One of each is a path a prompt injection can use.

2 paths in this server alone from private data, through text someone else wrote, to a way out. Denying 1 outbound tool breaks every one.

Reads private data1
Reads files, mail, messages, databases, secrets, calendars or repositories.
Reads text others write2
Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
Can send data out1
Can carry data to people or systems: it sends, posts or publishes, or takes a recipient, channel or URL.
deny to break every path
{
  "permissions": {
    "deny": [
      "mcp__standup-mr__post_standup_note"
    ]
  }
}

Other servers in the same agent add their own tools to these paths. Audit your whole setup to see them together.

Remote posture

What anyone on the internet sees at the remote endpoint: an anonymous initialize and tools/list, and the public OAuth metadata.

Sign-in required, OAuth metadata published

Looked at Nov 20, 2026, 18:58 UTC, unchanged since Oct 22, 2026. No credentials were sent and no tool was called. What is looked at.

Reachable
yes
HTTP status of an anonymous initialize
401
tools/list served without credentials
no
Tools that change things, listed without credentials
0
Protocol version
not observed
WWW-Authenticate on 401
yes
resource_metadata in WWW-Authenticate
https://standup.ilkerbalcilar.com/.well-known/oauth-protected-resource/mcp
RFC 9728 protected resource metadata
https://standup.ilkerbalcilar.com/.well-known/oauth-protected-resource/mcp
Authorization servers
https://standup.ilkerbalcilar.com/
Legacy HTTP+SSE transport
no
Dynamic client registration
yes
Client ID metadata documents
no

Findings

Matches of fixed checks, with the text they matched.

1 info

History

Changes to its tool definitions and to its remote endpoint, newest first.

No change seen yet. Its tools are rescanned every day, and a remote endpoint is looked at once a week.

Install

Pinned to version 1.1.3. Values in angle brackets are yours to fill in.

claude mcp add --transport http standup-mr https://standup.ilkerbalcilar.com/mcp
claude mcp add --transport http standup-mr https://standup.ilkerbalcilar.com/mcp

Run in a terminal.

Claude Code permissions

Allow the reads, ask before a change or a way out, deny the deletes. Paste into .claude/settings.json.

.claude/settings.json
{
  "permissions": {
    "allow": [
      "mcp__standup-mr__get_standup_data",
      "mcp__standup-mr__get_note_instructions"
    ],
    "ask": [
      "mcp__standup-mr__post_standup_note"
    ],
    "deny": []
  }
}

Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. A read that can send data out (it takes a URL, say) asks first too. It assumes the server is installed as standup-mr. Review it before you use it.

Capability tags behind 3 rules
  • mcp__standup-mr__get_standup_data untrusted-input
  • mcp__standup-mr__post_standup_note untrusted-input, outbound
  • mcp__standup-mr__get_note_instructions private-data

Pin

Keep the decision: fail CI when the tools change, follow every change, or show a badge.

Pin in CI

Fail a build when the tools you reviewed are not the tools the server serves today.

curl -s "https://radar.anlyon.com/api/v1/servers/io.github.Jubstaaa/standup-mr/verify?hash=c11d6852d96f2f3aaa5ddaa70944c5fb97913b005b9a3bfe00da5f19448a0fda" | jq -e '.changed == false'

Pinned hash c11d6852d96f, from Nov 13, 2026, 14:18 UTC.

Watch

Get told when its tools change: a new tool, a new description, a new class.

https://radar.anlyon.com/servers/io.github.Jubstaaa/standup-mr/changes.xml

An Atom feed. Works in any feed reader or Slack's RSS app.

Badge

Anlyon Radar badge for io.github.Jubstaaa/standup-mr
[![Anlyon Radar](https://radar.anlyon.com/badge/io.github.Jubstaaa/standup-mr.svg)](https://radar.anlyon.com/servers/io.github.Jubstaaa/standup-mr)

Source: MCP Registry · repository. Synced Nov 19, 2026, 23:17 UTC.

Standup Mr MCP server: questions and answers

Answered from the scan above, not from the publisher's description.

Is the Standup Mr MCP server safe?

No scan can promise that. What its definitions show: 3 tools, 1 of which can change, send or delete something, and 1 finding from fixed checks. Allow the reads, ask before each change, and deny the deletes; the permissions block on this page does that.

Can the Standup Mr MCP server delete data?

No tool is classed as destructive: going by their definitions, none of them deletes, cancels or revokes anything.

Can the Standup Mr MCP server do things that cannot be undone?

No tool is classed as irreversible: none of them sends, pays, publishes or merges, going by their definitions.

What tools does the Standup Mr MCP server have?

3 tools: 1 write, 2 read. post_standup_note, get_standup_data and get_note_instructions.

Does the Standup Mr MCP server need sign-in or OAuth?

Yes. Its remote endpoint answered 401 without credentials, and it publishes OAuth protected resource metadata (RFC 9728); its authorization server supports dynamic client registration.

Does the Standup Mr MCP server send data to outside services?

1 tool can carry data out (it sends, posts or publishes, or takes a recipient, channel or URL): post_standup_note.

Has the Standup Mr MCP server changed its tools?

Not since Anlyon Radar started tracking it. Last scanned Nov 13, 2026.