OffSeq Threat Radar status
Answered our latest tool-list check 4 hours ago with 12 tools. It will be marked verified after 3 successful checks in 7 days.
- Answered (30 days)
- 2 of 2 checks
- Last seen working
- 17 Nov, 06:16 UTC
- Last commit
- —
- Licence
- Not stated
Live checks
We call this hosted server's tools/list endpoint without credentials, from the public internet, every day while it answers and weekly otherwise.
- Answered
- Needs sign-in
- No answer
| Checked (UTC) | Result | Response time | Tools |
|---|---|---|---|
| 17 Nov, 06:16 | Answered | 2.2 s | 12 |
| 16 Nov, 00:17 | Answered | 2.1 s | 12 |
Tools (12)
Read from the server on 17 Nov 2026.
- search_threats
- Search OffSeq Radar's vulnerability and threat corpus (CVE records, CISA KEV, ENISA EUVD, EPSS, public exploits, news). Combine filters to answer questions like "exploited Fortinet CVEs this month" or "critical CVEs with rising EPSS". Results carry priority, KEV, EPSS, exploit maturity and EUVD signals. Use get_threat for one record in full.
- get_threat
- One vulnerability or threat record by CVE id (e.g. CVE-2024-3400) or Radar slug, resolved to the authoritative record: CVSS, priority with its factors, CISA KEV, EPSS with 30-day history, exploit maturity and sources, ENISA EUVD, OffSeq Mirage, source consensus, affected versions and remediation.
- match_packages
- Check installed packages against known vulnerabilities with ecosystem-native version comparison (distro backports included). Each package is a purl with version (pkg:npm/lodash@4.17.20, pkg:deb/debian/openssl@3.0.11-1~deb12u2?distro=bookworm), or name + ecosystem + version, or a CPE. Returns per package the matches, the smallest fixing version (upgradeTo) and CVEs with no fix (unfixed).
- scan_sbom
- Scan a whole SBOM or lockfile for vulnerable dependencies, riskiest first, with upgrade advice per package. Formats: cyclonedx-json, spdx-json, package-lock, composer-lock, cyclonedx-xml, spdx-tag-value, yarn-lock, pnpm-lock, cargo-lock, uv-lock, poetry-lock, gemfile-lock, go-mod, go-sum, purl-list, requirements. Pass the file text as content and its filename so the format is detected. failOn eval
- prioritize_cves
- Rank 2 to 50 CVEs into a patch order using Radar's priority score (CVSS, EPSS, CISA KEV, ransomware, exploit maturity, exploited but not in CISA KEV). Each row says why it ranks above the next; patterns group CVEs sharing a product, vendor or weakness.
- check_iocs
- Look up indicators of compromise (IP addresses, domains, URLs, file hashes) in the indicators Radar extracted from threat reports. Matching is a case-insensitive substring match per indicator type; up to 5 threats per indicator.
- get_landscape
- What changed across the vulnerability landscape in a window: CISA KEV additions, exploitation not in KEV (ENISA EUVD, OffSeq Mirage), new public exploits, EPSS risers and new critical CVEs, plus CVEs that several of those name (multiSignal). Each panel cites its source and as-of time.
- list_changes
- Your "What changed" feed: new signals (KEV listing, EPSS jump, exploit published, EUVD exploited, fix available...) on CVEs you starred or that affect your monitored hosts, plus decisions that went stale, expired or are due for review. Newest first.
- list_hosts
- Hosts in your Radar inventory (registered by the threat-finder CLI) with each host's cached finding summary and an account-wide aggregate. Use list_host_findings for one host's findings.
- list_host_findings
- Current vulnerability findings for one of your hosts, riskiest first, with exposure, KEV, EPSS, fix versions and any decision you recorded. Get hostId from list_hosts.
- list_decisions
- Your decision ledger: what you decided per CVE (patch_now, defer, accept, not_affected, mitigated), the assumptions behind it, and whether it still holds (active, review_due, expired, stale when a signal broke an assumption).
- record_decision
- Record a decision about a CVE in your ledger. Radar re-checks the assumptions as signals change and flags the decision stale when one breaks. Verdicts: patch_now, defer (needs until), accept, not_affected and mitigated (take a VEX justification). Assumptions that do not hold today are rejected. Confirm the verdict with the user before calling; this writes to their account.