accueil / serveurs / Dev & Code / io.github.endoflife-ai/endoflife-mcp
io.github.endoflife-ai/endoflife-mcp
serveur MCP (Model Context Protocol) · endoflife.ai 1.4.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 io.github.endoflife-ai/endoflife-mcp est sûr ?
Au dernier audit MCP Hub, le serveur MCP « io.github.endoflife-ai/endoflife-mcp » 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 10 outils
- check_eol≈ 244 tokens
Check whether a specific version of a software product is end-of-life (EOL). Returns lifecycle status, the EOL date, days remaining or days past EOL, the latest release, and eol_date_source (where the date comes from: vendor-override, vendor-fetched, vendor-verified, custom, upstream, or discrepancy) with its source URL. Use this for "is X version Y still supported?" questions.
Paramètres, retour & exemple (2)
Paramètresproduct· string · requis
Product slug or name, e.g. "postgresql", "nodejs", "ubuntu".version· string · requis
Version/cycle, e.g. "14", "18", "20.04".
Exemple d'appel{"name": "check_eol", "arguments": {"product": "texte", "version": "texte"}}Exemple de retour{"content": [{"type": "text", "text": "…"}]} - check_sbom≈ 272 tokens
Audit a CycloneDX or SPDX JSON software bill of materials. Components are mapped to tracked products and scored for EOL risk; unmatched components are listed honestly rather than guessed. Pass the SBOM as a JSON string or object. Versions resolve to their release family (python 3.12, php 7.4, ubuntu 20.04). Without a key up to 5 matched components are scored per call; Starter 25; Pro 50. Larger SBOMs return the scored subset plus a note of how many were not checked.
Paramètres, retour & exemple (2)
Paramètressbom· ? · requis
The SBOM document (JSON string or object). CycloneDX (bomFormat/components) or SPDX (spdxVersion/packages).max_items· integer · optionnel
Optional: return at most this many scored components (the tier cap applies first).
Exemple d'appel{"name": "check_sbom", "arguments": {"sbom": "texte"}}Exemple de retour{"content": [{"type": "text", "text": "…"}]} - get_edge_device_status≈ 324 tokens
Query the EOS Edge Device Intelligence feed — firewalls, VPN gateways and appliances, ADCs, router and switch operating systems — with end-of-support status in the vocabulary of CISA BOD 26-02 (eos, within-12-months, scheduled, no-date-announced). Filter by platform or vendor name, by status, or by model/line. Each platform carries its KEV summary, vendor-stated successor and provenance. Use for "which of our edge devices are past support or expire within 12 months?".
Paramètres, retour & exemple (3)
Paramètresmodel· string · optionnel
Optional substring matched against the line / model name, e.g. "ISA6000", "7.2", "SMA 100".status· string · optionnel · eos | within-12-months | scheduled | no-date-announced
Optional status filter.platform· string · optionnel
Optional substring matched against platform slug, name, vendor or category, e.g. "fortinet", "ivanti", "vpn".
Exemple d'appel{"name": "get_edge_device_status", "arguments": {"model": "texte", "status": "eos", "platform": "texte"}}Exemple de retour{"content": [{"type": "text", "text": "…"}]} - get_kev_exposure≈ 269 tokens
The exploited-vulnerability record for a product: every CVE CISA lists against it in the Known Exploited Vulnerabilities catalog, with the date added, the federal due date and CISA's required-action text verbatim (the "discontinue use" entries are the ones that matter for end-of-life versions), plus any entries from endoflife.ai's Exploited & Unpatchable feed (exploited CVEs whose affected versions will never receive a fix). Pass an optional version to include its support status alongside.
Paramètres, retour & exemple (2)
Paramètresproduct· string · requis
Product slug or name, e.g. "ivanti-connect-secure", "fortios".version· string · optionnel
Optional version/cycle to check support status for.
Exemple d'appel{"name": "get_kev_exposure", "arguments": {"product": "texte"}}Exemple de retour{"content": [{"type": "text", "text": "…"}]} - get_product_lifecycle≈ 164 tokens
Get the full version history for one product: every tracked version/cycle with its release date, EOL date, support status, and EOL Risk Score. Use for "give me the whole EOL schedule for X".
Paramètres, retour & exemple (1)
Paramètresproduct· string · requis
Product slug or name, e.g. "postgresql".
Exemple d'appel{"name": "get_product_lifecycle", "arguments": {"product": "texte"}}Exemple de retour{"content": [{"type": "text", "text": "…"}]} - get_risk_score≈ 222 tokens
Get the proprietary EOL Risk Score (0-100) for a product version, with the four-factor breakdown (EOL recency, attack surface, CISA KEV exposure, extended support). Omit "version" to score the product's highest-risk (most recently end-of-lifed) release. Use this to quantify how dangerous it is to keep running something.
Paramètres, retour & exemple (2)
Paramètresproduct· string · requis
Product slug or name, e.g. "openssl", "python".version· string · optionnel
Optional version/cycle. Omit for the highest-risk release.
Exemple d'appel{"name": "get_risk_score", "arguments": {"product": "texte"}}Exemple de retour{"content": [{"type": "text", "text": "…"}]} - get_upcoming_eol≈ 273 tokens
What reaches end-of-life soon. Returns every tracked version whose EOL date falls within the next N days (default 90), optionally limited to a list of products, sorted by date. Also lists versions that went EOL within the last "recent_past_days" days when set. Use for "what in our stack expires this quarter?".
Paramètres, retour & exemple (3)
Paramètresdays· integer · optionnel
Look-ahead window in days (default 90, max 730).products· array · optionnel
Optional product slugs or names to restrict to (max 50). Omit for the whole catalog.recent_past_days· integer · optionnel
Also include versions that went EOL within this many days in the past (default 0).
Exemple d'appel{"name": "get_upcoming_eol", "arguments": {"days": 1, "products": [], "recent_past_days": 1}}Exemple de retour{"content": [{"type": "text", "text": "…"}]} - get_upgrade_path≈ 199 tokens
Where to move a product version: the current version's support status and score, the supported releases with the longest remaining support, endoflife.ai's recommended target, and the vendor's stated successor where one is published (edge appliances). Use after check_eol says a version is EOL.
Paramètres, retour & exemple (2)
Paramètresproduct· string · requis
Product slug or name.version· string · optionnel
Optional current version/cycle.
Exemple d'appel{"name": "get_upgrade_path", "arguments": {"product": "texte"}}Exemple de retour{"content": [{"type": "text", "text": "…"}]} - list_products≈ 169 tokens
List or search the 700+ products endoflife.ai tracks. Pass an optional "query" substring to find the canonical slug for a product before calling the other tools (e.g. "postgres" → "postgresql"). Returns matching product slugs.
Paramètres, retour & exemple (1)
Paramètresquery· string · optionnel
Optional case-insensitive substring filter.
Exemple d'appel{"name": "list_products", "arguments": {"query": "texte"}}Exemple de retour{"content": [{"type": "text", "text": "…"}]} - scan_stack≈ 270 tokens
Audit a whole stack at once. Provide a list of products (optionally with versions) — e.g. parsed from a package.json or Dockerfile — and get an EOL Risk Score for each, so you can see what is unsupported and dangerous in one call. For CycloneDX or SPDX documents use check_sbom instead. Without a key: up to 5 items per call; Starter 25; Pro 50. Items beyond the limit are listed as not checked, with a note.
Paramètres, retour & exemple (1)
Paramètresitems· array · requis
List of stack components to score.
Exemple d'appel{"name": "scan_stack", "arguments": {"items": []}}Exemple de retour{"content": [{"type": "text", "text": "…"}]}
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é ».