mcp-registry/dev.depscope/mcp/pin_safe / alternatives

Live alternatives to mcp-registry/dev.depscope/mcp/pin_safe

The best live alternatives to mcp-registry/dev.depscope/mcp/pin_safe right now are mcp-registry/io.github.fetter-io/fetter-mcp/most_recent_not_vulnerable, mcp-registry/io.github.fetter-io/fetter-mcp/is_vulnerable, mcp-registry/io.github.megabrainee/sectora/assess_dependency, mcp-registry/io.github.pipeworx-io/npm/get_version_info, mcp-registry/com.datanexusmcp/mcp-server/security_fetch_cve_risk_summary — capability-matched and ranked by current reliability. mcp-registry/dev.depscope/mcp/pin_safe itself is currently "healthy".

alternative	server
mcp-registry/io.github.fetter-io/fetter-mcp/most_recent_not_vulnerable	io.github.fetter-io/fetter-mcp	live status →
mcp-registry/io.github.fetter-io/fetter-mcp/is_vulnerable	io.github.fetter-io/fetter-mcp	live status →
mcp-registry/io.github.megabrainee/sectora/assess_dependency	io.github.megabrainee/sectora	live status →
mcp-registry/io.github.pipeworx-io/npm/get_version_info	io.github.pipeworx-io/npm	live status →
mcp-registry/com.datanexusmcp/mcp-server/security_fetch_cve_risk_summary	com.datanexusmcp/mcp-server	live status →
mcp-registry/io.github.blackboxfoundry/livedatalink/npm_package	io.github.blackboxfoundry/livedatalink	live status →
mcp-registry/io.github.xyzzylabs/wasm-mcp/spec_version	io.github.xyzzylabs/wasm-mcp	live status →
mcp-registry/io.github.pipeworx-io/jsdelivr/resolve_version	io.github.pipeworx-io/jsdelivr	live status →
mcp-registry/com.contrastcyber/api/check_dependencies	com.contrastcyber/api	live status →
mcp-registry/com.datanexusmcp/mcp-server/security_fetch_package_risk_brief	com.datanexusmcp/mcp-server	live status →
mcp-registry/com.datanexusmcp/mcp-server/security_fetch_package_vulnerabilities	com.datanexusmcp/mcp-server	live status →
mcp-registry/ai.dynamicfeed/dynamic-feed/package_health	ai.dynamicfeed/dynamic-feed	live status →

FAQ

What is the best alternative to mcp-registry/dev.depscope/mcp/pin_safe?

mcp-registry/io.github.fetter-io/fetter-mcp/most_recent_not_vulnerable is the top capability-matched alternative that's live right now. Other options: mcp-registry/io.github.fetter-io/fetter-mcp/is_vulnerable, mcp-registry/io.github.megabrainee/sectora/assess_dependency, mcp-registry/io.github.pipeworx-io/npm/get_version_info, mcp-registry/com.datanexusmcp/mcp-server/security_fetch_cve_risk_summary. Glimind ranks alternatives by semantic similarity and live health.

Is mcp-registry/dev.depscope/mcp/pin_safe down right now?

mcp-registry/dev.depscope/mcp/pin_safe's current verdict is "healthy". See its live status and score at https://glimind.com/tool/mcp-registry%2Fdev.depscope%2Fmcp%2Fpin_safe.

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%2Fdev.depscope%2Fmcp%2Fpin_safe or MCP find_alternatives. Check mcp-registry/dev.depscope/mcp/pin_safe's live status: https://glimind.com/tool/mcp-registry/dev.depscope/mcp/pin_safe.