# Upgrade Brief (remote · upgrade-brief.shopttyass-85f.workers.dev)

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

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

## Components

- remote · `upgrade-brief.shopttyass-85f.workers.dev`: 71/100 (this document), [markdown](https://verifymcp.io/servers/dev-workers-shopttyass-85f-upgrade-brief-upgrade-brief/upgrade-brief.md), [page](https://verifymcp.io/servers/dev-workers-shopttyass-85f-upgrade-brief-upgrade-brief/upgrade-brief)

## Channel facts

- Endpoint: `https://upgrade-brief.shopttyass-85f.workers.dev/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `0.5.0`

## Trust breakdown

How this component scores in each security and reliability category. Every signal is checked automatically against the live server, 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-11-05.

- **Endpoint Security**: 63/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - No authorisation is required to call this server. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one.
  - HTTPS enforcement could not be verified: the plaintext port answered with HTTP 405, which proves neither a plaintext path nor enforcement.
  - HSTS check failed: the Strict-Transport-Security header is absent.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 62/100
  - AI-judged instruction clarity (good).
  - Context-footprint check failed: tool/resource definitions use about 2266 tokens (~188/item across 12 items; 12 tools + 0 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 47/100
  - Stability observed for 14 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 12 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 13 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 Upgrade Brief MCP server?

Upgrade Brief is a hosted endpoint at https://upgrade-brief.shopttyass-85f.workers.dev/mcp, so there is nothing to install locally. 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 --transport http dev-workers-shopttyass-85f-upgrade-brief-upgrade 'https://upgrade-brief.shopttyass-85f.workers.dev/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "dev-workers-shopttyass-85f-upgrade-brief-upgrade": {
      "url": "https://upgrade-brief.shopttyass-85f.workers.dev/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "dev-workers-shopttyass-85f-upgrade-brief-upgrade": {
      "type": "http",
      "url": "https://upgrade-brief.shopttyass-85f.workers.dev/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.dev-workers-shopttyass-85f-upgrade-brief-upgrade]
url = "https://upgrade-brief.shopttyass-85f.workers.dev/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "dev-workers-shopttyass-85f-upgrade-brief-upgrade": {
      "type": "remote",
      "url": "https://upgrade-brief.shopttyass-85f.workers.dev/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add dev-workers-shopttyass-85f-upgrade-brief-upgrade --url 'https://upgrade-brief.shopttyass-85f.workers.dev/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  dev-workers-shopttyass-85f-upgrade-brief-upgrade:
    url: "https://upgrade-brief.shopttyass-85f.workers.dev/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "dev-workers-shopttyass-85f-upgrade-brief-upgrade": {
      "Transport": "http",
      "Url": "https://upgrade-brief.shopttyass-85f.workers.dev/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add dev-workers-shopttyass-85f-upgrade-brief-upgrade -t streamable-http -u 'https://upgrade-brief.shopttyass-85f.workers.dev/mcp'
```

### Other

```json
{
  "mcpServers": {
    "dev-workers-shopttyass-85f-upgrade-brief-upgrade": {
      "type": "http",
      "url": "https://upgrade-brief.shopttyass-85f.workers.dev/mcp"
    }
  }
}
```

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

## 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-11-05 (score 71, +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-11-02 (score 70, +1)

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

### 2026-10-31 (score 69, +1)

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

### 2026-10-29 (score 68, +1)

- [security] The server rewrote its instructions, which are the text every model session reads
- [functional regression] Schema quality: 1529 → 2266
- [functional] Server version: 0.4.0 → 0.5.0
- [functional] New tool “crates_breaking_changes”
- [functional] New tool “go_breaking_changes”
- [functional] New tool “helm_breaking_changes”
- [functional] New tool “terraform_breaking_changes”

### 2026-10-27 (score 67, +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-10-26 (score 66, 0)

- [security] The server rewrote its instructions, which are the text every model session reads
- [functional regression] Schema quality: 1274 → 1529
- [functional] Server version: 0.3.1 → 0.4.0
- [functional] New tool “github_action_breaking_changes”

### 2026-10-24 (score 66, +1)

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

### 2026-10-23 (score 65, 0)

- [functional regression] Schema quality: 162 → 182
- [functional improvement] Stability: unverified → 0.03
- [functional] Server version: 0.3.0 → 0.3.1
- [cosmetic] “npm_breaking_changes” reworded the description of “from”
- [cosmetic] “npm_breaking_changes” reworded the description of “to”
- [cosmetic] “npm_changelog” reworded the description of “from”
- [cosmetic] “npm_changelog” reworded the description of “to”
- [cosmetic] “pypi_breaking_changes” reworded the description of “from”
- [cosmetic] “pypi_breaking_changes” reworded the description of “to”
- [cosmetic] “pypi_changelog” reworded the description of “from”
- [cosmetic] “pypi_changelog” reworded the description of “to”

## MCP tools (12)

### `npm_breaking_changes` (~202 tokens)

npm breaking changes

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.

Input parameters:

- `from` (string, required): Version you are on now: exact ('18.3.1') or a major/minor prefix ('18', '4.21') meaning the newest release of that series
- `package` (string, required): npm package name, e.g. 'react', 'next', '@types/node'
- `prereleases` (boolean): Include alpha/beta/rc versions in the range
- `to` (string): Target version: exact, or a major/minor prefix ('19', '2.0') meaning the first release of that series (19.0.0). Default: latest stable

### `npm_changelog` (~209 tokens)

npm changelog

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.

Input parameters:

- `from` (string, required): Version you are on now: exact ('18.3.1') or a major/minor prefix ('18', '4.21') meaning the newest release of that series
- `maxVersions` (integer): Newest N versions to return notes for (default 30)
- `package` (string, required): npm package name, e.g. 'react', 'next', '@types/node'
- `prereleases` (boolean): Include alpha/beta/rc versions in the range
- `to` (string): Target version: exact, or a major/minor prefix ('19', '2.0') meaning the first release of that series (19.0.0). Default: latest stable

### `pypi_breaking_changes` (~206 tokens)

pypi breaking changes

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.

Input parameters:

- `from` (string, required): Version you are on now: exact ('18.3.1') or a major/minor prefix ('18', '4.21') meaning the newest release of that series
- `package` (string, required): PyPI project name, e.g. 'pydantic', 'django', 'flask'
- `prereleases` (boolean): Include alpha/beta/rc versions in the range
- `to` (string): Target version: exact, or a major/minor prefix ('19', '2.0') meaning the first release of that series (19.0.0). Default: latest stable

### `pypi_changelog` (~218 tokens)

pypi changelog

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.

Input parameters:

- `from` (string, required): Version you are on now: exact ('18.3.1') or a major/minor prefix ('18', '4.21') meaning the newest release of that series
- `maxVersions` (integer): Newest N versions to return notes for (default 30)
- `package` (string, required): PyPI project name, e.g. 'pydantic', 'django', 'flask'
- `prereleases` (boolean): Include alpha/beta/rc versions in the range
- `to` (string): Target version: exact, or a major/minor prefix ('19', '2.0') meaning the first release of that series (19.0.0). Default: latest stable

### `dependency_upgrade_plan` (~146 tokens)

dependency upgrade plan

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.

Input parameters:

- `ecosystem` (string): Registry of all listed packages (default npm)
- `packages` (string, required): Comma-separated name@from[:to], up to 5, e.g. 'react@18.3.1:19,react-dom@18.3.1:19,next@14.2.0:15'

### `github_action_breaking_changes` (~239 tokens)

github action breaking changes

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.

Input parameters:

- `action` (string, required): GitHub Action as in 'uses:', owner/repo[/path], e.g. 'actions/checkout', 'github/codeql-action/init'
- `from` (string, required): Ref used now: major tag ('v3'), exact tag ('v3.6.0') or pinned commit SHA
- `prereleases` (boolean): Include prerelease tags
- `to` (string): Target: major tag ('v4' = newest v4.x.y, what @v4 runs), exact tag, or latest (default)
- `with` (string): Optional comma-separated input names your step passes in with:, to flag removed/changed ones

### `helm_breaking_changes` (~200 tokens)

helm breaking changes

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.

Input parameters:

- `chart` (string, required): Artifact Hub <repository>/<chart>, e.g. 'bitnami/redis', 'ingress-nginx/ingress-nginx'
- `from` (string, required): Version you use now: exact or a major/minor prefix meaning its newest release
- `prereleases` (boolean): Include prerelease versions
- `to` (string): Target version: exact, or a major prefix meaning its first release. Default: latest
- `values` (string): Optional comma-separated value keys you override, to flag removed or changed ones

### `terraform_breaking_changes` (~157 tokens)

terraform breaking changes

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.

Input parameters:

- `from` (string, required): Version you use now: exact or a major/minor prefix meaning its newest release
- `prereleases` (boolean): Include prerelease versions
- `provider` (string, required): Provider <namespace>/<name> as in required_providers, e.g. 'hashicorp/aws'
- `to` (string): Target version: exact, or a major prefix meaning its first release. Default: latest

### `crates_breaking_changes` (~179 tokens)

crates breaking changes

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.

Input parameters:

- `crate` (string, required): crates.io crate name, e.g. 'tokio', 'clap'
- `features` (string): Optional comma-separated Cargo features you enable, to flag removed ones
- `from` (string, required): Version you use now: exact or a major/minor prefix meaning its newest release
- `prereleases` (boolean): Include prerelease versions
- `to` (string): Target version: exact, or a major prefix meaning its first release. Default: latest

### `go_breaking_changes` (~166 tokens)

go breaking changes

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.

Input parameters:

- `from` (string, required): Version you use now: exact or a major/minor prefix meaning its newest release
- `module` (string, required): Go module path, e.g. 'github.com/gin-gonic/gin' (add /v2.. for v2+ modules)
- `prereleases` (boolean): Include prerelease versions
- `to` (string): Target version: exact, or a major prefix meaning its first release. Default: latest

### `npm_versions` (~91 tokens)

npm versions

Free: published versions of an npm package (newest first) with publish dates, bump type and deprecations, to pick valid from/to values.

Input parameters:

- `from` (string): Optional: list only versions after this one
- `limit` (integer): Max versions returned (default 50)
- `package` (string, required): npm package name, e.g. 'react', 'next', '@types/node'

### `pypi_versions` (~92 tokens)

pypi versions

Free: published versions of a PyPI project (newest first, PEP 440 order) with publish dates and bump type.

Input parameters:

- `from` (string): Optional: list only versions after this one
- `limit` (integer): Max versions returned (default 50)
- `package` (string, required): PyPI project name, e.g. 'pydantic', 'django', 'flask'

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/dev-workers-shopttyass-85f-upgrade-brief-upgrade-brief/upgrade-brief#diagnostics

## Score history

- 2026-11-05: 71
- 2026-11-04: 70
- 2026-11-03: 70
- 2026-11-02: 70
- 2026-11-01: 69
- 2026-10-31: 69
- 2026-10-30: 68
- 2026-10-29: 68
- 2026-10-28: 67
- 2026-10-27: 67
- 2026-10-26: 66
- 2026-10-25: 66
- 2026-10-24: 66
- 2026-10-23: 65
- 2026-10-22: 65

## Common questions

### What is the Upgrade Brief MCP server?

Upgrade Brief is an MCP server listed in the public MCP registry as dev.workers.shopttyass-85f.upgrade-brief/upgrade-brief. Breaking changes between two versions: npm, PyPI, GitHub Actions, Helm, Terraform, crates.io, Go. This page covers its hosted endpoint (https://upgrade-brief.shopttyass-85f.workers.dev/mcp).

### Is the Upgrade Brief MCP server safe to use?

Upgrade Brief scores 71 out of 100 on VerifyMCP. 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 Upgrade Brief MCP server expose?

Upgrade Brief exposes 12 tools: npm_breaking_changes, npm_changelog, pypi_breaking_changes, pypi_changelog, dependency_upgrade_plan, and 7 more. Their descriptions and schemas cost roughly 2,105 tokens of context every time the server is loaded.

### Does the Upgrade Brief MCP server require authentication?

No. We connected to Upgrade Brief without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

### Is the Upgrade Brief MCP server still maintained?

Upgrade Brief 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.

## Links

- Remote endpoint: https://upgrade-brief.shopttyass-85f.workers.dev/mcp
- Website: https://upgrade-brief.shopttyass-85f.workers.dev/
- Changelog RSS feed: https://verifymcp.io/servers/dev-workers-shopttyass-85f-upgrade-brief-upgrade-brief/upgrade-brief.xml
- Changelog JSON feed: https://verifymcp.io/servers/dev-workers-shopttyass-85f-upgrade-brief-upgrade-brief/upgrade-brief.json
- HTML version of this page: https://verifymcp.io/servers/dev-workers-shopttyass-85f-upgrade-brief-upgrade-brief/upgrade-brief