endoflife.ai — Software Lifecycle Intelligence MCP server

endoflife.ai — MCP Server

Exposes endoflife.ai's lifecycle intelligence to AI agents over the Model Context Protocol (MCP, Streamable HTTP transport). A dependency-free Cloudflare Worker that wraps the public api.endoflife.ai/v1 endpoints and the site's published feeds — no data duplicated, every answer carries a source URL.

Current version: 1.3.0 (SERVER_INFO.version in src/index.js, server.json, package.json — keep all three in step; CI fails if they disagree; the registry and Glama read server.json).

Tools (all read-only)

Every tool advertises annotations (readOnlyHint, idempotentHint) and a permissive outputSchema; results are returned both as JSON text and as structuredContent. Lookup misses return "did you mean" slug suggestions (prefix / substring / edit-distance ≤ 2 against the live product list).

Resources (resources/list / resources/read): llms.txt, the EOS Edge Device feed, Exploited & Unpatchable, KEV by product, the edge change log.

Prompts (prompts/list / prompts/get): auditstack, eolcalendar, edgedevicereview.

Endpoints: POST / (JSON-RPC), GET / (info page), GET /health (liveness JSON), GET /.well-known/mcp/server-card.json (discovery card).

Usage telemetry

With the USAGE Analytics Engine binding (see wrangler.toml, dataset endoflifemcpusage) each method / tool call writes one data point: tool name, client user agent, ok/error, keyed/anon, latency in ms. No request bodies. Query via the Cloudflare Analytics Engine SQL API, e.g.

SELECT blob1 AS tool, count() AS calls, sum(_sample_interval) AS weighted
FROM endoflife_mcp_usage WHERE timestamp > NOW() - INTERVAL '7' DAY
GROUP BY tool ORDER BY calls DESC

The binding is optional; the code no-ops without it.

Deploy

The hosted server at mcp.endoflife.ai is deployed by the maintainers from the endoflife.ai site repository's GitHub Actions workflow (pinned wrangler, Cloudflare credentials held there as repository secrets); this public repository carries no deploy workflow of its own. To run your own copy, wrangler deploy from this repository works with your own Cloudflare account, and wrangler dev runs it locally; the API service binding and the USAGE dataset in wrangler.toml are declared for both the default and production environments.

Shortened. The full README is on GitHub.