mcp-registry/io.github.pinalmdave/bookrails/reschedule_booking / alternatives

Live alternatives to mcp-registry/io.github.pinalmdave/bookrails/reschedule_booking

The best live alternatives to mcp-registry/io.github.pinalmdave/bookrails/reschedule_booking right now are mcp-registry/io.teres/booking/reschedule_booking, mcp-registry/com.hemmabo/hemmabo-mcp-server/hemmabo_booking_reschedule, mcp-registry/io.github.eziservices/mcp-public/reschedule_job, mcp-registry/io.favcrm/favcrm/confirm_booking, mcp-registry/bot.meet/mcp/book_meeting — capability-matched and ranked by current reliability. mcp-registry/io.github.pinalmdave/bookrails/reschedule_booking itself is currently "healthy".

alternative	server
mcp-registry/io.teres/booking/reschedule_booking	io.teres/booking	live status →
mcp-registry/com.hemmabo/hemmabo-mcp-server/hemmabo_booking_reschedule	com.hemmabo/hemmabo-mcp-server	live status →
mcp-registry/io.github.eziservices/mcp-public/reschedule_job	io.github.EziServices/mcp-public	live status →
mcp-registry/io.favcrm/favcrm/confirm_booking	io.favcrm/favcrm	live status →
mcp-registry/bot.meet/mcp/book_meeting	bot.meet/mcp	live status →
mcp-registry/io.favcrm/favcrm/update_service	io.favcrm/favcrm	live status →
mcp-registry/io.favcrm/favcrm/get_available_slots	io.favcrm/favcrm	live status →
mcp-registry/me.in-context/portfolio/booking_create	me.in-context/portfolio	live status →
mcp-registry/io.github.anteos-health/anteos-booking/reschedule_appointment	io.github.Anteos-Health/anteos-booking	live status →
mcp-registry/io.github.speeron-polska/speeron-next/confirm_booking	io.github.Speeron-Polska/speeron-next	live status →
mcp-registry/io.favcrm/favcrm/create_booking	io.favcrm/favcrm	live status →
mcp-registry/com.getcaboo/caboo/book_get_availability	com.getcaboo/caboo	live status →

FAQ

What is the best alternative to mcp-registry/io.github.pinalmdave/bookrails/reschedule_booking?

mcp-registry/io.teres/booking/reschedule_booking is the top capability-matched alternative that's live right now. Other options: mcp-registry/com.hemmabo/hemmabo-mcp-server/hemmabo_booking_reschedule, mcp-registry/io.github.eziservices/mcp-public/reschedule_job, mcp-registry/io.favcrm/favcrm/confirm_booking, mcp-registry/bot.meet/mcp/book_meeting. Glimind ranks alternatives by semantic similarity and live health.

Is mcp-registry/io.github.pinalmdave/bookrails/reschedule_booking down right now?

mcp-registry/io.github.pinalmdave/bookrails/reschedule_booking's current verdict is "healthy". See its live status and score at https://glimind.com/tool/mcp-registry%2Fio.github.pinalmdave%2Fbookrails%2Freschedule_booking.

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.pinalmdave%2Fbookrails%2Freschedule_booking or MCP find_alternatives. Check mcp-registry/io.github.pinalmdave/bookrails/reschedule_booking's live status: https://glimind.com/tool/mcp-registry/io.github.pinalmdave/bookrails/reschedule_booking.