Skip to content

Upgrade Brief MCP server

dev.workers.shopttyass-85f.upgrade-brief/upgrade-briefupgrade-brief.shopttyass-85f.workers.devstreamable-httpv0.5.0Scanned

Breaking changes between two versions: npm, PyPI, GitHub Actions, Helm, Terraform, crates.io, Go.

12 tools: 9 do something that can't be undone and 3 change things.

Tools: 0 delete, 9 irreversible, 3 write, 0 read.
  • Reads private data · 0
  • Reads text others write · 12
  • Can send data out · 9
  • 9 findings

Tools listed without sign-in. Remote posture

With Anlyon

9 tools here do something that can't be undone. Govern them.

  • 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 Upgrade Brief MCP server can do

The Upgrade Brief MCP server is published by upgrade-brief.shopttyass-85f.workers.dev, a domain the MCP Registry verified. It has 12 tools. It can do things that cannot be undone, such as sending, paying or publishing (npm_breaking_changes, npm_changelog, pypi_breaking_changes, pypi_changelog and 5 more) and create or change data (3 tools: dependency_upgrade_plan, npm_versions and pypi_versions), but cannot delete data. None of its tools only reads.

12 tools bring in text other people can write (npm_breaking_changes, npm_changelog, pypi_breaking_changes and 9 more); 9 tools can send data out of your system (npm_breaking_changes, npm_changelog, pypi_breaking_changes and 6 more).

The fixed checks matched 9 findings (annotation-conflict). Each one comes with the text it matched.

Its remote endpoint lists its tools without sign-in, and its tools changed 2 times since Anlyon Radar first saw them.

Last scanned Nov 10, 2026, version 0.5.0.

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.

12 tools

