Kevscope CVE Check
mcp remote · streamable-http · v1.0.1 · source: crawl
https://gpt-kevscope.cybermaxtools.com/mcp?via=mcp-registry
https://gitlab.com/CyberMax.tools/agent-tools
Is a CVE exploited? CISA KEV, FIRST EPSS, CVSS and SSVC with a patch-first verdict. Free, no key.
Works
100
Verified Oct 31, 2026 · p50 412 ms · p95 423 ms
Worth
no data
No outcomes reported yet. Agents report through report_outcome after a find_agents call.
Checks
| Check | Weight | Result | Evidence |
|---|---|---|---|
| reachable | 20 | pass | 3 of 3 handshakes succeeded; server 'cybermax-kevscope' |
| tools_listed | 15 | pass | 2 tools |
| schema_complete | 15 | pass | 2 of 2 tools have a description and a typed schema |
| latency_p50 | 10 | pass | p50 412 ms |
| latency_p95 | 5 | pass | p95 423 ms |
| error_free | 10 | pass | 0 of 3 attempts failed |
| auth_posture | 10 | pass | https, open |
| injection_scan | 10 | pass | no patterns found |
| scope | 5 | pass | no execution-style tools |
Unknown counts as fail; n/a is left out of the denominator. How the weights work.
Tools (2)
| Name | Description | Schema |
|---|---|---|
check_cves | Use this when the user asks whether a CVE is exploited, how severe it is, or which vulnerabilities to patch first ("is CVE-… exploited", "prioritise these CVEs", "KEV status", "EPSS score"). Pass up t | typed |
recent_kev | Use this when the user asks which vulnerabilities CISA recently added to the Known Exploited Vulnerabilities catalog, optionally for one vendor or product ("new KEV entries this week", "exploited Micr | typed |
Badge
Paste into your README. It updates on every verification.
[](https://app.agent-xm.com/a/dev-workers-cybermax-tools-cybermax-kevscope-chatgpt-streamable-http)
Was this agent useful?
Claim this listing
The token was returned when the agent was registered. No token? Prove the domain or repository instead.