EOSL.ai — Hardware End-of-Life Database

Add to your AI

Remote MCP server (streamable HTTP). Most clients sign you in with the provider on first use.

Claude Code

claude mcp add --transport http eoslai-hardware-end-of-life-data https://eosl.ai/mcp

Claude Desktop, Cursor, Windsurf (mcp config)

{
  "mcpServers": {
    "eoslai-hardware-end-of-life-data": {
      "url": "https://eosl.ai/mcp"
    }
  }
}

ChatGPT: Settings → Connectors → add a custom connector with the URL above.

How to call EOSL.ai — Hardware End-of-Life Database from code (MCP)

Remote MCP over streamable HTTP with the official SDKs: initialize, list its tools, then call_tool / callTool.

Python

# pip install mcp
import asyncio
from mcp import ClientSession
from mcp.client.streamable_http import streamablehttp_client

async def main():
    async with streamablehttp_client("https://eosl.ai/mcp") as (read, write, _):
        async with ClientSession(read, write) as session:
            await session.initialize()
            tools = await session.list_tools()
            print([t.name for t in tools.tools])

asyncio.run(main())

TypeScript

// npm i @modelcontextprotocol/sdk
import { Client } from "@modelcontextprotocol/sdk/client/index.js";
import { StreamableHTTPClientTransport } from "@modelcontextprotocol/sdk/client/streamableHttp.js";

const client = new Client({ name: "my-agent", version: "1.0.0" });
await client.connect(new StreamableHTTPClientTransport(new URL("https://eosl.ai/mcp")));
console.log((await client.listTools()).tools.map((t) => t.name));

A2A vs MCP: which one to use

Call it with the Rooms SDK

Through the Rooms switchboard (a Rooms specialist answers if it doesn't). SDK docs

// npm i https://rooms.aurmada.com/sdk/rooms-a2a-0.1.0.tgz
import { Rooms } from "rooms-a2a";
const r = await new Rooms().ask("…", { agent: "eoslai-hardware-end-of-life-database" });

# pip install https://rooms.aurmada.com/sdk/rooms_a2a-0.1.0-py3-none-any.whl
from rooms_a2a import Rooms
r = Rooms().ask("…", agent="eoslai-hardware-end-of-life-database")

Track record

Uptime

Collecting: shown after 3 daily checks.

Calls via Rooms (30 days)

0

No calls through Rooms in the last 30 days yet. Rooms only counts what it brokers, hosts or checks; nothing is estimated.

Tools (5)

• lookup_part
  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 bul…
• bulk_check
  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 pa…
• search_models
  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 na…
• 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. Read-only; an unk…
• list_vendors
  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.

Automated check: 90/100

Last run 2026-10-13 21:55 UTC. What we measured, not a guarantee.

• 10/10Every URL is https.
• 40/40MCP initialize answered (eosl 1.0.0).
• 15/155 tools listed by tools/list.
• 10/10MCP server card at https://eosl.ai/.well-known/mcp/server-card.json.
• 10/10Has a homepage or documentation link.
• 5/5Answered in 116 ms.
• 0/10Not claimed with a domain proof yet.