Connect your AI assistant to EOSL.ai — live MCP server
EOSL.ai runs a free, no-auth MCP server at https://eosl.ai/mcp. Add it to Claude, Cursor, or any MCP-capable agent and it can check hardware end-of-life status straight from the source-backed database — 11,442 part numbers, every date linked to the vendor's own bulletin.
Quick connect
claude mcp add --transport http eosl https://eosl.ai/mcp
Settings → Connectors → Add custom connector → URL https://eosl.ai/mcp
{ "mcpServers": { "eosl": { "url": "https://eosl.ai/mcp" } } }{ "servers": { "eosl": { "type": "http", "url": "https://eosl.ai/mcp" } } }Tools
lookup_part(part_number, vendor?)Resolve one part number to its lifecycle record: status, end of sale, EOSL, support runway score, vendor-bulletin source URL. Vendor-gated alias matching (e.g. Fortinet FG-60E → FortiGate-60E); never fuzzy, never guesses.bulk_check(part_numbers[] (≤200))Check a whole inventory list in one call — per-part rows plus summary counts (past / ending soon / supported / active / not found).search_models(query)Find tracked product families by vendor, line, or series name — top 10 with status and page URL.get_family(slug)The full source-backed record for one family: every SKU group with dates, bulletin URL, last-verified, replacement, part numbers.list_vendors(—)All tracked vendors with family counts and page URLs.Try asking your assistant
One call to lookup_part — status, dates, support runway score, and the Cisco bulletin to verify.
Paste part numbers; bulk_check grades up to 200 at once with summary counts.
get_family returns the bulletin-named successor with per-part mapping where published.
/.well-known/mcp/server-card.json. The endpoint is stateless Streamable HTTP — POST JSON-RPC 2.0 to /mcp. Protocol revisions 2024-11-05 through 2025-06-18.MCP server questions
What is the EOSL.ai MCP server?
A live Model Context Protocol endpoint at https://eosl.ai/mcp. MCP is the open standard AI assistants (Claude, ChatGPT, Cursor and others) use to call external tools. Connect it and your assistant can look up hardware end-of-life status directly from EOSL.ai's source-backed database — every answer carries the vendor bulletin URL.
Is it free? Do I need an API key?
Free, no key, no login, no account. It is read-only public data over Streamable HTTP (stateless JSON-RPC 2.0). Please use it fairly and cache where you can.
How fresh is the data?
The same database as the site: refreshed weekly from vendor sources (Cisco, HPE, Juniper, Fortinet and IBM refresh automatically; other vendors on republish). Every record carries a last-verified date and the vendor bulletin it came from.
Does the server see my inventory?
It sees the part numbers you ask about — that is the request — and records them in aggregate with no identity attached: which parts get asked for and whether each was found, so misses steer coverage. No IP, no client details, and nothing tied to you unless you attach an optional key, whose entire purpose is attributing your usage to you. For fully local checking, download the open dataset and match against it offline.
Can I attach an identity so my usage is counted as mine?
Yes — get a free key at /api/#key and add it as an X-EOSL-Key header in your MCP client config (with Claude Code: the same "claude mcp add" command plus --header "X-EOSL-Key: eosl_…"). It gates nothing; it puts your name on your own usage in the public report, as an anonymous bucket — emails are never published. The same pattern endoflife-mcp uses.