# Dev Facts Check

Get end-of-life dates, license facts, browser support and RFC status. It is free, with no sign-up and no key.

## What it does

Check the facts a developer asks for again and again: when a software version reaches end of life, whether the runtimes a repository pins are still supported, what an open-source license is, whether a web feature works in a browser, what an RFC says about itself and what changed between two versions of a package.

Ask "is Node.js 20 still supported?", "is anything in this repo past end of life?", "is the MIT license OSI approved?", "can I use CSS container queries in Safari?", "which RFC obsoletes RFC 2616?" or "what changed in express between 4.18.2 and 5.1.0?".

For a repository, pass the files that pin runtimes (package.json, .nvmrc, .python-version, pyproject.toml, go.mod, a Dockerfile or compose file, .tool-versions, mise.toml, .ruby-version, a Gemfile, composer.json or global.json) and get one row per runtime with its end-of-life date, days left, latest patch and the next supported cycle.

It reads five public sources: endoflife.date for release cycles and support dates, the SPDX License List for license identifiers and OSI and FSF status, webstatus.dev for Baseline status and the first browser version that supports a web feature, the RFC Editor and IETF Datatracker for RFC status, abstracts and obsoleting links, and GitHub releases and changelog files for the notes of each release in a version range.

Every answer names its source and the date of the data. endoflife.date is maintained by volunteers, so confirm a date with the vendor before a contract or compliance decision. A license answer identifies a license and does not say what it lets you do: it is not legal advice.

It does not scan packages for vulnerabilities or health: use the Package Health Check plugin for that.

It stores nothing about you: answers are cached for a few hours and the only lasting record is a daily count of calls per tool.

- Shows whether a version of a product has reached end of life, with its end-of-life and LTS dates
- Lists the release cycles of a product that are still supported, newest first, with the latest patch
- Reads the runtime pins in a repo (Node.js, Python, Go, Ruby, PHP, .NET, Docker images) and flags any past end of life
- Looks up an SPDX license by identifier or name: OSI approved, FSF free, deprecated or not
- Shows the first release of each major browser that supports a web feature, and its Baseline status
- Looks up an RFC by number or title words: status, abstract, and the RFCs that obsolete or update it
- Lists the GitHub release notes of an npm or PyPI package between 2 versions and flags breaking changes
- Names the source and the date of its data in every answer

## Who it is for

Anyone who asks an AI assistant a question like this one: “When does Node.js 20 reach end of life?”

Roles that use it at work: Software developer, Engineering manager.

Role guides that use it: [Software developer](https://tools.openkrill.app/for/software-developer).

## Price

Dev Facts Check is free to use. There is no sign-up, no account and no API key. Calls are limited to 60 calls a minute per network and 5000 calls a day per server, shared by all callers. Repeat questions are answered from a cache.

## Tools it offers

- `get_eol_status`: Get end-of-life status
- `check_runtime_eol`: Check runtime end of life
- `check_license`: Check a license
- `check_browser_support`: Check browser support
- `lookup_rfc`: Look up an RFC
- `get_release_notes`: Get release notes

## Connect

The MCP server is `https://devfacts.openkrill.app/mcp` (streamable HTTP). It needs no key.

Claude Code, in one command:

```
claude mcp add --transport http dev-facts https://devfacts.openkrill.app/mcp
```

Hermes Agent, in one command that answers its two setup questions (no key, enable all tools):

```
printf 'n\ny\n' | hermes mcp add dev-facts --url https://devfacts.openkrill.app/mcp
```

Or add these lines to `~/.hermes/config.yaml`, under an existing `mcp_servers:` key if the file has one. Start a new Hermes session after either step.

```
mcp_servers:
  dev-facts:
    url: https://devfacts.openkrill.app/mcp
```

Any other agent: give it this page's Markdown address, `https://tools.openkrill.app/tools/dev-facts.md`, and ask it to connect Dev Facts Check.

Install guides, each checked with a real call: [Dev Facts Check in ChatGPT](https://tools.openkrill.app/integrations/dev-facts/chatgpt), [Dev Facts Check in Claude](https://tools.openkrill.app/integrations/dev-facts/claude), [Dev Facts Check in Cursor](https://tools.openkrill.app/integrations/dev-facts/cursor), [Dev Facts Check in VS Code](https://tools.openkrill.app/integrations/dev-facts/vscode), [Dev Facts Check in Pi](https://tools.openkrill.app/integrations/dev-facts/pi).

## Job recipes for agents

Step-by-step recipes that walk an agent through 3 jobs with this server's tools:

- Get end-of-life status, with `get_eol_status`
- Get release notes, with `get_release_notes`
- Check a license, with `check_license`

[Download the recipes as SKILL.md](https://tools.openkrill.app/skills/dev-facts-jobs/SKILL.md). Save it as `dev-facts-jobs/SKILL.md` in your agent's skills folder. A connected MCP client gets the same recipes from `prompts/list` on the gateway, `https://api.openkrill.app/gateway/mcp`.

It is listed under Code and security in the [full tool list](https://tools.openkrill.app/tools). The same facts in plain text are in [llms.txt](https://tools.openkrill.app/llms.txt).

Source: the Dev Facts Check listing, version 1.3.0. As of 2026-10-18.