Upgrade Brief
REMOTE · UPGRADE-BRIEF.SHOPTTYASS-85F.WORKERS.DEV
Breaking changes between two versions: npm, PyPI, GitHub Actions, Helm, Terraform, crates.io, Go.
Available components
Last scanned (7 hours ago)
Scores higher than 57% of remote servers
Reachable. Last reached 5 Nov 2026.
Category Developer Tools
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. How we score → Why this is hard to score →
Endpoint Security63
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- No authorisation is required to call this server. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one. See how to fix → View diagnostics → Partial
- HTTPS enforcement could not be verified: the plaintext port answered with HTTP 405, which proves neither a plaintext path nor enforcement. View diagnostics → Unverified
- HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability62
- AI-judged instruction clarity (good).Pass
- 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. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management47
- Stability observed for 14 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
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 12 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 13 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
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.
- 2 Nov 26 +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.
- 31 Oct 26 +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.
- 29 Oct 26 +1
- The server rewrote its instructions, which are the text every model session reads security
- 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” functional
- 27 Oct 26 +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.
- 26 Oct 26 0
- The server rewrote its instructions, which are the text every model session reads security
- Schema quality: 1274 → 1529 ▼ functional
- Server version: 0.3.1 → 0.4.0 functional
- New tool “github_action_breaking_changes” functional
- 24 Oct 26 +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.
- 23 Oct 26 0
- Schema quality: 162 → 182 ▼ functional
- Stability: unverified → 0.03 ▲ functional
- Server version: 0.3.0 → 0.3.1 functional
- “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” cosmetic
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 · Probed https://upgrade-brief.shopttyass-85f.workers.dev/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=shopttyass-85f.workers.dev | CN=YE1,O=Let's Encrypt,C=US | 21 Oct 2026 | 19 Jan 2027 | ECDSA 256 | ECDSA-SHA384 | 53a1cc87193825426d166f950da7e8afa6e |
| SANs: *.shopttyass-85f.workers.dev, shopttyass-85f.workers.dev | ||||||
| CN=YE1,O=Let's Encrypt,C=US (CA) | CN=Root YE,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | ECDSA 384 | ECDSA-SHA384 | 5ddd70dd31f801c85c186a7a04b80afe |
| CN=Root YE,O=ISRG,C=US (CA) | CN=ISRG Root X2,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | ECDSA-SHA384 | 872165fc34b6e5fba8add5b3705fb53a |
| CN=ISRG Root X2,O=Internet Security Research Group,C=US (CA) | CN=ISRG Root X1,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | SHA256-RSA | 6c8f1dc727c7117f7baf853ac980f9cd |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of upgrade-brief.shopttyass-85f.workers.dev. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| dev. | present | 60074 | 8 | Verified |
| workers.dev. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 200 |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://upgrade-brief.shopttyass-85f.workers.dev/mcp | Verified | 200 | |
| http (plaintext) | http://upgrade-brief.shopttyass-85f.workers.dev/mcp | Inconclusive | 405 |
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 →
crates_breaking_changes crates breaking changes ~179
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.
| Name | Type | Req | Description |
|---|---|---|---|
| crate | string | yes | crates.io crate name, e.g. 'tokio', 'clap' |
| features | string | – | Optional comma-separated Cargo features you enable, to flag removed ones |
| from | string | yes | 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 |
No output schema declared.
No examples provided.
dependency_upgrade_plan dependency upgrade plan ~146
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.
| Name | Type | Req | Description |
|---|---|---|---|
| ecosystem | string | – | Registry of all listed packages (default npm) |
| packages | string | yes | 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' |
No output schema declared.
No examples provided.
github_action_breaking_changes github action breaking changes ~239
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.
| Name | Type | Req | Description |
|---|---|---|---|
| action | string | yes | GitHub Action as in 'uses:', owner/repo[/path], e.g. 'actions/checkout', 'github/codeql-action/init' |
| from | string | yes | 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 |
No output schema declared.
No examples provided.
go_breaking_changes go breaking changes ~166
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.
| Name | Type | Req | Description |
|---|---|---|---|
| from | string | yes | Version you use now: exact or a major/minor prefix meaning its newest release |
| module | string | yes | 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 |
No output schema declared.
No examples provided.
helm_breaking_changes helm breaking changes ~200
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.
| Name | Type | Req | Description |
|---|---|---|---|
| chart | string | yes | Artifact Hub <repository>/<chart>, e.g. 'bitnami/redis', 'ingress-nginx/ingress-nginx' |
| from | string | yes | 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 |
No output schema declared.
No examples provided.
npm_breaking_changes npm breaking changes ~202
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.
| Name | Type | Req | Description |
|---|---|---|---|
| from | string | yes | 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 | yes | 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 |
No output schema declared.
No examples provided.
npm_changelog npm changelog ~209
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.
| Name | Type | Req | Description |
|---|---|---|---|
| from | string | yes | 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 | yes | 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 |
No output schema declared.
No examples provided.
npm_versions npm versions ~91
Free: published versions of an npm package (newest first) with publish dates, bump type and deprecations, to pick valid from/to values.
| Name | Type | Req | Description |
|---|---|---|---|
| from | string | – | Optional: list only versions after this one |
| limit | integer | – | Max versions returned (default 50) |
| package | string | yes | npm package name, e.g. 'react', 'next', '@types/node' |
No output schema declared.
No examples provided.
pypi_breaking_changes pypi breaking changes ~206
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.
| Name | Type | Req | Description |
|---|---|---|---|
| from | string | yes | 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 | yes | 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 |
No output schema declared.
No examples provided.
pypi_changelog pypi changelog ~218
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.
| Name | Type | Req | Description |
|---|---|---|---|
| from | string | yes | 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 | yes | 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 |
No output schema declared.
No examples provided.
pypi_versions pypi versions ~92
Free: published versions of a PyPI project (newest first, PEP 440 order) with publish dates and bump type.
| Name | Type | Req | Description |
|---|---|---|---|
| from | string | – | Optional: list only versions after this one |
| limit | integer | – | Max versions returned (default 50) |
| package | string | yes | PyPI project name, e.g. 'pydantic', 'django', 'flask' |
No output schema declared.
No examples provided.
terraform_breaking_changes terraform breaking changes ~157
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.
| Name | Type | Req | Description |
|---|---|---|---|
| from | string | yes | Version you use now: exact or a major/minor prefix meaning its newest release |
| prereleases | boolean | – | Include prerelease versions |
| provider | string | yes | 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 |
No output schema declared.
No examples provided.
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.
remote · upgrade-brief.shopttyass-85f.workers.dev
claude mcp add --transport http dev-workers-shopttyass-85f-upgrade-brief-upgrade 'https://upgrade-brief.shopttyass-85f.workers.dev/mcp'
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.