Skip to content

EOSL.ai — Hardware End-of-Life Database

by eosl.ai · remote · no sign-in to list tools · v1.0.0 · published by ai.eosl

Hardware end-of-life dates by part number, each linked to the vendor's own bulletin.

Changes · 1

5 tools: 1 change things and 4 only read.

Scanned Oct 21, 2026

No check matched anything in the tool definitions. No finding is not a safety guarantee. How the checks work.

claude mcp add --transport http eosl https://eosl.ai/mcp

Tools

Open a tool for its reasons and full description. Descriptions are the publisher's own words, shown as they are.

5 tools

Changes things 1Claude Code: ask
  • bulk_checkCheck up to 200 part numbers in one call (read-only, no auth; for a single part use lookup_part).No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    Description, as the server wrote it
    Check up to 200 part numbers in one call (read-only, no auth; for a single part use lookup_part). Returns a per-part row (status, EOSL date, source URL, page URL) plus summary counts: past, endingSoon, supported, active, notFound. Never partial and never destructive: unknown or malformed entries do not fail the call, each simply returns found:false in its row.
Only reads 4Claude Code: allow
  • get_familyFetch the full source-backed record for one product family by slug (from search_models or lookup_part pageUrl): lifecycle dates per SKU group, every part number, support runway sco…No findings

    Why it is in this group

    • The name "get_family" says "get": a word for reading.
    Description, as the server wrote it
    Fetch the full source-backed record for one product family by slug (from search_models or lookup_part pageUrl): lifecycle dates per SKU group, every part number, support runway score factors, and the vendor bulletin URLs. Read-only; an unknown slug returns found:false with a hint, never an error.
  • list_vendorsList all vendors tracked by EOSL.ai with family counts and vendor page URLs.No findings

    Why it is in this group

    • The name "list_vendors" says "list": a word for reading.
    Description, as the server wrote it
    List all vendors tracked by EOSL.ai with family counts and vendor page URLs. Read-only, no parameters. Use this first to check whether a vendor is covered at all; for specific models use search_models, for a part number use lookup_part.
  • lookup_partLook up one hardware part number or model name in the EOSL.ai database (read-only, no auth; for many parts use bulk_check).No findings

    Why it is in this group

    • The name "lookup_part" says "lookup": a word for reading.
    Description, as the server wrote it
    Look up one hardware part number or model name in the EOSL.ai database (read-only, no auth; for many parts use bulk_check). Returns support status, End-of-Sale and End-of-Service-Life dates, support runway score, and the primary vendor bulletin URL backing the dates. Matching is exact, then punctuation-insensitive, then Fortinet short-SKU aliases (FG-60E -> FortiGate-60E); a model/family name (e.g. "7010TX-48") that matches no SKU returns the family-level record, flagged matchedVia:family-name. Anything else returns found:false rather than a guessed date.
  • search_modelsSearch tracked product families by vendor, product line, or series name (case-insensitive substring, e.g.No findings

    Why it is in this group

    • The name "search_models" says "search": a word for reading.
    Description, as the server wrote it
    Search tracked product families by vendor, product line, or series name (case-insensitive substring, e.g. "nexus 9300"). Read-only. Returns up to 10 families with status, EOSL window, and page URL. Use this for discovery when you have a name; for an exact part number use lookup_part, and use get_family with a returned slug for the full record.

This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.

Install

Pinned to version 1.0.0. Values in angle brackets are yours to fill in.

claude mcp add --transport http eosl https://eosl.ai/mcp

Run in a terminal.

Claude Code permissions

Allow the reads, ask before a change, deny the deletes. Paste into .claude/settings.json.

.claude/settings.json
{
  "permissions": {
    "allow": [
      "mcp__eosl__lookup_part",
      "mcp__eosl__search_models",
      "mcp__eosl__get_family",
      "mcp__eosl__list_vendors"
    ],
    "ask": [
      "mcp__eosl__bulk_check"
    ],
    "deny": []
  }
}

Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. It assumes the server is installed as eosl. Review it before you use it.