Can't be undone 9Claude Code: ask
  • crates_breaking_changesRust crate upgrade brief between two versions: removed and changed Cargo features, default feature changes, dependency requirement diff, rust-version (MSRV) and edition changes, ya…Reads text others writeCan send data out1 finding

    Why it is in this group

    • The input addresses people (input.to): what it sends cannot be taken back.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
    • outboundThe input takes a destination (input.to): what the tool writes goes there.

    Findings

    • Warn

      The server marks "crates_breaking_changes" read-only (readOnlyHint: true), and its own name, description or input give the class "irreversible".

      Matched text

      annotations: {"readOnlyHint":true,"idempotentHint":true,"openWorldHint":true}; The input addresses people (input.to): what it sends cannot be taken back.

      What this check looks for
    Description, as the server wrote it
    Rust crate upgrade brief between two versions: removed and changed Cargo features, default feature changes, dependency requirement diff, rust-version (MSRV) and edition changes, yanked releases in the range, breaking items from GitHub releases and CHANGELOG, the Cargo.toml edit. Paid: $0.005 USDC per call via x402.

    Annotations the server declares

    • readOnlyHint: true
    • openWorldHint: true
    • idempotentHint: true
  • github_action_breaking_changesGitHub Actions upgrade brief between two versions of an action (e.g.Reads text others writeCan send data out1 finding

    Why it is in this group

    • The input addresses people (input.to): what it sends cannot be taken back.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
    • outboundThe input takes a destination (input.to): what the tool writes goes there.

    Findings

    • Warn

      The server marks "github_action_breaking_changes" read-only (readOnlyHint: true), and its own name, description or input give the class "irreversible".

      Matched text

      annotations: {"readOnlyHint":true,"idempotentHint":true,"openWorldHint":true}; The input addresses people (input.to): what it sends cannot be taken back.

      What this check looks for
    Description, as the server wrote it
    GitHub Actions upgrade brief between two versions of an action (e.g. actions/checkout v3 to v4): breaking changes from release notes and migration docs, action.yml input/output diff (removed, renamed, new required inputs, changed defaults), Node runtime change (node16/node20 removed, node24), deprecations, concrete workflow edits with SHA pin, and sources. Paid: $0.005 USDC per call via x402.

    Annotations the server declares

    • readOnlyHint: true
    • openWorldHint: true
    • idempotentHint: true
  • go_breaking_changesGo module upgrade brief between two versions: go.mod diff (go directive, requirements), major /vN import path change with the rewrite command, retracted and deprecated flags, break…Reads text others writeCan send data out1 finding

    Why it is in this group

    • The input addresses people (input.to): what it sends cannot be taken back.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
    • outboundThe input takes a destination (input.to): what the tool writes goes there.

    Findings

    • Warn

      The server marks "go_breaking_changes" read-only (readOnlyHint: true), and its own name, description or input give the class "irreversible".

      Matched text

      annotations: {"readOnlyHint":true,"idempotentHint":true,"openWorldHint":true}; The input addresses people (input.to): what it sends cannot be taken back.

      What this check looks for
    Description, as the server wrote it
    Go module upgrade brief between two versions: go.mod diff (go directive, requirements), major /vN import path change with the rewrite command, retracted and deprecated flags, breaking items from GitHub releases and CHANGELOG, the go get command. Paid: $0.005 USDC per call via x402.

    Annotations the server declares

    • readOnlyHint: true
    • openWorldHint: true
    • idempotentHint: true
  • helm_breaking_changesHelm chart upgrade brief between two chart versions: default values.yaml diff (removed, added, changed keys and possible renames), chart changelog and breaking items from Artifact …Reads text others writeCan send data out1 finding

    Why it is in this group

    • The input addresses people (input.to): what it sends cannot be taken back.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
    • outboundThe input takes a destination (input.to): what the tool writes goes there.

    Findings

    • Warn

      The server marks "helm_breaking_changes" read-only (readOnlyHint: true), and its own name, description or input give the class "irreversible".

      Matched text

      annotations: {"readOnlyHint":true,"idempotentHint":true,"openWorldHint":true}; The input addresses people (input.to): what it sends cannot be taken back.

      What this check looks for
    Description, as the server wrote it
    Helm chart upgrade brief between two chart versions: default values.yaml diff (removed, added, changed keys and possible renames), chart changelog and breaking items from Artifact Hub and the chart repo, README upgrade sections, kubeVersion, subchart and appVersion changes, concrete edits for your values file, sources. Paid: $0.01 USDC per call via x402.

    Annotations the server declares

    • readOnlyHint: true
    • openWorldHint: true
    • idempotentHint: true
  • npm_breaking_changesnpm breaking changes between two versions of a package, read from its real CHANGELOG and GitHub release notes: documented breaking items per version, major bumps, Node.js engine / …Reads text others writeCan send data out1 finding

    Why it is in this group

    • The input addresses people (input.to): what it sends cannot be taken back.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
    • outboundThe input takes a destination (input.to): what the tool writes goes there.

    Findings

    • Warn

      The server marks "npm_breaking_changes" read-only (readOnlyHint: true), and its own name, description or input give the class "irreversible".

      Matched text

      annotations: {"readOnlyHint":true,"idempotentHint":true,"openWorldHint":true}; The input addresses people (input.to): what it sends cannot be taken back.

      What this check looks for
    Description, as the server wrote it
    npm breaking changes between two versions of a package, read from its real CHANGELOG and GitHub release notes: documented breaking items per version, major bumps, Node.js engine / ESM-CJS / peer dependency changes, migration guide links and a verdict. Paid: $0.005 USDC per call via x402.

    Annotations the server declares

    • readOnlyHint: true
    • openWorldHint: true
    • idempotentHint: true
  • npm_changelognpm changelog between two versions: full release notes of every version in the range (newest first), with dates, bump type, deprecations, extracted breaking changes and package.jso…Reads text others writeCan send data out1 finding

    Why it is in this group

    • The input addresses people (input.to): what it sends cannot be taken back.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
    • outboundThe input takes a destination (input.to): what the tool writes goes there.

    Findings

    • Warn

      The server marks "npm_changelog" read-only (readOnlyHint: true), and its own name, description or input give the class "irreversible".

      Matched text

      annotations: {"readOnlyHint":true,"idempotentHint":true,"openWorldHint":true}; The input addresses people (input.to): what it sends cannot be taken back.

      What this check looks for
    Description, as the server wrote it
    npm changelog between two versions: full release notes of every version in the range (newest first), with dates, bump type, deprecations, extracted breaking changes and package.json changes. Paid: $0.01 USDC per call via x402.

    Annotations the server declares

    • readOnlyHint: true
    • openWorldHint: true
    • idempotentHint: true
  • pypi_breaking_changesPyPI breaking changes between two versions of a Python package, from its CHANGELOG/HISTORY/CHANGES file and GitHub releases: breaking items per version, Requires-Python and depende…Reads text others writeCan send data out1 finding

    Why it is in this group

    • The input addresses people (input.to): what it sends cannot be taken back.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
    • outboundThe input takes a destination (input.to): what the tool writes goes there.

    Findings

    • Warn

      The server marks "pypi_breaking_changes" read-only (readOnlyHint: true), and its own name, description or input give the class "irreversible".

      Matched text

      annotations: {"readOnlyHint":true,"idempotentHint":true,"openWorldHint":true}; The input addresses people (input.to): what it sends cannot be taken back.

      What this check looks for
    Description, as the server wrote it
    PyPI breaking changes between two versions of a Python package, from its CHANGELOG/HISTORY/CHANGES file and GitHub releases: breaking items per version, Requires-Python and dependency changes, yanked versions, migration guide links and a verdict. Paid: $0.005 USDC per call via x402.

    Annotations the server declares

    • readOnlyHint: true
    • openWorldHint: true
    • idempotentHint: true
  • pypi_changelogPyPI changelog between two versions of a Python package: full release notes per version (newest first) with dates, bump type, yanked flags, extracted breaking changes and Requires-…Reads text others writeCan send data out1 finding

    Why it is in this group

    • The input addresses people (input.to): what it sends cannot be taken back.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
    • outboundThe input takes a destination (input.to): what the tool writes goes there.

    Findings

    • Warn

      The server marks "pypi_changelog" read-only (readOnlyHint: true), and its own name, description or input give the class "irreversible".

      Matched text

      annotations: {"readOnlyHint":true,"idempotentHint":true,"openWorldHint":true}; The input addresses people (input.to): what it sends cannot be taken back.

      What this check looks for
    Description, as the server wrote it
    PyPI changelog between two versions of a Python package: full release notes per version (newest first) with dates, bump type, yanked flags, extracted breaking changes and Requires-Python / dependency changes. Paid: $0.01 USDC per call via x402.

    Annotations the server declares

    • readOnlyHint: true
    • openWorldHint: true
    • idempotentHint: true
  • terraform_breaking_changesTerraform provider upgrade brief between two versions: BREAKING CHANGES and deprecations per release from the provider CHANGELOG and GitHub releases, the major upgrade guide headin…Reads text others writeCan send data out1 finding

    Why it is in this group

    • The input addresses people (input.to): what it sends cannot be taken back.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
    • outboundThe input takes a destination (input.to): what the tool writes goes there.

    Findings

    • Warn

      The server marks "terraform_breaking_changes" read-only (readOnlyHint: true), and its own name, description or input give the class "irreversible".

      Matched text

      annotations: {"readOnlyHint":true,"idempotentHint":true,"openWorldHint":true}; The input addresses people (input.to): what it sends cannot be taken back.

      What this check looks for
    Description, as the server wrote it
    Terraform provider upgrade brief between two versions: BREAKING CHANGES and deprecations per release from the provider CHANGELOG and GitHub releases, the major upgrade guide headings and items, plugin protocol change, the required_providers edit, sources. Paid: $0.01 USDC per call via x402.

    Annotations the server declares

    • readOnlyHint: true
    • openWorldHint: true
    • idempotentHint: true
Changes things 3Claude Code: ask
  • dependency_upgrade_planDependency upgrade plan for up to 5 npm or PyPI packages: per package the breaking changes to the target version, major bumps, engine/Python and peer dependency changes, migration …Reads text others writeNo findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
    Description, as the server wrote it
    Dependency upgrade plan for up to 5 npm or PyPI packages: per package the breaking changes to the target version, major bumps, engine/Python and peer dependency changes, migration guides and a risk score, ordered by risk, plus peer requirements between the listed packages. Paid: $0.02 USDC per call via x402.

    Annotations the server declares

    • readOnlyHint: true
    • openWorldHint: true
    • idempotentHint: true
  • npm_versionsFree: published versions of an npm package (newest first) with publish dates, bump type and deprecations, to pick valid from/to values.Reads text others writeNo findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
    Description, as the server wrote it
    Free: published versions of an npm package (newest first) with publish dates, bump type and deprecations, to pick valid from/to values.

    Annotations the server declares

    • readOnlyHint: true
    • openWorldHint: true
    • idempotentHint: true
  • pypi_versionsFree: published versions of a PyPI project (newest first, PEP 440 order) with publish dates and bump type.Reads text others writeNo findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
    Description, as the server wrote it
    Free: published versions of a PyPI project (newest first, PEP 440 order) with publish dates and bump type.

    Annotations the server declares

    • readOnlyHint: true
    • openWorldHint: true
    • idempotentHint: 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.

No private-data, untrusted-input, outbound path in this server alone: no tool is tagged private-data.

Reads private data0
Reads files, mail, messages, databases, secrets, calendars or repositories.

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.

Tools listed without sign-in

Looked at Nov 21, 2026, 19:24 UTC, unchanged since Oct 30, 2026. No credentials were sent and no tool was called. What is looked at.

Reachable
yes
HTTP status of an anonymous initialize
200
tools/list served without credentials
yes
Tools that change things, listed without credentials
12
Protocol version
2025-06-18
WWW-Authenticate on 401
not observed
resource_metadata in WWW-Authenticate
not observed
RFC 9728 protected resource metadata
not observed
Authorization servers
not observed
Legacy HTTP+SSE transport
no
Dynamic client registration
not observed
Client ID metadata documents
not observed
  • HighThe whole server

    The endpoint served tools/list without credentials, and the list has 12 tools that change things (9 irreversible, 3 write). Whether a call also works without credentials was not tested: tools are never called.

    Matched text

    https://upgrade-brief.shopttyass-85f.workers.dev/mcp: tools/list returned 12 tools to an anonymous client, including npm_breaking_changes (irreversible), npm_changelog (irreversible), pypi_breaking_changes (irreversible), pypi_changelog (irreversible), github_action_breaking_changes (irreversible) and 7 more

    What this check looks for

Posture changes

  1. Oct 30, 2026
    • Tools that change things, listed without credentials: 7 to 12

Findings

Matches of fixed checks, with the text they matched.

9 warn
  • The server marks "npm_breaking_changes" read-only (readOnlyHint: true), and its own name, description or input give the class "irreversible".

    Matched text

    annotations: {"readOnlyHint":true,"idempotentHint":true,"openWorldHint":true}; The input addresses people (input.to): what it sends cannot be taken back.

    What this check looks for
  • The server marks "npm_changelog" read-only (readOnlyHint: true), and its own name, description or input give the class "irreversible".

    Matched text

    annotations: {"readOnlyHint":true,"idempotentHint":true,"openWorldHint":true}; The input addresses people (input.to): what it sends cannot be taken back.

    What this check looks for
  • The server marks "pypi_breaking_changes" read-only (readOnlyHint: true), and its own name, description or input give the class "irreversible".

    Matched text

    annotations: {"readOnlyHint":true,"idempotentHint":true,"openWorldHint":true}; The input addresses people (input.to): what it sends cannot be taken back.

    What this check looks for
  • The server marks "pypi_changelog" read-only (readOnlyHint: true), and its own name, description or input give the class "irreversible".

    Matched text

    annotations: {"readOnlyHint":true,"idempotentHint":true,"openWorldHint":true}; The input addresses people (input.to): what it sends cannot be taken back.

    What this check looks for
  • The server marks "github_action_breaking_changes" read-only (readOnlyHint: true), and its own name, description or input give the class "irreversible".

    Matched text

    annotations: {"readOnlyHint":true,"idempotentHint":true,"openWorldHint":true}; The input addresses people (input.to): what it sends cannot be taken back.

    What this check looks for
  • The server marks "helm_breaking_changes" read-only (readOnlyHint: true), and its own name, description or input give the class "irreversible".

    Matched text

    annotations: {"readOnlyHint":true,"idempotentHint":true,"openWorldHint":true}; The input addresses people (input.to): what it sends cannot be taken back.

    What this check looks for
Show 3 more findings
  • The server marks "terraform_breaking_changes" read-only (readOnlyHint: true), and its own name, description or input give the class "irreversible".

    Matched text

    annotations: {"readOnlyHint":true,"idempotentHint":true,"openWorldHint":true}; The input addresses people (input.to): what it sends cannot be taken back.

    What this check looks for
  • The server marks "crates_breaking_changes" read-only (readOnlyHint: true), and its own name, description or input give the class "irreversible".

    Matched text

    annotations: {"readOnlyHint":true,"idempotentHint":true,"openWorldHint":true}; The input addresses people (input.to): what it sends cannot be taken back.

    What this check looks for
  • The server marks "go_breaking_changes" read-only (readOnlyHint: true), and its own name, description or input give the class "irreversible".

    Matched text

    annotations: {"readOnlyHint":true,"idempotentHint":true,"openWorldHint":true}; The input addresses people (input.to): what it sends cannot be taken back.

    What this check looks for

History

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

  1. PostureRemote posture changed. Tools that change things, listed without credentials: 7 -> 12.View diff
    • Tools that change things, listed without credentials: 7 to 12
  2. Tools4 added.+4 addedView diff
  3. Tools1 added, 4 changed.+1 added~4 changedView diff

Install

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

claude mcp add --transport http upgrade-brief https://upgrade-brief.shopttyass-85f.workers.dev/mcp
claude mcp add --transport http upgrade-brief https://upgrade-brief.shopttyass-85f.workers.dev/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": [],
    "ask": [
      "mcp__upgrade-brief__npm_breaking_changes",
      "mcp__upgrade-brief__npm_changelog",
      "mcp__upgrade-brief__pypi_breaking_changes",
      "mcp__upgrade-brief__pypi_changelog",
      "mcp__upgrade-brief__dependency_upgrade_plan",
      "mcp__upgrade-brief__github_action_breaking_changes",
      "mcp__upgrade-brief__helm_breaking_changes",
      "mcp__upgrade-brief__terraform_breaking_changes",
      "mcp__upgrade-brief__crates_breaking_changes",
      "mcp__upgrade-brief__go_breaking_changes",
      "mcp__upgrade-brief__npm_versions",
      "mcp__upgrade-brief__pypi_versions"
    ],
    "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 upgrade-brief. Review it before you use it.

Capability tags behind 12 rules
  • mcp__upgrade-brief__npm_breaking_changes untrusted-input, outbound
  • mcp__upgrade-brief__npm_changelog untrusted-input, outbound
  • mcp__upgrade-brief__pypi_breaking_changes untrusted-input, outbound
  • mcp__upgrade-brief__pypi_changelog untrusted-input, outbound
  • mcp__upgrade-brief__dependency_upgrade_plan untrusted-input
  • mcp__upgrade-brief__github_action_breaking_changes untrusted-input, outbound
  • mcp__upgrade-brief__helm_breaking_changes untrusted-input, outbound
  • mcp__upgrade-brief__terraform_breaking_changes untrusted-input, outbound
  • mcp__upgrade-brief__crates_breaking_changes untrusted-input, outbound
  • mcp__upgrade-brief__go_breaking_changes untrusted-input, outbound
  • mcp__upgrade-brief__npm_versions untrusted-input
  • mcp__upgrade-brief__pypi_versions untrusted-input

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/dev.workers.shopttyass-85f.upgrade-brief/upgrade-brief/verify?hash=a8ffde965dc85ecc7ad7102180e75cb734b48738568fe491982852a6420c5d44" | jq -e '.changed == false'

Pinned hash a8ffde965dc8, from Nov 10, 2026, 07:18 UTC.

Watch

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

https://radar.anlyon.com/servers/dev.workers.shopttyass-85f.upgrade-brief/upgrade-brief/changes.xml

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

Badge

Anlyon Radar badge for dev.workers.shopttyass-85f.upgrade-brief/upgrade-brief
[![Anlyon Radar](https://radar.anlyon.com/badge/dev.workers.shopttyass-85f.upgrade-brief/upgrade-brief.svg)](https://radar.anlyon.com/servers/dev.workers.shopttyass-85f.upgrade-brief/upgrade-brief)

Source: MCP Registry. Synced Oct 29, 2026, 00:17 UTC.

Upgrade Brief MCP server: questions and answers

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

Is the Upgrade Brief MCP server safe?

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

Can the Upgrade Brief MCP server delete data?

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

Can the Upgrade Brief MCP server do things that cannot be undone?

Yes. 9 tools can send, pay, publish or merge: npm_breaking_changes, npm_changelog, pypi_breaking_changes, pypi_changelog, github_action_breaking_changes, helm_breaking_changes and 3 more.

What tools does the Upgrade Brief MCP server have?

12 tools: 9 irreversible, 3 write. npm_breaking_changes, npm_changelog, pypi_breaking_changes, pypi_changelog, github_action_breaking_changes, helm_breaking_changes, terraform_breaking_changes, crates_breaking_changes and 4 more.

Does the Upgrade Brief MCP server need sign-in or OAuth?

Its remote endpoint listed its tools to an anonymous client, without sign-in.

Does the Upgrade Brief MCP server send data to outside services?

9 tools can carry data out (it sends, posts or publishes, or takes a recipient, channel or URL): npm_breaking_changes, npm_changelog, pypi_breaking_changes, pypi_changelog, github_action_breaking_changes, helm_breaking_changes and 3 more.

Has the Upgrade Brief MCP server changed its tools?

Yes, 2 times since Anlyon Radar started tracking it, most recently on Oct 29, 2026. Every change is on this page and in its Atom feed.