What's New
REMOTE · WHATSNEW.FYI
Changelogs for apps, games and operating systems. Ask what shipped since the version you run.
Available components
Last scanned (16 hours ago)
Scores higher than 86% of remote servers
Reachable. Last reached 21 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 Security80
- 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. Nothing on it is marked destructive, but we can't show that an anonymous caller can only read: full credit needs the server to list at least one tool and every tool to be verifiably read-only. We use a best-effort check of tool names and descriptions to tell read-only tools from tools that change things, so some genuinely read-only tools may not get full credit. Names that start with a read verb (get, list, read, search and similar) and accurate readOnlyHint annotations help. Meet that to earn full credit, or require authorisation. See how to fix → View diagnostics → Partial
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
- 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 Usability63
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 1395 tokens (~279/item across 5 items; 5 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 Management100
- No destabilizing schema changes in the last 30 days.Pass
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
- Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 5 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 6 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a current MCP spec version (2026-07-28).Pass
Checks we ran (13)
- TLS certificate
- Authorization
- HTTPS
- HSTS header
- DNSSEC
- Transport
- Schema quality
- Stability
- Tool coverage
- Injection markers
- Destructive annotations
- Judged manipulation
- MCP protocol
Does not apply to this hosted endpoint (2)
- Supply Chain SecurityScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
- Provenance & TransparencyScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
The score does not measure everything. What the score does not measure →
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.
- 11 Nov 26 0
- Stability: 0.97 → pass security
- 10 Nov 26 0
- Stability: pass → 0.97 functional
- 8 Nov 26 0
- Stability: 0.97 → pass security
- 7 Nov 26 0
- Stability: pass → 0.97 functional
- 6 Nov 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 13 Oct 26 0
- The server rewrote its instructions, which are the text every model session reads security
- 28 Sept 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 26 Sept 26 0
- The server rewrote its instructions, which are the text every model session reads security
- Schema quality: 223 → 267 ▼ functional
- Server version: 1.6.0 → 1.7.0 functional
- New tool “missing_changes” functional
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 21 Nov 2026 · Probed https://whatsnew.fyi/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=*.whatsnew.fyi | CN=YR1,O=Let's Encrypt,C=US | 26 Sept 2026 | 25 Dec 2026 | RSA 2048 | SHA256-RSA | 5b966395fd678f565b0c49a80b0f0f67a37 |
| SANs: *.whatsnew.fyi, whatsnew.fyi | ||||||
| CN=YR1,O=Let's Encrypt,C=US (CA) | CN=Root YR,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | RSA 2048 | SHA256-RSA | a20253f15f2691c05dc1ce13b9bcca4e |
| CN=Root YR,O=ISRG,C=US (CA) | CN=ISRG Root X1,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | RSA 4096 | SHA256-RSA | f24b6d17f9d9ad7cb1c9fea78782699f |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of whatsnew.fyi. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | Trust anchor | 20326, 38696 | 8, 8 | Verified |
| fyi. | DS published | 6839 | 8 | Verified |
| whatsnew.fyi. | No DS | 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 |
| Header | Value |
|---|---|
| strict-transport-security | max-age=63072000; includeSubDomains |
| content-security-policy | default-src 'self'; base-uri 'self'; form-action 'self'; frame-ancestors 'none'; frame-src 'none'; object-src 'none'; script-src 'self' 'unsafe-inline'; style-src 'self' 'unsafe-inline'; img-src 'self' https://lh3.googleusercontent.com https://avatars.githubusercontent.com https://gitlab.com https://secure.gravatar.com https://avatars.steamstatic.com https://avatars.akamai.steamstatic.com https://avatars.cloudflare.steamstatic.com https://www.gravatar.com; font-src 'self'; media-src 'none'; manifest-src 'self'; worker-src 'self' blob:; connect-src 'self'; upgrade-insecure-requests |
| x-content-type-options | nosniff |
| x-frame-options | DENY |
| referrer-policy | strict-origin-when-cross-origin |
| permissions-policy | accelerometer=(), autoplay=(), camera=(), display-capture=(), encrypted-media=(), geolocation=(), gyroscope=(), magnetometer=(), microphone=(), midi=(), payment=(), usb=(), xr-spatial-tracking=(), browsing-topics=() |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://whatsnew.fyi/mcp | Verified | 200 | |
| http (plaintext) | http://whatsnew.fyi/mcp | HTTPS enforced | 308 | https://whatsnew.fyi/mcp |
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 →
list_products List tracked products ~130
The products What's New tracks release notes for, with slugs, categories and platforms. Filter by category and/or a name query.
| Name | Type | Req | Description |
|---|---|---|---|
| category | string | – | Limit results to one product category. |
| query | string | – | Filter by name, e.g. "terminal" or "jetbrains". |
| sort | string | – | "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?". Defaul… |
| Name | Type | Req | Description |
|---|---|---|---|
| products | array | yes | – |
| returned | integer | yes | – |
| total | integer | yes | Matches before the cap. |
| truncated | boolean | – | – |
No examples provided.
missing_changes What an outdated project is missing ~381
For a whole project's outdated report — npm/pnpm outdated --json (current → from, wanted, latest), ncu --format installedVersion, pip or uv pip list --outdated --format json (version → from, latest_version → latest), go list -m -u -json all (Version → from, Update.Version → latest), cargo outdated, dotnet list package --outdated, a Gradle versions report — pass each package with the version installed and, where the tool gives them, wanted and latest. Answers what the project is missing, most exposed first: per package, the security releases, CVE ids and fixes it does not have, split into toWanted (from → wanted: reachable by an update within the declared range, no manifest edit) and toLatest (→ latest: needs the range changed), with the cost of moving beside them (major bump, breaking mentions, removed/deprecated) and a few of the fixes themselves. Counts are deterministic over every tracked release; no model judged anything. Up to 100 packages a call. Pass repository (from the package's own package.json) for scoped or renamed packages; a Maven, Go or NuGet package goes by its purl. For the vendor's own breaking-change and migration sections, call upgrade_notes on the packages worth moving. A Maven, Go or NuGet package this server does not track is checked against deps.dev after the answer and counted; pass recordMisses: false for private packages.
| Name | Type | Req | Description |
|---|---|---|---|
| dependencies | array | yes | Up to 100 per call; split a larger project. |
| recordMisses | boolean | – | Default true. A Maven, Go or NuGet package this server does not track is checked against deps.dev after the answer and counted per day, with nothing about the caller, to decide what to track next. Pa… |
| Name | Type | Req | Description |
|---|---|---|---|
| dependencies | array | yes | Most exposed first — CVEs, then security releases, then fixes, then releases behind; untracked last, in the order given. |
| notes | array | – | – |
| summary | object | yes | – |
No examples provided.
search_releases Search products and release notes ~61
Full-catalog search across product names and release history. Returns matching products and releases with permalinks.
| Name | Type | Req | Description |
|---|---|---|---|
| category | string | – | Limit results to one product category. |
| query | string | yes | Search products and release notes. At least 2 characters. |
| Name | Type | Req | Description |
|---|---|---|---|
| category | string | – | Limit results to one product category. |
| note | string | – | Present when nothing matched. |
| products | array | yes | – |
| query | string | yes | The query as searched — trimmed and capped. |
| releases | array | yes | – |
No examples provided.
upgrade_notes Review a dependency upgrade ~325
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.
| Name | Type | Req | Description |
|---|---|---|---|
| dependencies | array | yes | Up to 20 per call; split a larger upgrade. |
| recordMisses | boolean | – | Default true. A Maven, Go or NuGet package this server does not track is checked against deps.dev after the answer and counted per day, with nothing about the caller, to decide what to track next. Pa… |
| Name | Type | Req | Description |
|---|---|---|---|
| dependencies | array | yes | – |
| notes | array | – | – |
No examples provided.
whats_new What changed in a product ~129
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 | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | Releases to return, default 10. |
| product | string | yes | Product slug or name, e.g. "next-js" or "Next.js". |
| since_version | string | – | 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… |
| Name | Type | Req | Description |
|---|---|---|---|
| changeCounts | object | – | Change items across the whole span, even when truncated. |
| newerCount | integer | – | Releases above the pinned version, before the limit. |
| notes | array | – | How the product or the version was resolved. |
| product | object | yes | – |
| releases | array | yes | – |
| returned | integer | yes | – |
| sinceVersion | string | – | The version you passed. |
| sinceVersionFound | boolean | – | Whether that version was found in the history. False means the releases below are the latest, not the ones after yours. |
| truncated | boolean | – | – |
No examples provided.
How do I install the What's New MCP server?
What's New is a hosted endpoint at https://whatsnew.fyi/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 · whatsnew.fyi
claude mcp add --transport http fyi-whatsnew-changelogs 'https://whatsnew.fyi/mcp'
What is the What's New MCP server?
What's New is an MCP server listed in the public MCP registry as fyi.whatsnew/changelogs. Changelogs for apps, games and operating systems. Ask what shipped since the version you run. This page covers its hosted endpoint (https://whatsnew.fyi/mcp).
Is the What's New MCP server safe to use?
What's New scores 85 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 What's New MCP server expose?
What's New exposes 5 tools: list_products, search_releases, whats_new, upgrade_notes, missing_changes. Their descriptions and schemas cost roughly 1,026 tokens of context every time the server is loaded.
Does the What's New MCP server require authentication?
No. We connected to What's New without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the What's New MCP server still maintained?
What's New is still listed as active in the MCP registry. We last reached this channel on 21 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.
What did VerifyMCP test on the What's New MCP server?
VerifyMCP ran 13 checks on What's New, covering TLS certificate, Authorization, HTTPS, HSTS header and 9 more. Supply Chain Security and Provenance & Transparency do not apply to a hosted endpoint, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.