mcp-registry/be.vibedeploy/vibedeploy/read_source_files / alternatives
mcp-registry/be.vibedeploy/vibedeploy/read_source_filesThe best live alternatives to mcp-registry/be.vibedeploy/vibedeploy/read_source_files right now are mcp-registry/com.searchcode/mcp/code_get_files, mcp-registry/io.github.parallect/prxhub/add_sources, mcp-registry/io.github.foundrynet/foundrynet-scrape/extract_batch, mcp-registry/it.elsas/security-intel/scan_dependencies, mcp-registry/io.github.cmoen11/redm-mcp/read_lines — capability-matched and ranked by current reliability. mcp-registry/be.vibedeploy/vibedeploy/read_source_files itself is currently "healthy".
mcp-registry/com.searchcode/mcp/code_get_files is the top capability-matched alternative that's live right now. Other options: mcp-registry/io.github.parallect/prxhub/add_sources, mcp-registry/io.github.foundrynet/foundrynet-scrape/extract_batch, mcp-registry/it.elsas/security-intel/scan_dependencies, mcp-registry/io.github.cmoen11/redm-mcp/read_lines. Glimind ranks alternatives by semantic similarity and live health.
mcp-registry/be.vibedeploy/vibedeploy/read_source_files's current verdict is "healthy". See its live status and score at https://glimind.com/tool/mcp-registry%2Fbe.vibedeploy%2Fvibedeploy%2Fread_source_files.
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%2Fbe.vibedeploy%2Fvibedeploy%2Fread_source_files
or MCP find_alternatives. Check mcp-registry/be.vibedeploy/vibedeploy/read_source_files's live status: https://glimind.com/tool/mcp-registry/be.vibedeploy/vibedeploy/read_source_files.