mcp-registry/io.github.evanfollis/preflight/check_publish_readiness / alternatives
mcp-registry/io.github.evanfollis/preflight/check_publish_readinessThe best live alternatives to mcp-registry/io.github.evanfollis/preflight/check_publish_readiness right now are mcp-registry/io.github.pduggusa/dredd-mcp/check_mcp_server, mcp-registry/co.ainumbers/tools/validate_mcp_server_json, mcp-registry/online.sasame/research/readiness_report, mcp-registry/online.sasame/research/verify_mcp_ready, mcp-registry/online.sasame/research/audit_mcp — capability-matched and ranked by current reliability. mcp-registry/io.github.evanfollis/preflight/check_publish_readiness itself is currently "healthy".
mcp-registry/io.github.pduggusa/dredd-mcp/check_mcp_server is the top capability-matched alternative that's live right now. Other options: mcp-registry/co.ainumbers/tools/validate_mcp_server_json, mcp-registry/online.sasame/research/readiness_report, mcp-registry/online.sasame/research/verify_mcp_ready, mcp-registry/online.sasame/research/audit_mcp. Glimind ranks alternatives by semantic similarity and live health.
mcp-registry/io.github.evanfollis/preflight/check_publish_readiness's current verdict is "healthy". See its live status and score at https://glimind.com/tool/mcp-registry%2Fio.github.evanfollis%2Fpreflight%2Fcheck_publish_readiness.
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%2Fio.github.evanfollis%2Fpreflight%2Fcheck_publish_readiness
or MCP find_alternatives. Check mcp-registry/io.github.evanfollis/preflight/check_publish_readiness's live status: https://glimind.com/tool/mcp-registry/io.github.evanfollis/preflight/check_publish_readiness.