mcp-registry/io.github.pipeworx-io/nvd/recent_cves / alternatives

Live alternatives to mcp-registry/io.github.pipeworx-io/nvd/recent_cves

The best live alternatives to mcp-registry/io.github.pipeworx-io/nvd/recent_cves right now are mcp-registry/io.github.pipeworx-io/nuget/recent_changes, mcp-registry/io.github.pipeworx-io/semanticscholar/recent_changes, mcp-registry/io.github.pipeworx-io/seo-ai-visibility/recent_changes, mcp-registry/io.github.pipeworx-io/reactome/recent_changes, mcp-registry/io.github.pipeworx-io/yelp/recent_changes — capability-matched and ranked by current reliability. mcp-registry/io.github.pipeworx-io/nvd/recent_cves itself is currently "healthy".

alternative	server
mcp-registry/io.github.pipeworx-io/nuget/recent_changes	io.github.pipeworx-io/nuget	live status →
mcp-registry/io.github.pipeworx-io/semanticscholar/recent_changes	io.github.pipeworx-io/semanticscholar	live status →
mcp-registry/io.github.pipeworx-io/seo-ai-visibility/recent_changes	io.github.pipeworx-io/seo-ai-visibility	live status →
mcp-registry/io.github.pipeworx-io/reactome/recent_changes	io.github.pipeworx-io/reactome	live status →
mcp-registry/io.github.pipeworx-io/yelp/recent_changes	io.github.pipeworx-io/yelp	live status →
mcp-registry/io.github.pipeworx-io/zoho_crm/recent_changes	io.github.pipeworx-io/zoho_crm	live status →
mcp-registry/io.github.pipeworx-io/linear/recent_changes	io.github.pipeworx-io/linear	live status →
mcp-registry/io.github.pipeworx-io/law-feeds/recent_changes	io.github.pipeworx-io/law-feeds	live status →
mcp-registry/io.github.pipeworx-io/legiscan/recent_changes	io.github.pipeworx-io/legiscan	live status →
mcp-registry/io.github.pipeworx-io/launches/recent_changes	io.github.pipeworx-io/launches	live status →
mcp-registry/io.github.pipeworx-io/leadconnector/recent_changes	io.github.pipeworx-io/leadconnector	live status →
mcp-registry/io.github.pipeworx-io/leetcode/recent_changes	io.github.pipeworx-io/leetcode	live status →

FAQ

What is the best alternative to mcp-registry/io.github.pipeworx-io/nvd/recent_cves?

mcp-registry/io.github.pipeworx-io/nuget/recent_changes is the top capability-matched alternative that's live right now. Other options: mcp-registry/io.github.pipeworx-io/semanticscholar/recent_changes, mcp-registry/io.github.pipeworx-io/seo-ai-visibility/recent_changes, mcp-registry/io.github.pipeworx-io/reactome/recent_changes, mcp-registry/io.github.pipeworx-io/yelp/recent_changes. Glimind ranks alternatives by semantic similarity and live health.

Is mcp-registry/io.github.pipeworx-io/nvd/recent_cves down right now?

mcp-registry/io.github.pipeworx-io/nvd/recent_cves's current verdict is "healthy". See its live status and score at https://glimind.com/tool/mcp-registry%2Fio.github.pipeworx-io%2Fnvd%2Frecent_cves.

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%2Fnvd%2Frecent_cves or MCP find_alternatives. Check mcp-registry/io.github.pipeworx-io/nvd/recent_cves's live status: https://glimind.com/tool/mcp-registry/io.github.pipeworx-io/nvd/recent_cves.