API Tools

eosl.ai

Provides an API for querying hardware part numbers, product lifecycle dates, and vendor support information from the EOSL database.

1 endpoint5 known toolsFirst detected August 5, 2026Last detected September 5, 2026

ENDPOINT 1

https://eosl.ai/mcp

No auth detected

MCP server metadata

Name: eosl
Version: 1.0.0

Capabilities

tools

Server instructions

Look up end-of-life status for enterprise datacenter hardware (Cisco, Dell, HPE, Fortinet, IBM, Juniper, and more) by part number or product family. Every date is backed by a linked vendor bulletin — nothing is estimated, and unknown parts return found:false. Confirm critical dates at the sourceUrl before making support or purchasing decisions.

Known tools 5

lookup_part

Look up one hardware part number or model name in the EOSL.

Inferred read-only

bulk_check

Check up to 200 part numbers in one call (read-only, no auth; for a single part use lookup_part).

Inferred read-only

search_models

Search tracked product families by vendor, product line, or series name (case-insensitive substring, e.

Inferred read-only

get_family

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.

Inferred read-only

list_vendors

List all vendors tracked by EOSL.

Inferred read-only

CONNECT WITH APPROVAL

Client installation

Review this server and its permissions before adding it. Secret placeholders must be set locally.

Codex

~/.codex/config.toml

[mcp_servers.eosl]
url = "https://eosl.ai/mcp"
enabled = true

Claude Code

.mcp.json

{
  "mcpServers": {
    "eosl": {
      "type": "http",
      "url": "https://eosl.ai/mcp"
    }
  }
}

Claude Desktop

Settings → Connectors → Add custom connector

Name: eosl
Remote MCP URL: https://eosl.ai/mcp

Add this remote URL as a custom connector in Claude Desktop. Availability depends on the user plan and workspace policy.

Cursor

.cursor/mcp.json

{
  "mcpServers": {
    "eosl": {
      "url": "https://eosl.ai/mcp"
    }
  }
}

Visual Studio Code

.vscode/mcp.json

Add to Visual Studio Code

{
  "servers": {
    "eosl": {
      "type": "http",
      "url": "https://eosl.ai/mcp"
    }
  }
}

Generic MCP

Client-specific MCP configuration

{
  "name": "eosl",
  "transport": "streamable-http",
  "url": "https://eosl.ai/mcp"
}

MCP Inspector

Run the official MCP Inspector locally and enter the indexed Streamable HTTP endpoint.

TRUST AND VERIFICATION EVIDENCE

Trust Data Available

BuiltWith Trust API v2 evidence for eosl.ai was fetched 2026-08-28T16:43:43.473Z.

Trust status Neutral

eosl.ai is assessed as Neutral: No suspicious signals found, but no strong positive signal either

Indexed

Evidence is source-attributed and does not guarantee that a third-party server is safe. Risk labels are conservative metadata heuristics.