For developers: free MCP tools

Facts your coding agent can check before it ships

Four MCP servers answer CVE, package, version and citation questions from public records, with the date they were read. No key, no sign-up and nothing to install.

Install dev-security See the 4 tools

claude plugin marketplace add nguyenhieuec/agent-tools-plugins
claude plugin install dev-security@openkrill

The 4 tools

CVE

CVE Risk Check

Priority for one CVE or a whole lock file: the CISA exploited list, the EPSS score and the version that fixes it.

Is lodash 4.17.15 vulnerable?

Package

Package Health Check

One npm or PyPI package: latest version, deprecation notice, last release, licence and known advisories.

Is the npm package request still maintained?

Version

Dev Facts Check

End-of-life dates, licence facts, browser support and RFCs, each with its source and read date.

When does Node.js 20 reach end of life?

Citation

Citation Checker

References checked against DOI.org, Crossref and OpenAlex: found, wrong, retracted or not found.

Is this DOI real, and is the paper retracted?

Try these 3 prompts

Real answers from the live servers, read on 2026-10-09. Ask again for a newer reading.

"Is lodash 4.17.15 vulnerable, and which version fixes it?"

check_package

Yes: 6 advisories, such as CVE-2021-23337, which is high. Upgrade to 4.18.0.

Source: OSV.dev, npm registry. Read 2026-10-09.
"Is the npm package request still maintained?"

check_package

No. It is deprecated; the last release, 2.88.2, came out on 2020-02-11, and it has 1 moderate advisory (CVE-2023-28155).

Source: npm registry, deps.dev, OSV.dev. Read 2026-10-09.
"Is Node.js 20 still supported?"

get_eol_status

No. Node.js 20 reached end of life on 2026-04-30. The supported LTS lines are 24, to 2028-04-30, and 22, to 2027-04-30.

Source: endoflife.date. Read 2026-10-09.

Install

Claude Code: dev-security brings CVE Risk Check, Package Health Check and Dev Facts Check, each with a skill that says when to use it. Add Citation Checker on its own line.

claude plugin marketplace add nguyenhieuec/agent-tools-plugins
claude plugin install dev-security@openkrill
claude mcp add --transport http citations https://citations.openkrill.app/mcp

Cursor, and any client that reads an mcp.json: merge these four servers into .cursor/mcp.json or ~/.cursor/mcp.json.

{
  "mcpServers": {
    "cve": { "url": "https://cve.openkrill.app/mcp" },
    "packages": { "url": "https://packages.openkrill.app/mcp" },
    "dev-facts": { "url": "https://devfacts.openkrill.app/mcp" },
    "citations": { "url": "https://citations.openkrill.app/mcp" }
  }
}

Start a new session and ask the first prompt above. ChatGPT, Claude on the web and Pi have their own steps: open the guide for CVE Risk Check in ChatGPT, CVE Risk Check in Claude or CVE Risk Check in Pi.

Using it in production

The servers run on our side over streamable HTTP. No package, no Python or Node.js version and no environment variable.

Rate limit	60 tool calls a minute from one network, per server
Daily cap	One cap per server, shared by every caller, reset at 00:00 UTC
At a limit	A tool error that starts with `rate_limited` or `daily_limit`
Key	None
Higher limits	Email support@openkrill.app with the server and calls a day
SLA	None yet

What each server receives and keeps is on the privacy page. The tools cannot tell whether your code reaches a vulnerable function, and a package with no known advisory can still be unsafe.

Want a person to do it?

The Dependency report runs these tools on one repo's lock file, and a person sends a ranked fix list: 99 USD per repo, paid through escrow.