mcp-registry/io.github.pipeworx-io/epss/top_exploited / alternatives

Live alternatives to mcp-registry/io.github.pipeworx-io/epss/top_exploited

The best live alternatives to mcp-registry/io.github.pipeworx-io/epss/top_exploited right now are mcp-registry/io.github.blackboxfoundry/livedatalink/epss_score, mcp-registry/io.github.getgapup/mcp-knowledge/vuln_exploitability_forecast, mcp-registry/io.github.getgapup/gapup-mcp/vuln_exploitability_forecast, mcp-registry/com.datanexusmcp/mcp-server/security_fetch_cve_epss, mcp-registry/io.github.megabrainee/sectora/get_trending_cves — capability-matched and ranked by current reliability. mcp-registry/io.github.pipeworx-io/epss/top_exploited itself is currently "healthy".

alternativeserver
mcp-registry/io.github.blackboxfoundry/livedatalink/epss_scoreio.github.blackboxfoundry/livedatalinklive status →
mcp-registry/io.github.getgapup/mcp-knowledge/vuln_exploitability_forecastio.github.getgapup/mcp-knowledgelive status →
mcp-registry/io.github.getgapup/gapup-mcp/vuln_exploitability_forecastio.github.getgapup/gapup-mcplive status →
mcp-registry/com.datanexusmcp/mcp-server/security_fetch_cve_epsscom.datanexusmcp/mcp-serverlive status →
mcp-registry/io.github.megabrainee/sectora/get_trending_cvesio.github.megabrainee/sectoralive status →
mcp-registry/com.datanexusmcp/mcp-server/security_fetch_cve_risk_summarycom.datanexusmcp/mcp-serverlive status →
mcp-registry/ai.dynamicfeed/dynamic-feed/exploited_vulnerabilitiesai.dynamicfeed/dynamic-feedlive status →
mcp-registry/io.github.getgapup/mcp-knowledge/vuln_patch_priority_engineio.github.getgapup/mcp-knowledgelive status →
mcp-registry/io.github.getgapup/gapup-mcp/vuln_patch_priority_engineio.github.getgapup/gapup-mcplive status →
mcp-registry/io.github.onefreeman1337/osf-data-marketplace/is_cve_exploitedio.github.onefreeman1337/osf-data-marketplacelive status →
mcp-registry/io.tooloracle/cybershield/cve_risk_scoreio.tooloracle/cybershieldlive status →
mcp-registry/com.contrastcyber/api/exploit_lookupcom.contrastcyber/apilive status →

FAQ

What is the best alternative to mcp-registry/io.github.pipeworx-io/epss/top_exploited?

mcp-registry/io.github.blackboxfoundry/livedatalink/epss_score is the top capability-matched alternative that's live right now. Other options: mcp-registry/io.github.getgapup/mcp-knowledge/vuln_exploitability_forecast, mcp-registry/io.github.getgapup/gapup-mcp/vuln_exploitability_forecast, mcp-registry/com.datanexusmcp/mcp-server/security_fetch_cve_epss, mcp-registry/io.github.megabrainee/sectora/get_trending_cves. Glimind ranks alternatives by semantic similarity and live health.

Is mcp-registry/io.github.pipeworx-io/epss/top_exploited down right now?

mcp-registry/io.github.pipeworx-io/epss/top_exploited's current verdict is "healthy". See its live status and score at https://glimind.com/tool/mcp-registry%2Fio.github.pipeworx-io%2Fepss%2Ftop_exploited.

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.pipeworx-io%2Fepss%2Ftop_exploited or MCP find_alternatives. Check mcp-registry/io.github.pipeworx-io/epss/top_exploited's live status: https://glimind.com/tool/mcp-registry/io.github.pipeworx-io/epss/top_exploited.