mcp-registry/io.github.trycourier/courier/subscribe_user_to_lists / alternatives

Live alternatives to mcp-registry/io.github.trycourier/courier/subscribe_user_to_lists

The best live alternatives to mcp-registry/io.github.trycourier/courier/subscribe_user_to_lists right now are mcp-registry/com.po6/mailbox/list_email_lists, mcp-registry/io.github.pipeworx-io/stripe_connect/stripe_list_subscriptions, mcp-registry/ai.datamerge/mcp/list_lists, mcp-registry/app.saber.mcp/saber/signal_subscriptions-list, mcp-registry/io.github.tlkc888-jenkins/joy/list_campaigns — capability-matched and ranked by current reliability. mcp-registry/io.github.trycourier/courier/subscribe_user_to_lists itself is currently "healthy".

alternative	server
mcp-registry/com.po6/mailbox/list_email_lists	com.po6/mailbox	live status →
mcp-registry/io.github.pipeworx-io/stripe_connect/stripe_list_subscriptions	io.github.pipeworx-io/stripe_connect	live status →
mcp-registry/ai.datamerge/mcp/list_lists	ai.datamerge/mcp	live status →
mcp-registry/app.saber.mcp/saber/signal_subscriptions-list	app.saber.mcp/saber	live status →
mcp-registry/io.github.tlkc888-jenkins/joy/list_campaigns	io.github.tlkc888-Jenkins/joy	live status →
mcp-registry/app.saber.mcp/saber/subscription_actions-create	app.saber.mcp/saber	live status →
mcp-registry/io.github.pipeworx-io/klaviyo/klaviyo_list_lists	io.github.pipeworx-io/klaviyo	live status →
mcp-registry/io.favcrm/favcrm/list_subscriptions	io.favcrm/favcrm	live status →
pulsemcp/adbutler/list_data_lists	AdButler	live status →
mcp-registry/com.adbutler/mcp-server/list_data_lists	com.adbutler/mcp-server	live status →
pulsemcp/adbutler/create_data_list	AdButler	live status →
mcp-registry/com.adbutler/mcp-server/create_data_list	com.adbutler/mcp-server	live status →

FAQ

What is the best alternative to mcp-registry/io.github.trycourier/courier/subscribe_user_to_lists?

mcp-registry/com.po6/mailbox/list_email_lists is the top capability-matched alternative that's live right now. Other options: mcp-registry/io.github.pipeworx-io/stripe_connect/stripe_list_subscriptions, mcp-registry/ai.datamerge/mcp/list_lists, mcp-registry/app.saber.mcp/saber/signal_subscriptions-list, mcp-registry/io.github.tlkc888-jenkins/joy/list_campaigns. Glimind ranks alternatives by semantic similarity and live health.

Is mcp-registry/io.github.trycourier/courier/subscribe_user_to_lists down right now?

mcp-registry/io.github.trycourier/courier/subscribe_user_to_lists's current verdict is "healthy". See its live status and score at https://glimind.com/tool/mcp-registry%2Fio.github.trycourier%2Fcourier%2Fsubscribe_user_to_lists.

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.trycourier%2Fcourier%2Fsubscribe_user_to_lists or MCP find_alternatives. Check mcp-registry/io.github.trycourier/courier/subscribe_user_to_lists's live status: https://glimind.com/tool/mcp-registry/io.github.trycourier/courier/subscribe_user_to_lists.