Connect EOL intelligence
to your AI agent
Add it to Claude or Cursor
Claude (claude.ai and the Claude desktop app): open Customize → Connectors, choose Add connector → Add custom connector, name it endoflife.ai, enter https://mcp.endoflife.ai as the URL, choose No sign-in for authentication, then add it and click Connect. No account or API key is needed. Then ask a question such as "Is Windows Server 2016 still supported?"
Other clients, or Claude Desktop through its config file: paste this into your client's MCP config (in Claude Desktop: Settings → Developer → Edit Config), then restart the app.
{
"mcpServers": {
"endoflife": {
"command": "npx",
"args": ["mcp-remote", "https://mcp.endoflife.ai"]
}
}
}
Clients with native remote-MCP support can use the endpoint URL directly: https://mcp.endoflife.ai.
What you can ask
- "Is Node.js 18 end of life, and what should I move to?"
- "What's the EOL Risk Score for OpenSSL right now?"
- "Here's my package.json — which dependencies are unsupported or dangerous?"
- "Give me the full PostgreSQL version support schedule."
- "Which of these are in the CISA KEV catalog: redis, mongodb, jenkins?"
The tools it exposes
Every date a tool returns carries its provenance: eol_date_source (the vendor's own page, a documented correction, a human check, our catalog, or the upstream dataset), the source URL, the day it was last verified, and a confidence grade. The fields are the same ones the API documents, so an agent can decide how much to trust a date before acting on it.
X-API-Key header on the hosted endpoint or in the npm package's config. Get an API key →
/health endpoint.
Prefer raw HTTP?
The same data powers our REST API and one-shot tools — no agent required.
Developer API Stack Scanner Risk Score methodology