io.github.MRFrazer25/vulnerability-exposure-mcp

### Added
- `watchlist`: save the software you run once (typed or pasted, as for `am_i_affected`), and `check` reports only what changed since the last check: newly confirmed CVEs, CVEs newly added to CISA KEV, EPSS jumps of 10 points or more, and changed verdicts. A lookup that fails keeps the last good result to compare with. The list is one file in your own config folder, readable only by you.
- `vulnerability-exposure-mcp watch` runs the same check from a terminal and prints what changed, so Task Scheduler, cron or launchd can run it daily with no server. The README shows how for each OS.
- An opt-in disk cache (`VULN_EXPOSURE_CACHE=on`) for public data-source responses: NVD, CISA KEV, EPSS, Exploit-DB, CVE.org, endoflife.date and OSV advisories. Repeat checks in a new session are much faster (a Jenkins check went from 4 s to 0.7 s) and use less of NVD's rate limit. It's off by default, never stores keys or results, lives in the user's own cache folder (readable only by them), expires each entry after hours, is capped at 200 MB, and `vulnerability-exposure-mcp cache status` / `cache clear` show and empty it. Each file is signed with a key kept in your OS credential store, so a file that was edited or moved is fetched again rather than trusted, and the KEV catalog is kept for an hour, so a CVE CISA adds shows up the same morning.

### Changed
- `check_report` also checks claims about the host against its lookups: open ports, VirusTotal and AbuseIPDB counts, a Spamhaus listing and host names no lookup returned. It catches "no public exploit" when Exploit-DB has one, checks "X isn't in KEV, but Y is" clause by clause, and flags a table's fix cell that leaves out "after". A product named with a version no lookup returned ("runs OpenSSH 9.6p1") is flagged wherever it sits, and so is a sentence quoting a source that returned nothing ("GreyNoise shows it doesn't scan" when GreyNoise hit its limit), unless it says the source wasn't checked.
- CVEs NVD says apply only on a specific platform or with a component (CVE-2024-4577: PHP on Windows) say so, with the platform. A build the input says runs on Linux or Unix (an Ubuntu package, "(Ubuntu)" in a banner) has Windows-only CVEs ruled out, whether you ask about every CVE or one. Key facts mark a confirmed KEV or ransomware CVE that needs a platform. These rules were being dropped when NVD records were trimmed.
- The most likely confirmed CVEs carry their EPSS trend over the last 30 days, and ones whose exploitation likelihood jumped are listed as `epss_rising` and in key facts.
- A weekly workflow calls every keyless data source the way the server does (`scripts/health_check.py`) and opens an issue when one fails or changes shape, so an upstream format change is caught before users hit it. It uses no API keys, only a separate job can write issues, and a manual "simulate failure" run tests the issue step.

### Security
- CVE descriptions from NVD and CISA KEV's text fields are cleaned of instruction-like text before the model sees them, like banners and advisories already were. Tests plant prompt-injection text in every outside source (NVD, KEV, OSV, endoflife.date, CVE records, InternetDB) and check it never reaches the model as an instruction.

### Fixed
- Plugin and extension CVEs (36 for Jenkins 2.440) no longer count as the product's own "needs review" CVEs; they're listed separately as `plugin_cves_not_counted`.
- A product with more NVD candidates than were read (Windows 10 22H2 has about 3,456) says how many were checked and that its counts are a minimum. With an NVD key, up to 4,000 are read instead of 1,000.
- "Citrix ADC", NetScaler's former name, maps to NetScaler.
- `am_i_affected` items say which Windows release a build number was mapped to, and Windows 10 and 11 releases get end-of-life dates from endoflife.date (Home and Pro dates, with a note that other editions and paid extended updates last longer).
- When a Linux or Unix build rules out Windows-o