CVE Risk Check

Name: CVE Risk Check
Author: app.openkrill

MCP serverMCP

Triage a CVE: how severe it is, whether it is exploited, and how likely exploitation is.

by app.openkrillhomepage ↗v1.0.0

Is this yours?

This record is unclaimed

Wellknown found it in public sources; nobody has proven control of it yet. Claiming takes one click if the repository is under your GitHub account, or a small file on your domain otherwise. Verified owners get the badge, 15-minute checks, status alerts, edits that outrank crawled data, and a ranking boost.

Agents can do it too: POST https://wellknown.network/api/v1/claims with {"agent":"cve-risk-check","method":"well_known_file"} — machine-readable steps at claim.json, guide at /docs/claim.

Claim this record

Observed by Wellknown

Evidence

Everything here was measured by our prober or read from a registry. Nothing is self-reported.

30-day availability15/15 checks ok

30 days ago

when	check	result	http	latency	detail
5 h ago	mcp initialize	ok	200	73 ms	server cve 1.0.0 · protocol 2025-06-18 · 6 tools
11 h ago	mcp initialize	ok	200	44 ms	server cve 1.1.0 · protocol 2025-06-18 · 7 tools
17 h ago	mcp initialize	ok	200	57 ms	server cve 1.1.0 · protocol 2025-06-18 · 7 tools
24 h ago	mcp initialize	ok	200	28 ms	server cve 1.1.0 · protocol 2025-06-18 · 7 tools
31 h ago	mcp initialize	ok	200	44 ms	server cve 1.1.0 · protocol 2025-06-18 · 7 tools
2 d ago	mcp initialize	ok	200	33 ms	server cve 1.1.0 · protocol 2025-06-18 · 7 tools
2 d ago	mcp initialize	ok	200	8 ms	server cve 1.1.0 · protocol 2025-06-18 · 7 tools
2 d ago	mcp initialize	ok	200	21 ms	server cve 1.1.0 · protocol 2025-06-18 · 7 tools
2 d ago	mcp initialize	ok	200	28 ms	server cve 1.1.0 · protocol 2025-06-18 · 7 tools
3 d ago	mcp initialize	ok	200	348 ms	server cve 1.1.0 · protocol 2025-06-18 · 7 tools

Tools observed via MCP handshake

check_cve — Use this when the user asks how serious a CVE is, such as "how bad is CVE-2021-44228?". Pass the CVE id. Returns a priority (exploited, likely, routine or unkno
check_cves — Rank several CVEs. Use this when the user has a list of CVE ids and wants to know which to deal with first, such as "which of these CVEs should I patch first?".
list_recent_kev — Use this when the user asks what CISA recently added to its Known Exploited Vulnerabilities list, such as "what exploited CVEs were added this month?". Optional
submit_feedback — Send feedback to the maintainers about a missing tool, broken links, a bug, or stale data. Use this to send feedback, a bug report or a feature request to the m
get_feedback_reply — Read the feedback reply for a ticket from submit_feedback. Use this to read the maintainers' reply to feedback you sent with submit_feedback, given its ticket i
index_tools — LinkedIn recruiter jobs feedback broken links: search openkrill MCP tools by task. Use this to find a tool for recruiter search, LinkedIn keywords, jobs, feedba

Declared by sources

What the publisher says

Attributed to the source that supplied each field. Treated as claims, not facts.

No long description beyond the summary.

kind Official MCP Registry

name Official MCP Registry

summary Official MCP Registry

version Official MCP Registry

description Official MCP Registry

homepageUrl Official MCP Registry

publisherName Official MCP Registry

Provenance

Where this record came from

Every source is kept verbatim. Field changes are logged as events.

Official MCP Registryapp.openkrill/cve

first seen 4 d ago · fetched 25 h agoopen ↗

Field history (6 recent events)

4 d ago · declared · summary → "Triage a CVE: how severe it is, whether it is exploited, and how likely exploitation is."
4 d ago · declared · description → "Triage a CVE: how severe it is, whether it is exploited, and how likely exploitation is."
4 d ago · declared · publisherName → "app.openkrill"
4 d ago · declared · homepageUrl → "https://tools.openkrill.app/"
4 d ago · declared · version → "1.0.0"
4 d ago · declared · protocols → ["mcp"]

This record is unclaimed

Evidence

What the publisher says

Capabilities

Where this record came from