mcp-registry/io.github.pipeworx-io/ibge-br/name_frequency / alternatives

Live alternatives to mcp-registry/io.github.pipeworx-io/ibge-br/name_frequency

The best live alternatives to mcp-registry/io.github.pipeworx-io/ibge-br/name_frequency right now are mcp-registry/io.github.pipeworx-io/nationalize/batch_predict, mcp-registry/io.github.pipeworx-io/agify/predict_age, mcp-registry/io.github.pipeworx-io/brapi/prime_rate, mcp-registry/io.github.pipeworx-io/brapi/inflation, mcp-registry/io.github.pipeworx-io/bpstat-pt/list_domains — capability-matched and ranked by current reliability. mcp-registry/io.github.pipeworx-io/ibge-br/name_frequency itself is currently "healthy".

alternative	server
mcp-registry/io.github.pipeworx-io/nationalize/batch_predict	io.github.pipeworx-io/nationalize	live status →
mcp-registry/io.github.pipeworx-io/agify/predict_age	io.github.pipeworx-io/agify	live status →
mcp-registry/io.github.pipeworx-io/brapi/prime_rate	io.github.pipeworx-io/brapi	live status →
mcp-registry/io.github.pipeworx-io/brapi/inflation	io.github.pipeworx-io/brapi	live status →
mcp-registry/io.github.pipeworx-io/bpstat-pt/list_domains	io.github.pipeworx-io/bpstat-pt	live status →
mcp-registry/io.github.pipeworx-io/nationalize/predict_nationality	io.github.pipeworx-io/nationalize	live status →
mcp-registry/io.github.pipeworx-io/agify/predict_age_country	io.github.pipeworx-io/agify	live status →
mcp-registry/io.github.pipeworx-io/genderize/predict_gender_country	io.github.pipeworx-io/genderize	live status →
mcp-registry/io.github.blackboxfoundry/livedatalink/census_business	io.github.blackboxfoundry/livedatalink	live status →
mcp-registry/io.github.pipeworx-io/bcb-br/indicator	io.github.pipeworx-io/bcb-br	live status →
mcp-registry/io.github.pipeworx-io/brapi/quote_list	io.github.pipeworx-io/brapi	live status →
mcp-registry/io.github.mcp-dir/jusbrasil-mcp/cpf_processos	io.github.mcp-dir/jusbrasil-mcp	live status →

FAQ

What is the best alternative to mcp-registry/io.github.pipeworx-io/ibge-br/name_frequency?

mcp-registry/io.github.pipeworx-io/nationalize/batch_predict is the top capability-matched alternative that's live right now. Other options: mcp-registry/io.github.pipeworx-io/agify/predict_age, mcp-registry/io.github.pipeworx-io/brapi/prime_rate, mcp-registry/io.github.pipeworx-io/brapi/inflation, mcp-registry/io.github.pipeworx-io/bpstat-pt/list_domains. Glimind ranks alternatives by semantic similarity and live health.

Is mcp-registry/io.github.pipeworx-io/ibge-br/name_frequency down right now?

mcp-registry/io.github.pipeworx-io/ibge-br/name_frequency's current verdict is "healthy". See its live status and score at https://glimind.com/tool/mcp-registry%2Fio.github.pipeworx-io%2Fibge-br%2Fname_frequency.

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%2Fibge-br%2Fname_frequency or MCP find_alternatives. Check mcp-registry/io.github.pipeworx-io/ibge-br/name_frequency's live status: https://glimind.com/tool/mcp-registry/io.github.pipeworx-io/ibge-br/name_frequency.