mcp-registry/io.github.foundrynet/cyber-intel-mcp/vulnerability_scan / alternatives

Live alternatives to mcp-registry/io.github.foundrynet/cyber-intel-mcp/vulnerability_scan

The best live alternatives to mcp-registry/io.github.foundrynet/cyber-intel-mcp/vulnerability_scan right now are mcp-registry/ai.dynamicfeed/dynamic-feed/exploited_vulnerabilities, mcp-registry/io.github.onefreeman1337/osf-data-marketplace/is_cve_exploited, mcp-registry/com.datanexusmcp/mcp-server/security_fetch_cve_risk_summary, mcp-registry/it.elsas/security-intel/check_cve, mcp-registry/io.github.foundrynet/oss-intel-mcp/dependency_risk — capability-matched and ranked by current reliability. mcp-registry/io.github.foundrynet/cyber-intel-mcp/vulnerability_scan itself is currently "healthy".

alternative	server
mcp-registry/ai.dynamicfeed/dynamic-feed/exploited_vulnerabilities	ai.dynamicfeed/dynamic-feed	live status →
mcp-registry/io.github.onefreeman1337/osf-data-marketplace/is_cve_exploited	io.github.onefreeman1337/osf-data-marketplace	live status →
mcp-registry/com.datanexusmcp/mcp-server/security_fetch_cve_risk_summary	com.datanexusmcp/mcp-server	live status →
mcp-registry/it.elsas/security-intel/check_cve	it.elsas/security-intel	live status →
mcp-registry/io.github.foundrynet/oss-intel-mcp/dependency_risk	io.github.FoundryNet/oss-intel-mcp	live status →
mcp-registry/io.github.getgapup/mcp-knowledge/cve_security_lookup	io.github.getgapup/mcp-knowledge	live status →
mcp-registry/io.github.getgapup/gapup-mcp/cve_security_lookup	io.github.getgapup/gapup-mcp	live status →
mcp-registry/io.github.foundrynet/financial-signals-mcp/anomaly_alert	io.github.FoundryNet/financial-signals-mcp	live status →
mcp-registry/io.github.foundrynet/weather-intel-mcp/supply_chain_risk	io.github.FoundryNet/weather-intel-mcp	live status →
mcp-registry/com.contrastcyber/api/cve_lookup	com.contrastcyber/api	live status →
mcp-registry/io.github.digitalweb33333-creator/x402-endpoints/cve_lookup	io.github.digitalweb33333-creator/x402-endpoints	live status →
mcp-registry/io.github.foundrynet/crypto-intel-mcp/anomaly_scan	io.github.FoundryNet/crypto-intel-mcp	live status →

FAQ

What is the best alternative to mcp-registry/io.github.foundrynet/cyber-intel-mcp/vulnerability_scan?

mcp-registry/ai.dynamicfeed/dynamic-feed/exploited_vulnerabilities is the top capability-matched alternative that's live right now. Other options: mcp-registry/io.github.onefreeman1337/osf-data-marketplace/is_cve_exploited, mcp-registry/com.datanexusmcp/mcp-server/security_fetch_cve_risk_summary, mcp-registry/it.elsas/security-intel/check_cve, mcp-registry/io.github.foundrynet/oss-intel-mcp/dependency_risk. Glimind ranks alternatives by semantic similarity and live health.

Is mcp-registry/io.github.foundrynet/cyber-intel-mcp/vulnerability_scan down right now?

mcp-registry/io.github.foundrynet/cyber-intel-mcp/vulnerability_scan's current verdict is "healthy". See its live status and score at https://glimind.com/tool/mcp-registry%2Fio.github.foundrynet%2Fcyber-intel-mcp%2Fvulnerability_scan.

How does Glimind pick alternatives?

By semantic capability match (what the tool does) filtered to tools that are healthy right now — from cross-ecosystem real usage. Neutral: Glimind sells no tools.

For agents

Get a live, capability-matched substitute in one call: GET https://glimind.com/v1/alternatives/mcp-registry%2Fio.github.foundrynet%2Fcyber-intel-mcp%2Fvulnerability_scan or MCP find_alternatives. Check mcp-registry/io.github.foundrynet/cyber-intel-mcp/vulnerability_scan's live status: https://glimind.com/tool/mcp-registry/io.github.foundrynet/cyber-intel-mcp/vulnerability_scan.