mcp-registry/it.elsas/security-intel/check_package / alternatives
mcp-registry/it.elsas/security-intel/check_packageThe best live alternatives to mcp-registry/it.elsas/security-intel/check_package right now are mcp-registry/com.datanexusmcp/mcp-server/security_fetch_package_risk_brief, mcp-registry/io.github.foundrynet/cyber-intel-mcp/vulnerability_scan, mcp-registry/io.github.megabrainee/sectora/assess_dependency, mcp-registry/io.github.onefreeman1337/osf-data-marketplace/is_cve_exploited, mcp-registry/io.github.blackboxfoundry/livedatalink/kev_status_check — capability-matched and ranked by current reliability. mcp-registry/it.elsas/security-intel/check_package itself is currently "healthy".
mcp-registry/com.datanexusmcp/mcp-server/security_fetch_package_risk_brief is the top capability-matched alternative that's live right now. Other options: mcp-registry/io.github.foundrynet/cyber-intel-mcp/vulnerability_scan, mcp-registry/io.github.megabrainee/sectora/assess_dependency, mcp-registry/io.github.onefreeman1337/osf-data-marketplace/is_cve_exploited, mcp-registry/io.github.blackboxfoundry/livedatalink/kev_status_check. Glimind ranks alternatives by semantic similarity and live health.
mcp-registry/it.elsas/security-intel/check_package's current verdict is "healthy". See its live status and score at https://glimind.com/tool/mcp-registry%2Fit.elsas%2Fsecurity-intel%2Fcheck_package.
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.
Get a live, capability-matched substitute in one call: GET https://glimind.com/v1/alternatives/mcp-registry%2Fit.elsas%2Fsecurity-intel%2Fcheck_package
or MCP find_alternatives. Check mcp-registry/it.elsas/security-intel/check_package's live status: https://glimind.com/tool/mcp-registry/it.elsas/security-intel/check_package.