mcp-registry/io.github.kuhumcst/dannet/analyze_namespace_usage / alternatives

Live alternatives to mcp-registry/io.github.kuhumcst/dannet/analyze_namespace_usage

The best live alternatives to mcp-registry/io.github.kuhumcst/dannet/analyze_namespace_usage right now are mcp-registry/io.github.pipeworx-io/open-sanctions/get_entity, mcp-registry/ai.sugra/api-mcp/resolve_entity, mcp-registry/io.github.br0ski777/ens-resolver/crypto_resolve_ens, mcp-registry/com.dropwatchhq/entity-screen/resolve_entity, mcp-registry/io.github.subsquid-labs/portal-mcp-server/portal_resolve_entity — capability-matched and ranked by current reliability. mcp-registry/io.github.kuhumcst/dannet/analyze_namespace_usage itself is currently "healthy".

alternative	server
mcp-registry/io.github.pipeworx-io/open-sanctions/get_entity	io.github.pipeworx-io/open-sanctions	live status →
mcp-registry/ai.sugra/api-mcp/resolve_entity	ai.sugra/api-mcp	live status →
mcp-registry/io.github.br0ski777/ens-resolver/crypto_resolve_ens	io.github.Br0ski777/ens-resolver	live status →
mcp-registry/com.dropwatchhq/entity-screen/resolve_entity	com.dropwatchhq/entity-screen	live status →
mcp-registry/io.github.subsquid-labs/portal-mcp-server/portal_resolve_entity	io.github.subsquid-labs/portal-mcp-server	live status →
mcp-registry/io.github.bch1212/pubrecords/mcp_verify_entity	io.github.bch1212/pubrecords	live status →
mcp-registry/io.github.pipeworx-io/wikidata/get_entity	io.github.pipeworx-io/wikidata	live status →
mcp-registry/io.github.pipeworx-io/permid/get_entity	io.github.pipeworx-io/permid	live status →
mcp-registry/co.ainumbers/tools/classify_nis2_entity	co.ainumbers/tools	live status →
mcp-registry/io.github.entia-systems-core/entity-verification/get_entia_home	io.github.entia-systems-core/entity-verification	live status →
mcp-registry/ai.tunnelmind/data/get_entity	ai.tunnelmind/data	live status →
mcp-registry/ai.namewhisper/ens-tools/enumerate_entities	ai.namewhisper/ens-tools	live status →

FAQ

What is the best alternative to mcp-registry/io.github.kuhumcst/dannet/analyze_namespace_usage?

mcp-registry/io.github.pipeworx-io/open-sanctions/get_entity is the top capability-matched alternative that's live right now. Other options: mcp-registry/ai.sugra/api-mcp/resolve_entity, mcp-registry/io.github.br0ski777/ens-resolver/crypto_resolve_ens, mcp-registry/com.dropwatchhq/entity-screen/resolve_entity, mcp-registry/io.github.subsquid-labs/portal-mcp-server/portal_resolve_entity. Glimind ranks alternatives by semantic similarity and live health.

Is mcp-registry/io.github.kuhumcst/dannet/analyze_namespace_usage down right now?

mcp-registry/io.github.kuhumcst/dannet/analyze_namespace_usage's current verdict is "healthy". See its live status and score at https://glimind.com/tool/mcp-registry%2Fio.github.kuhumcst%2Fdannet%2Fanalyze_namespace_usage.

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.kuhumcst%2Fdannet%2Fanalyze_namespace_usage or MCP find_alternatives. Check mcp-registry/io.github.kuhumcst/dannet/analyze_namespace_usage's live status: https://glimind.com/tool/mcp-registry/io.github.kuhumcst/dannet/analyze_namespace_usage.