What's New
Server Details
Changelogs for apps, games and operating systems. Ask what shipped since the version you run.
- Status
- Healthy
- Uptime
- 100.0% over 37 days
- Last Tested
- Transport
- Streamable HTTP · MCP 2025-11-25
- URL
TDQS
Scored across 4 tools
Each tool targets a distinct operation: listing product metadata, searching across the catalog, retrieving version-to-version upgrade notes, and getting latest releases per product. Overlap is minimal and the descriptions make the boundaries clear.
list_products, search_releases, and upgrade_notes follow a verb_noun pattern, but whats_new breaks the pattern with a phrase. All names are snake_case and readable, so the inconsistency is minor.
Four tools are well-scoped for a specialized release-notes tracking server. Each tool covers a distinct aspect without redundancy, and the count is in the ideal range.
The surface covers the core user journeys: discovering products, searching releases, checking what's new, and assessing upgrade impact between versions. As a read-only aggregator, no CRUD operations are expected.
Available Tools
4 toolslist_productsList tracked productsARead-onlyIdempotentInspect
The products What's New tracks release notes for, with slugs, categories and platforms. Filter by category and/or a name query.
| Name | Required | Description | Default |
|---|---|---|---|
| sort | No | "popular" ranks by current audience popularity — outside signals (stars, downloads, players) blended with this site's own readers — and answers "what are the most popular software right now?". Default is the curated catalog order (or search relevance when query is set, which ignores sort). | |
| query | No | Filter by name, e.g. "terminal" or "jetbrains". | |
| category | No | Limit results to one product category. |
Output Schema
| Name | Required | Description |
|---|---|---|
| total | Yes | Matches before the cap. |
| products | Yes | |
| returned | Yes | |
| truncated | No |
TDQS
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already declare readOnlyHint=true and idempotentHint=true, so the safety profile is covered. The description adds the return shape and filter behavior, but sort semantics and result details are left to the schema and output schema. This is a modest addition, not a contradiction.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
Two concise sentences convey scope, returned fields, and filtering behavior with no filler. The most important information is front-loaded.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
For a list tool with zero required parameters, fully documented parameters, an output schema, and safety annotations, the description is sufficient for correct invocation. Only minor improvement would be explicit guidance on choosing this over search_releases or whats_new, but that is not essential here.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema coverage is 100% and the schema gives detailed descriptions for sort and category. The description adds the useful summary that filters can be combined, but it does not materially extend what the schema already provides.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description states a specific verb ('List') and a specific resource ('products What's New tracks release notes for'), and identifies the returned fields ('slugs, categories and platforms'). It is clearly distinct from siblings like search_releases and whats_new, which target release searching and news rather than the product catalog.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
The description frames this as the catalog of tracked products and mentions the available filters ('category and/or a name query'), giving clear context for when to call it. It does not explicitly contrast with search_releases or whats_new, but the resource distinction is implied strongly enough to select correctly.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
search_releasesSearch products and release notesARead-onlyIdempotentInspect
Full-catalog search across product names and release history. Returns matching products and releases with permalinks.
| Name | Required | Description | Default |
|---|---|---|---|
| query | Yes | Search products and release notes. At least 2 characters. | |
| category | No | Limit results to one product category. |
Output Schema
| Name | Required | Description |
|---|---|---|
| note | No | Present when nothing matched. |
| query | Yes | The query as searched — trimmed and capped. |
| category | No | Limit results to one product category. |
| products | Yes | |
| releases | Yes |
TDQS
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already communicate readOnlyHint, idempotentHint, and openWorldHint=false, so the safety profile is covered. The description adds the 'full-catalog' scope and the fact that results include permalinks, which is useful context. It does not disclose behavior like pagination, result limits, ordering, or match semantics, but given the annotations, the additional burden is modest.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
A single sentence conveys scope, action, and return value with no filler. The key differentiator (full-catalog coverage) is front-loaded, and every word earns its place.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
Given the presence of a complete input schema, an output schema, and informative annotations, the description is nearly sufficient on its own. The main gap is the lack of any note about result size, sorting, or how matching works, but for a simple read-only search these are minor and largely inferable from the schema and output contract.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema description coverage is 100%, so the schema already documents both parameters. The description adds no parameter-specific semantics beyond what is in the schema; it does not clarify the format or behavior of the query beyond 'search products and release notes', nor does it elaborate on the category filter. Baseline 3 is appropriate.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description uses a specific verb ('search') and names its resource precisely: 'full-catalog search across product names and release history.' It also states what is returned (matching products and releases with permalinks), making its scope clear even without inspecting the schema. This distinguishes it from sibling tools like list_products or whats_new.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
The description implies usage context: it is a search tool for finding specific products or releases across the full catalog. However, it does not explicitly say when to prefer this over list_products or whats_new, nor does it mention any exclusions or scenarios where an alternative should be used.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
upgrade_notesReview a dependency upgradeARead-onlyIdempotentInspect
Before or after upgrading dependencies — package.json / lockfile / requirements changes, npm update, pip install -U, a Gradle version catalog, go.mod, a workflow's actions — pass each package with the version you run and the version you are moving to. Returns every tracked release in between with the vendor's own breaking-change, deprecation, migration and security sections verbatim, the categorized change list, CVE ids and deterministic signals (major bump, removed/deprecated items, breaking mentions) — including breaking changes shipped in minor or patch versions. Pass repository (from the package's own package.json) for scoped or renamed packages; it makes the match exact. A Maven/Gradle, Go, NuGet or GitHub Actions package goes by its purl (e.g. pkg:maven/com.squareup.okhttp3/okhttp), or by its own coordinate as the name (group:artifact, a module path, owner/repo@ref), and is matched exactly or not at all.
| Name | Required | Description | Default |
|---|---|---|---|
| dependencies | Yes | Up to 20 per call; split a larger upgrade. |
Output Schema
| Name | Required | Description |
|---|---|---|
| notes | No | |
| dependencies | Yes |
TDQS
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already declare readOnlyHint and idempotentHint, and the description adds substantial behavior beyond that: returns vendor sections verbatim, categorized changes, CVE IDs, deterministic signals, and breaking changes shipped in minor/patch versions. It also discloses exact-match semantics for Maven/Gradle, Go, NuGet, and GitHub Actions packages. No contradiction with annotations.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is front-loaded with the main usage context and each sentence earns its place: when to use it, what it returns, and how to identify packages correctly. It is dense and somewhat run-on, but the length is justified by the tool's complexity and the important edge cases it covers.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
For a read-only lookup tool with an output schema and safety annotations, the description covers the essential preconditions (from/to versions, package identity), return contents, and edge cases such as scoped packages, renamed packages, purls, and exact matching. Nothing critical is missing for an agent to invoke it correctly.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema description coverage is 100%, so the baseline is 3. The description adds genuine value by explaining why `repository` matters for scoped/renamed packages and by illustrating purl/coordinate forms for non-npm ecosystems. The schema already documents the remaining parameter semantics, so the description complements rather than repeats.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description clearly states the resource (dependency upgrades) and the action ('pass each package...' / 'Returns...'), and enumerates specific outputs such as vendor breaking-change sections, categorized changes, and CVE IDs. It does not explicitly contrast itself with siblings like search_releases or whats_new, so differentiation relies on context rather than direct statement.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
The description gives strong contextual usage guidance: 'Before or after upgrading dependencies' plus concrete scenarios like package.json changes, npm update, pip install -U, Gradle version catalogs, go.mod, and workflow actions. It does not state when not to use the tool or name alternative sibling tools, so it falls short of full exclusionary guidance.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
whats_newWhat changed in a productARead-onlyIdempotentInspect
A product's newest releases with notes. Pass since_version (the version you run) to get only what shipped after it, with per-category change counts.
| Name | Required | Description | Default |
|---|---|---|---|
| limit | No | Releases to return, default 10. | |
| product | Yes | Product slug or name, e.g. "next-js" or "Next.js". | |
| since_version | No | The version you run. Returns only the releases above it in the history, matched exactly or as the same version spelled with fewer trailing zeros. A version we do not hold is reported as a miss rather than guessed into an ordering. |
Output Schema
| Name | Required | Description |
|---|---|---|
| notes | No | How the product or the version was resolved. |
| product | Yes | |
| releases | Yes | |
| returned | Yes | |
| truncated | No | |
| newerCount | No | Releases above the pinned version, before the limit. |
| changeCounts | No | Change items across the whole span, even when truncated. |
| sinceVersion | No | The version you passed. |
| sinceVersionFound | No | Whether that version was found in the history. False means the releases below are the latest, not the ones after yours. |
TDQS
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already declare readOnlyHint and idempotentHint, and the description adds useful behavior beyond that: filtering by since_version and returning per-category change counts. It also indirectly conveys that omitting since_version returns the newest releases without filtering, which is helpful.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
Two sentences with no filler: the first states the tool's core function, the second explains the key optional parameter and output characteristic. It is compact, front-loaded, and every sentence contributes value.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
Given the output schema exists and annotations cover safety/idempotence, the description covers the essential behavioral detail (since_version filtering and per-category counts) plus the notion of newest releases. Nothing critical for calling the tool correctly is missing.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema description coverage is 100%, so the baseline is 3. The description essentially restates the since_version semantics already present in the schema (the version you run, only what shipped after it) without adding new parameter-level meaning.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description clearly identifies the tool as returning a product's newest releases with notes, which is a specific verb-resource combination. It does not explicitly differentiate from sibling tools like search_releases, so the distinctiveness is somewhat implicit rather than stated.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
The description gives a clear usage condition for the since_version parameter: pass the version you run to get only what shipped after it. However, it gives no explicit guidance on when to choose this tool over list_products or search_releases, leaving the choice to be inferred from context.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
1 tool update
- Changed
upgrade_notes9 fields changed- changed
Input schema / properties / dependencies / items / properties / name / descriptionPrevious value: -"The package name as its registry spells it, e.g. \"better-auth\" or \"@tanstack/react-query\"."New value: +"The package as its ecosystem spells it: \"better-auth\", \"@tanstack/react-query\", a Maven \"group:artifact\", a Go module path, or an Action's \"owner/repo@ref\"." - added
Input schema / properties / dependencies / items / properties / purlAdded value: +{ + "description": "The package as a purl (package URL), e.g. \"pkg:maven/com.squareup.okhttp3/okhttp\", \"pkg:golang/github.com/spf13/cobra\" or \"pkg:nuget/Newtonsoft.Json\" — what an SBOM, OSV or Renovate already names it by. Takes precedence over name and registry; a version inside it is ignored in favour of from/to.", + "maxLength": 300, + "pattern": "^[Pp][Kk][Gg]:", + "type": "string" +} - changed
Input schema / properties / dependencies / items / properties / registry / descriptionPrevious value: -"Default npm."New value: +"Default npm — unless purl, or the name's own shape (group:artifact, a Go module path), says otherwise." - changed
Input schema / properties / dependencies / items / properties / repository / descriptionPrevious value: -"The package's source repository — its package.json `repository` (any GitHub URL, github:owner/repo or owner/repo). Resolves scoped and renamed packages the name alone cannot, and makes the match exact."New value: +"The package's source repository — its package.json `repository`, or the repo a Maven or NuGet package is built from (any GitHub URL, github:owner/repo or owner/repo). Resolves scoped and renamed packages the name alone cannot, and makes the match exact." - changed
Output schema / properties / dependencies / items / properties / match / properties / tier / descriptionPrevious value: -"identifier: a registry id or repository the catalog tracks. name: a name-only guess — check the product before trusting it, and pass repository to make it exact."New value: +"identifier: a registry id, a purl or a repository the catalog tracks. namespace: the package sits under a namespace the product claims (a Maven group, say) — the notes are the family's. name: a name-only guess — check the product before trusting it, and pass purl or repository to make it exact." - changed
Output schema / properties / dependencies / items / properties / match / properties / tier / enumPrevious value: -[ - "identifier", - "name" -]New value: +[ + "identifier", + "namespace", + "name" +] - added
Output schema / properties / dependencies / items / properties / purlAdded value: +{ + "description": "The package as a versionless purl, as it was matched.", + "type": "string" +} - added
Output schema / properties / dependencies / items / properties / registry / descriptionAdded value: +"The registry, when the package is in one of these four; absent for a Maven, Go, NuGet or Actions package." - changed
Output schema / properties / dependencies / items / requiredPrevious value: -[ - "name", - "registry", - "from", - "status" -]New value: +[ + "name", + "from", + "status" +]
1 tool update
- Added
upgrade_notes
3 tool updates
- Changed
list_products3 fields changed- added
Output schema / properties / products / items / properties / archivedAdded value: +{ + "description": "Whether the upstream repository is archived; absent when unknown.", + "type": "boolean" +} - added
Output schema / properties / products / items / properties / languageAdded value: +{ + "type": "string" +} - added
Output schema / properties / products / items / properties / licenseAdded value: +{ + "description": "SPDX expression as the product's own source states it, e.g. MIT or LicenseRef-proprietary; absent when unknown.", + "type": "string" +}
- Changed
search_releases3 fields changed- added
Output schema / properties / products / items / properties / archivedAdded value: +{ + "description": "Whether the upstream repository is archived; absent when unknown.", + "type": "boolean" +} - added
Output schema / properties / products / items / properties / languageAdded value: +{ + "type": "string" +} - added
Output schema / properties / products / items / properties / licenseAdded value: +{ + "description": "SPDX expression as the product's own source states it, e.g. MIT or LicenseRef-proprietary; absent when unknown.", + "type": "string" +}
- Changed
whats_new3 fields changed- added
Output schema / properties / product / properties / archivedAdded value: +{ + "description": "Whether the upstream repository is archived; absent when unknown.", + "type": "boolean" +} - added
Output schema / properties / product / properties / languageAdded value: +{ + "type": "string" +} - added
Output schema / properties / product / properties / licenseAdded value: +{ + "description": "SPDX expression as the product's own source states it, e.g. MIT or LicenseRef-proprietary; absent when unknown.", + "type": "string" +}
3 tool updates
- Changed
list_products2 fields changed- changed
Input schema / properties / category / enumPrevious value: -[ - "Developer Tools", - "Frameworks & Libraries", - "Languages & Runtimes", - "Games", - "Operating Systems", - "Browsers", - "Communication", - "Media", - "AI", - "Design Tools", - "Productivity", - "Firmware", - "Drivers" -]New value: +[ + "Developer Tools", + "Frameworks & Libraries", + "Languages & Runtimes", + "Infrastructure & DevOps", + "Databases & Data", + "Security & Privacy", + "Games", + "Gaming Tools", + "Operating Systems", + "System Utilities", + "Browsers", + "Communication", + "Media", + "Creative Tools", + "AI", + "Productivity", + "Lifestyle & Apps", + "Firmware", + "Drivers" +] - changed
Output schema / properties / products / items / properties / category / enumPrevious value: -[ - "Developer Tools", - "Frameworks & Libraries", - "Languages & Runtimes", - "Games", - "Operating Systems", - "Browsers", - "Communication", - "Media", - "AI", - "Design Tools", - "Productivity", - "Firmware", - "Drivers" -]New value: +[ + "Developer Tools", + "Frameworks & Libraries", + "Languages & Runtimes", + "Infrastructure & DevOps", + "Databases & Data", + "Security & Privacy", + "Games", + "Gaming Tools", + "Operating Systems", + "System Utilities", + "Browsers", + "Communication", + "Media", + "Creative Tools", + "AI", + "Productivity", + "Lifestyle & Apps", + "Firmware", + "Drivers" +]
- Changed
search_releases3 fields changed- changed
Input schema / properties / category / enumPrevious value: -[ - "Developer Tools", - "Frameworks & Libraries", - "Languages & Runtimes", - "Games", - "Operating Systems", - "Browsers", - "Communication", - "Media", - "AI", - "Design Tools", - "Productivity", - "Firmware", - "Drivers" -]New value: +[ + "Developer Tools", + "Frameworks & Libraries", + "Languages & Runtimes", + "Infrastructure & DevOps", + "Databases & Data", + "Security & Privacy", + "Games", + "Gaming Tools", + "Operating Systems", + "System Utilities", + "Browsers", + "Communication", + "Media", + "Creative Tools", + "AI", + "Productivity", + "Lifestyle & Apps", + "Firmware", + "Drivers" +] - changed
Output schema / properties / category / enumPrevious value: -[ - "Developer Tools", - "Frameworks & Libraries", - "Languages & Runtimes", - "Games", - "Operating Systems", - "Browsers", - "Communication", - "Media", - "AI", - "Design Tools", - "Productivity", - "Firmware", - "Drivers" -]New value: +[ + "Developer Tools", + "Frameworks & Libraries", + "Languages & Runtimes", + "Infrastructure & DevOps", + "Databases & Data", + "Security & Privacy", + "Games", + "Gaming Tools", + "Operating Systems", + "System Utilities", + "Browsers", + "Communication", + "Media", + "Creative Tools", + "AI", + "Productivity", + "Lifestyle & Apps", + "Firmware", + "Drivers" +] - changed
Output schema / properties / products / items / properties / category / enumPrevious value: -[ - "Developer Tools", - "Frameworks & Libraries", - "Languages & Runtimes", - "Games", - "Operating Systems", - "Browsers", - "Communication", - "Media", - "AI", - "Design Tools", - "Productivity", - "Firmware", - "Drivers" -]New value: +[ + "Developer Tools", + "Frameworks & Libraries", + "Languages & Runtimes", + "Infrastructure & DevOps", + "Databases & Data", + "Security & Privacy", + "Games", + "Gaming Tools", + "Operating Systems", + "System Utilities", + "Browsers", + "Communication", + "Media", + "Creative Tools", + "AI", + "Productivity", + "Lifestyle & Apps", + "Firmware", + "Drivers" +]
- Changed
whats_new1 field changed- changed
Output schema / properties / product / properties / category / enumPrevious value: -[ - "Developer Tools", - "Frameworks & Libraries", - "Languages & Runtimes", - "Games", - "Operating Systems", - "Browsers", - "Communication", - "Media", - "AI", - "Design Tools", - "Productivity", - "Firmware", - "Drivers" -]New value: +[ + "Developer Tools", + "Frameworks & Libraries", + "Languages & Runtimes", + "Infrastructure & DevOps", + "Databases & Data", + "Security & Privacy", + "Games", + "Gaming Tools", + "Operating Systems", + "System Utilities", + "Browsers", + "Communication", + "Media", + "Creative Tools", + "AI", + "Productivity", + "Lifestyle & Apps", + "Firmware", + "Drivers" +]
1 tool update
- Changed
list_products1 field changed- added
Input schema / properties / sortAdded value: +{ + "description": "\"popular\" ranks by current audience popularity — outside signals (stars, downloads, players) blended with this site's own readers — and answers \"what are the most popular software right now?\". Default is the curated catalog order (or search relevance when query is set, which ignores sort).", + "enum": [ + "curated", + "popular" + ], + "type": "string" +}
3 tool updates
- Changed
list_products1 field changed- changed
Output schema / (root)Previous value: -nullNew value: +{ + "$schema": "https://json-schema.org/draft/2020-12/schema", + "additionalProperties": false, + "properties": { + "products": { + "items": { + "additionalProperties": false, + "properties": { + "category": { + "enum": [ + "Developer Tools", + "Frameworks & Libraries", + "Languages & Runtimes", + "Games", + "Operating Systems", + "Browsers", + "Communication", + "Media", + "AI", + "Design Tools", + "Productivity", + "Firmware", + "Drivers" + ], + "type": "string" + }, + "description": { + "type": "string" + }, + "homepage": { + "description": "The vendor's own site.", + "type": "string" + }, + "labels": { + "description": "Provenance to keep with any quote, e.g. “Sample data”.", + "items": { + "type": "string" + }, + "type": "array" + }, + "name": { + "type": "string" + }, + "platforms": { + "items": { + "type": "string" + }, + "type": "array" + }, + "slug": { + "type": "string" + }, + "url": { + "description": "This product's page on What's New.", + "type": "string" + }, + "vendor": { + "type": "string" + } + }, + "required": [ + "slug", + "name", + "vendor", + "category", + "description", + "url", + "homepage" + ], + "type": "object" + }, + "type": "array" + }, + "returned": { + "maximum": 9007199254740991, + "minimum": -9007199254740991, + "type": "integer" + }, + "total": { + "description": "Matches before the cap.", + "maximum": 9007199254740991, + "minimum": -9007199254740991, + "type": "integer" + }, + "truncated": { + "const": true, + "type": "boolean" + } + }, + "required": [ + "total", + "returned", + "products" + ], + "type": "object" +}
- Changed
search_releases1 field changed- changed
Output schema / (root)Previous value: -nullNew value: +{ + "$schema": "https://json-schema.org/draft/2020-12/schema", + "additionalProperties": false, + "properties": { + "category": { + "description": "Limit results to one product category.", + "enum": [ + "Developer Tools", + "Frameworks & Libraries", + "Languages & Runtimes", + "Games", + "Operating Systems", + "Browsers", + "Communication", + "Media", + "AI", + "Design Tools", + "Productivity", + "Firmware", + "Drivers" + ], + "type": "string" + }, + "note": { + "description": "Present when nothing matched.", + "type": "string" + }, + "products": { + "items": { + "additionalProperties": false, + "properties": { + "category": { + "enum": [ + "Developer Tools", + "Frameworks & Libraries", + "Languages & Runtimes", + "Games", + "Operating Systems", + "Browsers", + "Communication", + "Media", + "AI", + "Design Tools", + "Productivity", + "Firmware", + "Drivers" + ], + "type": "string" + }, + "description": { + "type": "string" + }, + "homepage": { + "description": "The vendor's own site.", + "type": "string" + }, + "labels": { + "description": "Provenance to keep with any quote, e.g. “Sample data”.", + "items": { + "type": "string" + }, + "type": "array" + }, + "name": { + "type": "string" + }, + "platforms": { + "items": { + "type": "string" + }, + "type": "array" + }, + "slug": { + "type": "string" + }, + "url": { + "description": "This product's page on What's New.", + "type": "string" + }, + "vendor": { + "type": "string" + } + }, + "required": [ + "slug", + "name", + "vendor", + "category", + "description", + "url", + "homepage" + ], + "type": "object" + }, + "type": "array" + }, + "query": { + "description": "The query as searched — trimmed and capped.", + "type": "string" + }, + "releases": { + "items": { + "additionalProperties": false, + "properties": { + "changes": { + "items": { + "additionalProperties": false, + "properties": { + "category": { + "enum": [ + "added", + "changed", + "fixed", + "removed", + "deprecated", + "security" + ], + "type": "string" + }, + "text": { + "type": "string" + } + }, + "required": [ + "category", + "text" + ], + "type": "object" + }, + "type": "array" + }, + "channel": { + "description": "The source's own classification, e.g. “longterm”.", + "type": "string" + }, + "date": { + "description": "ISO 8601 timestamp.", + "type": "string" + }, + "labels": { + "description": "Provenance to keep with any quote, e.g. “Pre-release”.", + "items": { + "type": "string" + }, + "type": "array" + }, + "prerelease": { + "const": true, + "type": "boolean" + }, + "product": { + "additionalProperties": false, + "properties": { + "name": { + "type": "string" + }, + "slug": { + "type": "string" + } + }, + "required": [ + "slug", + "name" + ], + "type": "object" + }, + "sourceUrl": { + "description": "The vendor's own release notes.", + "type": "string" + }, + "summary": { + "type": "string" + }, + "title": { + "type": "string" + }, + "url": { + "description": "This release's page on What's New.", + "type": "string" + }, + "version": { + "type": "string" + } + }, + "required": [ + "title", + "date", + "url", + "sourceUrl", + "product" + ], + "type": "object" + }, + "type": "array" + } + }, + "required": [ + "query", + "products", + "releases" + ], + "type": "object" +}
- Changed
whats_new1 field changed- changed
Output schema / (root)Previous value: -nullNew value: +{ + "$schema": "https://json-schema.org/draft/2020-12/schema", + "additionalProperties": false, + "properties": { + "changeCounts": { + "additionalProperties": { + "maximum": 9007199254740991, + "minimum": -9007199254740991, + "type": "integer" + }, + "description": "Change items across the whole span, even when truncated.", + "propertyNames": { + "enum": [ + "added", + "changed", + "fixed", + "removed", + "deprecated", + "security" + ], + "type": "string" + }, + "type": "object" + }, + "newerCount": { + "description": "Releases above the pinned version, before the limit.", + "maximum": 9007199254740991, + "minimum": -9007199254740991, + "type": "integer" + }, + "notes": { + "description": "How the product or the version was resolved.", + "items": { + "type": "string" + }, + "type": "array" + }, + "product": { + "additionalProperties": false, + "properties": { + "category": { + "enum": [ + "Developer Tools", + "Frameworks & Libraries", + "Languages & Runtimes", + "Games", + "Operating Systems", + "Browsers", + "Communication", + "Media", + "AI", + "Design Tools", + "Productivity", + "Firmware", + "Drivers" + ], + "type": "string" + }, + "description": { + "type": "string" + }, + "homepage": { + "description": "The vendor's own site.", + "type": "string" + }, + "labels": { + "description": "Provenance to keep with any quote, e.g. “Sample data”.", + "items": { + "type": "string" + }, + "type": "array" + }, + "name": { + "type": "string" + }, + "platforms": { + "items": { + "type": "string" + }, + "type": "array" + }, + "slug": { + "type": "string" + }, + "url": { + "description": "This product's page on What's New.", + "type": "string" + }, + "vendor": { + "type": "string" + } + }, + "required": [ + "slug", + "name", + "vendor", + "category", + "description", + "url", + "homepage" + ], + "type": "object" + }, + "releases": { + "items": { + "additionalProperties": false, + "properties": { + "body": { + "type": "string" + }, + "bodyTruncated": { + "const": true, + "description": "The body was cut at the cap; the permalink has it all.", + "type": "boolean" + }, + "changes": { + "items": { + "additionalProperties": false, + "properties": { + "category": { + "enum": [ + "added", + "changed", + "fixed", + "removed", + "deprecated", + "security" + ], + "type": "string" + }, + "text": { + "type": "string" + } + }, + "required": [ + "category", + "text" + ], + "type": "object" + }, + "type": "array" + }, + "channel": { + "description": "The source's own classification, e.g. “longterm”.", + "type": "string" + }, + "date": { + "description": "ISO 8601 timestamp.", + "type": "string" + }, + "labels": { + "description": "Provenance to keep with any quote, e.g. “Pre-release”.", + "items": { + "type": "string" + }, + "type": "array" + }, + "prerelease": { + "const": true, + "type": "boolean" + }, + "sourceUrl": { + "description": "The vendor's own release notes.", + "type": "string" + }, + "summary": { + "type": "string" + }, + "title": { + "type": "string" + }, + "url": { + "description": "This release's page on What's New.", + "type": "string" + }, + "version": { + "type": "string" + } + }, + "required": [ + "title", + "date", + "url", + "sourceUrl" + ], + "type": "object" + }, + "type": "array" + }, + "returned": { + "maximum": 9007199254740991, + "minimum": -9007199254740991, + "type": "integer" + }, + "sinceVersion": { + "description": "The version you passed.", + "type": "string" + }, + "sinceVersionFound": { + "description": "Whether that version was found in the history. False means the releases below are the latest, not the ones after yours.", + "type": "boolean" + }, + "truncated": { + "const": true, + "type": "boolean" + } + }, + "required": [ + "product", + "returned", + "releases" + ], + "type": "object" +}
3 tool updates
- First observed
list_products - First observed
search_releases - First observed
whats_new
Related MCP Connectors
An agent-friendly API for product changelogs. A unified registry via CLI, API, or MCP.
- ShipstarOAuthai.shipstar
Generate changelogs, release emails, help-center articles, banners, and social posts from commits.
Latest versions, LTS windows, and EOL dates for 300+ products. Fresh ground truth for stale models.
Check exact npm/PyPI upgrades for evidence-backed breaking changes; query APIs and components.
Related MCP Servers
- AlicenseNot gradedqualityAmaintenanceProvides a local, queryable mirror of changelogs from Anthropic and related AI dev tools, enabling agents to discover cross-product workflows and sync updates via MCP.42 npmMIT
- AlicenseNot gradedqualityCmaintenanceEnables tracking and querying of vendor changelog entries, release notes, and product announcements, with tools to see recent changes, sweep for active accounts, and check feed coverage.MIT

Modelmeterofficial
AlicenseNot gradedqualityCmaintenanceEnables AI agents to query model pricing, deprecations, and cost estimates via a machine-readable changelog of the AI stack.1MIT- AlicenseNot gradedqualityDmaintenanceGenerate professional changelogs from git history and suggest semver bumps, with optional AI enhancement via Claude.39 npm2MIT
Glama MCP Gateway
Add one secure layer between your agents and this server.