mcp-registry/ai.datamerge/mcp/run_contact_search / alternatives

Live alternatives to mcp-registry/ai.datamerge/mcp/run_contact_search

The best live alternatives to mcp-registry/ai.datamerge/mcp/run_contact_search right now are mcp-registry/app.saber.mcp/saber/contacts-get_research, mcp-registry/app.saber.mcp/saber/contacts-create_research, mcp-registry/app.saber.mcp/saber/contact_lists-create, mcp-registry/app.saber.mcp/saber/contacts-create_signal, mcp-registry/com.advocatemcp/advocate/request_callback — capability-matched and ranked by current reliability. mcp-registry/ai.datamerge/mcp/run_contact_search itself is currently "healthy".

alternative	server
mcp-registry/app.saber.mcp/saber/contacts-get_research	app.saber.mcp/saber	live status →
mcp-registry/app.saber.mcp/saber/contacts-create_research	app.saber.mcp/saber	live status →
mcp-registry/app.saber.mcp/saber/contact_lists-create	app.saber.mcp/saber	live status →
mcp-registry/app.saber.mcp/saber/contacts-create_signal	app.saber.mcp/saber	live status →
mcp-registry/com.advocatemcp/advocate/request_callback	com.advocatemcp/advocate	live status →
mcp-registry/app.saber.mcp/saber/contacts-list_signals	app.saber.mcp/saber	live status →
mcp-registry/co.bizverify/mcp/check_job_status	co.bizverify/mcp	live status →
mcp-registry/ai.fodda/mcp-server/check_research_status	ai.fodda/mcp-server	live status →
mcp-registry/io.github.pipeworx-io/intercom/ic_search_contacts	io.github.pipeworx-io/intercom	live status →
mcp-registry/com.gocreativeai.enrich/prism/search_web	com.gocreativeai.enrich/prism	live status →
mcp-registry/com.gocreativeai.omnicall/agent-tools/search_web	com.gocreativeai.omnicall/agent-tools	live status →
mcp-registry/io.github.colinhughes2121/gocreative-agent-api/search_web	io.github.ColinHughes2121/gocreative-agent-api	live status →

FAQ

What is the best alternative to mcp-registry/ai.datamerge/mcp/run_contact_search?

mcp-registry/app.saber.mcp/saber/contacts-get_research is the top capability-matched alternative that's live right now. Other options: mcp-registry/app.saber.mcp/saber/contacts-create_research, mcp-registry/app.saber.mcp/saber/contact_lists-create, mcp-registry/app.saber.mcp/saber/contacts-create_signal, mcp-registry/com.advocatemcp/advocate/request_callback. Glimind ranks alternatives by semantic similarity and live health.

Is mcp-registry/ai.datamerge/mcp/run_contact_search down right now?

mcp-registry/ai.datamerge/mcp/run_contact_search's current verdict is "healthy". See its live status and score at https://glimind.com/tool/mcp-registry%2Fai.datamerge%2Fmcp%2Frun_contact_search.

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%2Fai.datamerge%2Fmcp%2Frun_contact_search or MCP find_alternatives. Check mcp-registry/ai.datamerge/mcp/run_contact_search's live status: https://glimind.com/tool/mcp-registry/ai.datamerge/mcp/run_contact_search.