
EOL, licences, browsers, RFCs
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?".
Example path
https://devfacts.openkrill.app/mcpDev Facts Check: EOL, licences, browsers, RFCs. Use these tools for developer reference facts: for support and end-of-life dates of a software product or version, for the runtime versions a repository pins when you have its files open (package.json, .nvmrc, .python-version, pyproject.toml, go.mod, Dockerfile, .tool-versions and similar) or for runtimes named by version, such as node 18 and python 3.8, for an SPDX license's identifier and OSI or FSF status, for Baseline status and browser versions of a web platform feature, for an RFC by number or by words in its title, and for what changed in a package or GitHub repository between the version the user has and a newer one. Pass one product, license, feature or RFC per call; takes all the pin files of a repository in one call, with each file's name and contents, and a row with status unmatched names its reason: say which pin could not be checked instead of guessing its date. When returns complete false, say the notes are partial and give compareUrl. When a result has status not_found, ambiguous or version_not_found, read error.hint and the candidates, then call again with one of them instead of guessing. Always give the source and asOf date with the answer. endoflife.date is community maintained: say so when the answer drives a decision. A license answer is not legal advice and says nothing about what a license permits. Do not use these tools for package vulnerabilities or package health: say this plugin does not cover them. This server allows 60 tool calls a minute per network and 5,000 a day for all callers together; the day count resets at 00:00 UTC. If a tool fails, gives a wrong answer, or a tool you need is missing, call with one short message (kind, message, tool); reads the answer.
None in the store listings or on the server