mcp-registry/io.github.pipeworx-io/calendly/current_user / alternatives

Live alternatives to mcp-registry/io.github.pipeworx-io/calendly/current_user

The best live alternatives to mcp-registry/io.github.pipeworx-io/calendly/current_user right now are mcp-registry/io.github.makloai/mcp-server-dashform/get_user_info, mcp-registry/io.github.pipeworx-io/wakatime/current_user, mcp-registry/io.github.pipeworx-io/close-crm/close_me, mcp-registry/io.github.keploy/mcp/getCurrentUser, pulsemcp/adbutler/get_user — capability-matched and ranked by current reliability. mcp-registry/io.github.pipeworx-io/calendly/current_user itself is currently "healthy".

alternative	server
mcp-registry/io.github.makloai/mcp-server-dashform/get_user_info	io.github.makloai/mcp-server-dashform	live status →
mcp-registry/io.github.pipeworx-io/wakatime/current_user	io.github.pipeworx-io/wakatime	live status →
mcp-registry/io.github.pipeworx-io/close-crm/close_me	io.github.pipeworx-io/close-crm	live status →
mcp-registry/io.github.keploy/mcp/getCurrentUser	io.github.keploy/mcp	live status →
pulsemcp/adbutler/get_user	AdButler	live status →
mcp-registry/com.adbutler/mcp-server/get_user	com.adbutler/mcp-server	live status →
mcp-registry/io.stablebaseline/sb/getCurrentUser	io.stablebaseline/sb	live status →
mcp-registry/com.windowsforum/mcp-server/get_user	com.windowsforum/mcp-server	live status →
mcp-registry/io.github.trackingtime/mcp-server/get_user	io.github.TrackingTime/mcp-server	live status →
mcp-registry/io.github.luisa-sys/lyra-mcp-server/lyra_connect_calendar	io.github.luisa-sys/lyra-mcp-server	live status →
mcp-registry/io.github.ruyaacapital-admin/socializioz-chatgpt-mcp/get_user_profile	io.github.RuyaaCapital-admin/socializioz-chatgpt-mcp	live status →
mcp-registry/io.github.pipeworx-io/zendesk/zd_get_user	io.github.pipeworx-io/zendesk	live status →

FAQ

What is the best alternative to mcp-registry/io.github.pipeworx-io/calendly/current_user?

mcp-registry/io.github.makloai/mcp-server-dashform/get_user_info is the top capability-matched alternative that's live right now. Other options: mcp-registry/io.github.pipeworx-io/wakatime/current_user, mcp-registry/io.github.pipeworx-io/close-crm/close_me, mcp-registry/io.github.keploy/mcp/getCurrentUser, pulsemcp/adbutler/get_user. Glimind ranks alternatives by semantic similarity and live health.

Is mcp-registry/io.github.pipeworx-io/calendly/current_user down right now?

mcp-registry/io.github.pipeworx-io/calendly/current_user's current verdict is "healthy". See its live status and score at https://glimind.com/tool/mcp-registry%2Fio.github.pipeworx-io%2Fcalendly%2Fcurrent_user.

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%2Fcalendly%2Fcurrent_user or MCP find_alternatives. Check mcp-registry/io.github.pipeworx-io/calendly/current_user's live status: https://glimind.com/tool/mcp-registry/io.github.pipeworx-io/calendly/current_user.