mcp-registry/io.github.saloprj/dialogbrain/contacts_find / alternatives

Live alternatives to mcp-registry/io.github.saloprj/dialogbrain/contacts_find

The best live alternatives to mcp-registry/io.github.saloprj/dialogbrain/contacts_find right now are mcp-registry/io.github.pipeworx-io/court-listener/resolve_entity, mcp-registry/io.github.pipeworx-io/plos/resolve_entity, mcp-registry/io.github.pipeworx-io/data-howardcounty/resolve_entity, mcp-registry/io.github.pipeworx-io/data-pa/resolve_entity, mcp-registry/io.github.pipeworx-io/data-sncf/resolve_entity — capability-matched and ranked by current reliability. mcp-registry/io.github.saloprj/dialogbrain/contacts_find itself is currently "healthy".

alternative	server
mcp-registry/io.github.pipeworx-io/court-listener/resolve_entity	io.github.pipeworx-io/court-listener	live status →
mcp-registry/io.github.pipeworx-io/plos/resolve_entity	io.github.pipeworx-io/plos	live status →
mcp-registry/io.github.pipeworx-io/data-howardcounty/resolve_entity	io.github.pipeworx-io/data-howardcounty	live status →
mcp-registry/io.github.pipeworx-io/data-pa/resolve_entity	io.github.pipeworx-io/data-pa	live status →
mcp-registry/io.github.pipeworx-io/data-sncf/resolve_entity	io.github.pipeworx-io/data-sncf	live status →
mcp-registry/io.github.pipeworx-io/madrid-events/resolve_entity	io.github.pipeworx-io/madrid-events	live status →
mcp-registry/io.github.pipeworx-io/rijksmuseum/resolve_entity	io.github.pipeworx-io/rijksmuseum	live status →
mcp-registry/io.github.pipeworx-io/cftc-cot/resolve_entity	io.github.pipeworx-io/cftc-cot	live status →
mcp-registry/io.github.pipeworx-io/data-utah/resolve_entity	io.github.pipeworx-io/data-utah	live status →
mcp-registry/io.github.pipeworx-io/arcgis-linncounty/resolve_entity	io.github.pipeworx-io/arcgis-linncounty	live status →
mcp-registry/io.github.pipeworx-io/tinder-bio/resolve_entity	io.github.pipeworx-io/tinder-bio	live status →
mcp-registry/io.github.pipeworx-io/overheid-nl/resolve_entity	io.github.pipeworx-io/overheid-nl	live status →

FAQ

What is the best alternative to mcp-registry/io.github.saloprj/dialogbrain/contacts_find?

mcp-registry/io.github.pipeworx-io/court-listener/resolve_entity is the top capability-matched alternative that's live right now. Other options: mcp-registry/io.github.pipeworx-io/plos/resolve_entity, mcp-registry/io.github.pipeworx-io/data-howardcounty/resolve_entity, mcp-registry/io.github.pipeworx-io/data-pa/resolve_entity, mcp-registry/io.github.pipeworx-io/data-sncf/resolve_entity. Glimind ranks alternatives by semantic similarity and live health.

Is mcp-registry/io.github.saloprj/dialogbrain/contacts_find down right now?

mcp-registry/io.github.saloprj/dialogbrain/contacts_find's current verdict is "healthy". See its live status and score at https://glimind.com/tool/mcp-registry%2Fio.github.saloprj%2Fdialogbrain%2Fcontacts_find.

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.saloprj%2Fdialogbrain%2Fcontacts_find or MCP find_alternatives. Check mcp-registry/io.github.saloprj/dialogbrain/contacts_find's live status: https://glimind.com/tool/mcp-registry/io.github.saloprj/dialogbrain/contacts_find.