About EOSL.ai — Hardware End-of-Life Database
Hardware end-of-life dates by part number, each linked to the vendor's own bulletin
Configuration
Remote servers need no local install. Pick your client, then copy the config or install in one click.
https://eosl.ai/mcpclaude mcp add --transport http ai-eosl-eosl https://eosl.ai/mcp{"mcpServers":{"ai-eosl-eosl":{"type":"http","url":"https://eosl.ai/mcp"}}}Open in Cursor{"servers":{"ai-eosl-eosl":{"type":"http","url":"https://eosl.ai/mcp"}}}Open in VS Code{"mcpServers":{"ai-eosl-eosl":{"type":"http","url":"https://eosl.ai/mcp"}}}{"mcpServers":{"ai-eosl-eosl":{"serverUrl":"https://eosl.ai/mcp"}}}Run commands in a terminal; paste JSON into the client’s MCP config and restart. Servers that need sign-in will prompt on first connect.
Tools
5| Parameter | Type | Required | Description |
|---|---|---|---|
| vendor | string | No | Optional vendor, e.g. "Cisco". A tracked vendor restricts the match to that vendor (a part tracked under another vendor returns found:false naming that vendor). A string that is not a tracked vendor is ignored and reported back as vendorHint. |
| part_number | string | Yes | Vendor part number / SKU, e.g. "WS-C3850-48P-S" or "FG-100F". |
Details
The maintainer has not added details yet. Check the README in the repository.
Comments
New to MCP?
From what the protocol is to installing your first server, these answers cover most first questions.
An open protocol that defines how AI applications connect to external tools and data in a uniform way. Clients talk to the model; MCP servers provide tools, resources and prompt templates. They exchange standard messages, so one server can be reused by many clients.