mcp-registry/io.corpusiq/multi-source-mcp/calendly_connector / alternatives

Live alternatives to mcp-registry/io.corpusiq/multi-source-mcp/calendly_connector

The best live alternatives to mcp-registry/io.corpusiq/multi-source-mcp/calendly_connector right now are mcp-registry/fyi.clearmarket/clearmarket/get_event, mcp-registry/io.github.capratesignals-cpu/cap-rate-signals/log_missed_query, mcp-registry/fyi.clearmarket/clearmarket/list_events, mcp-registry/ai.mrmarket/mrmarket-mcp/query_data, mcp-registry/io.github.pipeworx-io/destatis/deep_research — capability-matched and ranked by current reliability. mcp-registry/io.corpusiq/multi-source-mcp/calendly_connector itself is currently "healthy".

alternative	server
mcp-registry/fyi.clearmarket/clearmarket/get_event	fyi.clearmarket/clearmarket	live status →
mcp-registry/io.github.capratesignals-cpu/cap-rate-signals/log_missed_query	io.github.capratesignals-cpu/cap-rate-signals	live status →
mcp-registry/fyi.clearmarket/clearmarket/list_events	fyi.clearmarket/clearmarket	live status →
mcp-registry/ai.mrmarket/mrmarket-mcp/query_data	ai.mrmarket/mrmarket-mcp	live status →
mcp-registry/io.github.pipeworx-io/destatis/deep_research	io.github.pipeworx-io/destatis	live status →
mcp-registry/io.github.pipeworx-io/arcgis-cary/deep_research	io.github.pipeworx-io/arcgis-cary	live status →
mcp-registry/io.github.pipeworx-io/kraken/deep_research	io.github.pipeworx-io/kraken	live status →
mcp-registry/io.github.pipeworx-io/japan-law/deep_research	io.github.pipeworx-io/japan-law	live status →
mcp-registry/io.github.pipeworx-io/inaturalist/deep_research	io.github.pipeworx-io/inaturalist	live status →
mcp-registry/io.github.pipeworx-io/arcgis-detroit/deep_research	io.github.pipeworx-io/arcgis-detroit	live status →
mcp-registry/io.github.pipeworx-io/arcgis-coquitlam/deep_research	io.github.pipeworx-io/arcgis-coquitlam	live status →
mcp-registry/io.github.pipeworx-io/data-gr/deep_research	io.github.pipeworx-io/data-gr	live status →

FAQ

What is the best alternative to mcp-registry/io.corpusiq/multi-source-mcp/calendly_connector?

mcp-registry/fyi.clearmarket/clearmarket/get_event is the top capability-matched alternative that's live right now. Other options: mcp-registry/io.github.capratesignals-cpu/cap-rate-signals/log_missed_query, mcp-registry/fyi.clearmarket/clearmarket/list_events, mcp-registry/ai.mrmarket/mrmarket-mcp/query_data, mcp-registry/io.github.pipeworx-io/destatis/deep_research. Glimind ranks alternatives by semantic similarity and live health.

Is mcp-registry/io.corpusiq/multi-source-mcp/calendly_connector down right now?

mcp-registry/io.corpusiq/multi-source-mcp/calendly_connector's current verdict is "healthy". See its live status and score at https://glimind.com/tool/mcp-registry%2Fio.corpusiq%2Fmulti-source-mcp%2Fcalendly_connector.

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.corpusiq%2Fmulti-source-mcp%2Fcalendly_connector or MCP find_alternatives. Check mcp-registry/io.corpusiq/multi-source-mcp/calendly_connector's live status: https://glimind.com/tool/mcp-registry/io.corpusiq/multi-source-mcp/calendly_connector.