目录 / changelogs
changelogs
Every vendor publishes release notes somewhere different. A GitHub release, a Steam patch note, a console firmware page, an IDE changelog nobody links to. What's New reads all of them and stores what it finds in one shape. Four read-only tools open that catalog to an agent: list_products and search_releases do what they sound like, whats_new takes the version you actually run and answers with only what shipped after it, and upgrade_notes takes the dependencies you are upgrading, from npm to Maven, and answers per package with the vendor's own breaking-change and migration sections — the ones a minor version number never announced. There is no key and no sign-in: point a client at https://whatsnew.fyi/mcp and start asking. Every entry keeps the provenance labels the site shows and links to the vendor's own notes, which are still the authoritative copy.
接入信息
- 传输形态
- http
- 鉴权方式
- 鉴权未知
- 端点
https://changelogs--whatsnew.run.tools
{
"mcpServers": {
"changelogs": {
"url": "https://changelogs--whatsnew.run.tools"
}
}
}
能力清单
| 工具 | 说明 |
|---|---|
| list_products | The products What's New tracks release notes for, with slugs, categories and platforms. Filter by category and/or a name query. |
| search_releases | Full-catalog search across product names and release history. Returns matching products and releases with permalinks. |
| whats_new | 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. |
| upgrade_notes | 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. A Maven, Go or NuGet package this server does not track is checked against deps.dev after the answer and counted, to decide what to track next; pass recordMisses: false for private packages. |
提交举报 / 纠错
侵权举报经核验成立后，我们会即时下线该条目并删除已存的内容副本。