English Français العربية

EOSL.ai — Hardware End-of-Life Database

Official registry Data and databases

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

Website

Install

Add this to your client's MCP configuration (Claude Desktop: claude_desktop_config.json; Cursor: .cursor/mcp.json; VS Code and others use the same "mcpServers" shape).

Remote (streamable-http)
Claude Code 
claude mcp add --transport http eosl-ai-hardware-end-of-life-database 'https://eosl.ai/mcp'
JSON configuration (Claude Desktop, Cursor, VS Code) 
{
    "mcpServers": {
        "eosl-ai-hardware-end-of-life-database": {
            "type": "http",
            "url": "https://eosl.ai/mcp"
        }
    }
}

Frequently asked questions

What is EOSL.ai — Hardware End-of-Life Database?

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

How do I install EOSL.ai — Hardware End-of-Life Database?

It runs as a remote server. In Claude Code: claude mcp add --transport http eosl-ai-hardware-end-of-life-database 'https://eosl.ai/mcp'. For other clients, paste the JSON configuration from this page into their MCP settings.

Does EOSL.ai — Hardware End-of-Life Database need an API key?

Its registry entry lists no required key or secret. Some features may still need an account with the service it connects to.

Who maintains EOSL.ai — Hardware End-of-Life Database?

It is published by ai.eosl. AI.tn lists it but does not maintain or endorse it.

From the official MCP Registry. Listing is not an endorsement: review a server's code and permissions before giving it access to your data.