CISA KEV Ransomware CVE, SSL CT Logs & Domain Recon
Audit active CISA KEV ransomware CVEs, SSL/TLS CT log subdomains, SPF/DMARC security & ICANN RDAP.
What it does
CISA KEV Ransomware CVE, SSL CT Logs & Domain Recon is an MCP server, a connector that lets an AI assistant use it as a tool. It is hosted: an assistant connects to it over the internet, nothing to install.
From the publisher's description, Electra Index matched it to one capability: security scanning. That makes it a candidate for tasks such as review pull requests or scan code for vulnerabilities.
Facts come from the Official MCP Registry, as declared by the publisher. Capabilities are matched automatically (low confidence). None of this is a test of the tool.
At a glance
How to connect
As declared in the Official MCP Registry · not tested by Electra IndexHosted endpoint
https://mcp.apify.com/?actors=b2b-quant-apis/cisa-kev-ransomware-vulnerability-auditor,b2b-quant-apis/b2b-ssl-tls-ct-log-subdomain-attack-surface-auditor,b2b-quant-apis/global-b2b-email-domain-security-auditor,b2b-quant-apis/icann-rdap-domain-whois-brand-reconstreamable-http
In Claude Code: claude mcp add --transport http cisa-kev-ransomware-cve-ssl-ct-logs-domain-recon https://mcp.apify.com/?actors=b2b-quant-apis/cisa-kev-ransomware-vulnerability-auditor,b2b-quant-apis/b2b-ssl-tls-ct-log-subdomain-attack-surface-auditor,b2b-quant-apis/global-b2b-email-domain-security-auditor,b2b-quant-apis/icann-rdap-domain-whois-brand-recon
MCP settings (Claude Desktop, Cursor and other MCP clients)
{
"mcpServers": {
"cisa-kev-ransomware-cve-ssl-ct-logs-domain-recon": {
"url": "https://mcp.apify.com/?actors=b2b-quant-apis/cisa-kev-ransomware-vulnerability-auditor,b2b-quant-apis/b2b-ssl-tls-ct-log-subdomain-attack-surface-auditor,b2b-quant-apis/global-b2b-email-domain-security-auditor,b2b-quant-apis/icann-rdap-domain-whois-brand-recon"
}
}
}Live check
Electra Index connected to the hosted endpoint 2h agoREACHABLE The endpoint answered but asks for an API key or a sign-in before connecting. Electra Index never sends credentials, so the tool list is not visible here.
What "online" means: the server answered an MCP connection at the time of the check. It is not a guarantee of security, quality or continuous uptime. How we test: we open an MCP session and ask for the tool list, as an AI assistant would. We never run a tool and never send a key. Checked every few days. Method
Is this your server? Monitoring Pro: a check every 30 minutes and an email within the hour when it stops answering. Launch offer: $39.99 once, for life.
Tasks it helps with
Share of each task's required capabilities it covers| Review pull requests Security Scanning | 50% |
| Scan code for vulnerabilities Security Scanning | 50% |
Similar tools
Listed for the same task: review pull requests- diffpilotREMOTELOCALMCP server for PR code review, commit messages, changelogs, and secret detection
- MCP Code Review ServerREMOTELOCALCode review as an MCP server — structured reviews with OWASP security scanning
- StrixREMOTELOCALAI pentesting: run scans, triage vulnerabilities, review PRs, manage schedules and assets
- LazarettoREMOTELOCALFree lockfile malware check plus paid behavioral scan of packages, agent skills and MCP tools
- Radar Agent ToolsREMOTELOCALNo-key tools: web page to Markdown, WHOIS/DNS/SSL, Federal Register, clinical trials, odds, CVEs
- DraugrREMOTELOCALSecurity scanning for AI agents: SAST, SCA, secrets, IaC, DAST, ranked by real risk
Ready-made AI agents
- $20/mo · Prices & score →
- $18/mo · free plan · Prices & score →
- $24/mo · free plan · Prices & score →
- Tessl45$100/mo · free plan · Prices & score →
Facts & evidence
Each fact shows where it was seen and when.| Fact | Value | Evidence | Source | Last confirmed |
|---|---|---|---|---|
| Hosted endpoint | https://mcp.apify.com/?actors=b2b-quant-apis/cisa-kev-ransomware-vulnerability-auditor,b2b-quant-apis/b2b-ssl-tls-ct-log-subdomain-attack-surface-auditor,b2b-quant-apis/global-b2b-email-domain-security-auditor,b2b-quant-apis/icann-rdap-domain-whois-brand-recon | DECLARED | SRC-001 Official MCP Registry | 2h ago |
| Local install (package) | no | DECLARED | SRC-001 Official MCP Registry | 2h ago |
| Remote access (hosted) | yes | DECLARED | SRC-001 Official MCP Registry | 2h ago |
| Website | https://jesleytassili-glitch.github.io/b2b-quant-mcp-n8n-suite/actors/cisa-kev-ransomware-vulnerability-auditor.html | DECLARED | SRC-001 Official MCP Registry | 2h ago |
| Repository | https://github.com/jesleytassili-glitch/b2b-quant-mcp-n8n-suite | DECLARED | SRC-001 Official MCP Registry | 2h ago |
| Registry status | active | DECLARED | SRC-001 Official MCP Registry | 2h ago |
| Version | 1.0.0 | DECLARED | SRC-001 Official MCP Registry | 2h ago |
| MCP server | yes | DECLARED | SRC-001 Official MCP Registry | 2h ago |
Change history
- NEW02 Nov 2026first seen in the index
Is this page accurate?
Flag it and our robot re-checks the official source. Reports never change a score.Is CISA KEV Ransomware CVE, SSL CT Logs & Domain Recon still online?
Free alerts · no account▲ 0Do you run CISA KEV Ransomware CVE, SSL CT Logs & Domain Recon? Know when it stops answering
For publishers · optionalIts hosted endpoint can be monitored. Monitoring Pro connects every 30 minutes like an AI assistant, emails you within the hour when it stops answering, keeps a 90-day availability history and adds your answer rate to your badge.
Monitoring never changes a score or a rank.
Questions about CISA KEV Ransomware CVE, SSL CT Logs & Domain Recon
How do I connect CISA KEV Ransomware CVE, SSL CT Logs & Domain Recon?
Use the hosted endpoint https://mcp.apify.com/?actors=b2b-quant-apis/cisa-kev-ransomware-vulnerability-auditor,b2b-quant-apis/b2b-ssl-tls-ct-log-subdomain-attack-surface-auditor,b2b-quant-apis/global-b2b-email-domain-security-auditor,b2b-quant-apis/icann-rdap-domain-whois-brand-recon in your assistant's MCP settings. The exact settings are in "How to connect" above, as declared in the Official MCP Registry.
What can I use CISA KEV Ransomware CVE, SSL CT Logs & Domain Recon for?
Based on its description, it is most relevant to: review pull requests, scan code for vulnerabilities.