accueil / serveurs / Dev & Code / fyi.whatsnew/changelogs
fyi.whatsnew/changelogs
serveur MCP (Model Context Protocol) · whatsnew-fyi 1.7.0
Référencé dans l'annuaire. Seul le pentest comportemental fait foi, et il n'a pas encore été exécuté sur ce serveur.
Est-ce que fyi.whatsnew/changelogs est sûr ?
Au dernier audit MCP Hub, le serveur MCP « fyi.whatsnew/changelogs » est classé « Non encore testé ». Référencé dans l'annuaire. Seul le pentest comportemental fait foi, et il n'a pas encore été exécuté sur ce serveur. Le verdict est réévalué en continu ; consultez la fiche pour l'état à jour.
Méthode : MCP Hub analyse la description de chaque outil (couche 1) et, pour le verdict fort, exécute le serveur dans une micro-VM isolée avec leurres et réseau bloqué (couche 2). On publie des noms et des compteurs, jamais le contenu brut renvoyé par un outil.
Les 5 outils
- list_products≈ 778 tokens
The products What's New tracks release notes for, with slugs, categories and platforms. Filter by category and/or a name query.
Paramètres, retour & exemple (3)
Paramètressort· string · optionnel · curated | popular
"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· string · optionnel
Filter by name, e.g. "terminal" or "jetbrains".category· string · optionnel · Developer Tools | Frameworks & Libraries | Languages & Runtimes | Infrastructure & DevOps | Databases & Data | Security & Privacy | Games | Gaming Tools
Limit results to one product category.
Exemple d'appel{"name": "list_products", "arguments": {"sort": "curated", "query": "texte", "category": "Developer Tools"}}Exemple de retour{"content": [{"type": "text", "text": "…"}], "structuredContent": {"total": 1, "products": [], "returned": 1, "truncated": true}} - missing_changes≈ 4236 tokens
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.
Paramètres, retour & exemple (2)
Paramètresdependencies· array · requis
Up to 100 per call; split a larger project.recordMisses· boolean · optionnel
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. Pass false for private packages.
Exemple d'appel{"name": "missing_changes", "arguments": {"dependencies": []}}Exemple de retour{"content": [{"type": "text", "text": "…"}], "structuredContent": {"notes": [], "summary": {}, "dependencies": []}} - search_releases≈ 1075 tokens
Full-catalog search across product names and release history. Returns matching products and releases with permalinks.
Paramètres, retour & exemple (2)
Paramètresquery· string · requis
Search products and release notes. At least 2 characters.category· string · optionnel · Developer Tools | Frameworks & Libraries | Languages & Runtimes | Infrastructure & DevOps | Databases & Data | Security & Privacy | Games | Gaming Tools
Limit results to one product category.
Exemple d'appel{"name": "search_releases", "arguments": {"query": "texte"}}Exemple de retour{"content": [{"type": "text", "text": "…"}], "structuredContent": {"note": "texte", "query": "texte", "category": "Developer Tools", "products": [], "releases": []}} - upgrade_notes≈ 2784 tokens
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.
Paramètres, retour & exemple (2)
Paramètresdependencies· array · requis
Up to 20 per call; split a larger upgrade.recordMisses· boolean · optionnel
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. Pass false for private packages.
Exemple d'appel{"name": "upgrade_notes", "arguments": {"dependencies": []}}Exemple de retour{"content": [{"type": "text", "text": "…"}], "structuredContent": {"notes": [], "dependencies": []}} - whats_new≈ 1174 tokens
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.
Paramètres, retour & exemple (3)
Paramètreslimit· integer · optionnel
Releases to return, default 10.product· string · requis
Product slug or name, e.g. "next-js" or "Next.js".since_version· string · optionnel
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.
Exemple d'appel{"name": "whats_new", "arguments": {"product": "texte"}}Exemple de retour{"content": [{"type": "text", "text": "…"}], "structuredContent": {"notes": [], "product": {}, "releases": [], "returned": 1, "truncated": true, "newerCount": 1, "changeCounts": {}, "sinceVersion": "texte", "sinceVersionFound": true}}
C'est votre serveur ?
Revendiquez-le sur l'espace créateur (preuve GitHub, domaine ou npm) pour afficher le badge « propriétaire vérifié » et lancer un pentest comportemental à la demande afin d'obtenir le badge « Vérifié ».