INDIVIDUAL MCP TOOL
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 Microsoft vulnerabilities this month", "ransomware-linked CVEs").
LIVE ENDPOINT
https://gpt-kevscope.cybermaxtools.com/mcp?via=mcp-registry
Connect to this endpoint to inspect the live schema for recent_kev and invoke it with your own arguments.
Indexed input schema
{}Risk classification
Inferred read-only · medium confidence · heuristic, not a guarantee.
- No write-capable action terms were found; this is not proof that invocation has no side effects.
Parent server
CONNECT WITH APPROVAL
Client installation
Review this server and its permissions before adding it. Secret placeholders must be set locally.
Codex
~/.codex/config.toml
[mcp_servers.cybermax-kevscope]
url = "https://gpt-kevscope.cybermaxtools.com/mcp?via=mcp-registry"
enabled = true
Claude Code
.mcp.json
{
"mcpServers": {
"cybermax-kevscope": {
"type": "http",
"url": "https://gpt-kevscope.cybermaxtools.com/mcp?via=mcp-registry"
}
}
}
Claude Desktop
Settings → Connectors → Add custom connector
Name: cybermax-kevscope
Remote MCP URL: https://gpt-kevscope.cybermaxtools.com/mcp?via=mcp-registry
Add this remote URL as a custom connector in Claude Desktop. Availability depends on the user plan and workspace policy.
Cursor
.cursor/mcp.json
{
"mcpServers": {
"cybermax-kevscope": {
"url": "https://gpt-kevscope.cybermaxtools.com/mcp?via=mcp-registry"
}
}
}
Visual Studio Code
.vscode/mcp.json
Add to Visual Studio Code{
"servers": {
"cybermax-kevscope": {
"type": "http",
"url": "https://gpt-kevscope.cybermaxtools.com/mcp?via=mcp-registry"
}
}
}
Generic MCP
Client-specific MCP configuration
{
"name": "cybermax-kevscope",
"transport": "streamable-http",
"url": "https://gpt-kevscope.cybermaxtools.com/mcp?via=mcp-registry"
}
MCP Inspector
Run the official MCP Inspector locally and enter the indexed Streamable HTTP endpoint.
Related tools
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").