mcp-registry/io.github.pipeworx-io/hgnc/resolve_xref / alternatives

Live alternatives to mcp-registry/io.github.pipeworx-io/hgnc/resolve_xref

The best live alternatives to mcp-registry/io.github.pipeworx-io/hgnc/resolve_xref right now are mcp-registry/io.github.pipeworx-io/cbioportal/get_gene, mcp-registry/io.github.pipeworx-io/ensembl/xrefs, mcp-registry/io.github.pipeworx-io/ensembl/lookup_symbol, mcp-registry/io.github.pipeworx-io/ensembl/lookup, mcp-registry/io.github.pipeworx-io/gnomad/gene — capability-matched and ranked by current reliability. mcp-registry/io.github.pipeworx-io/hgnc/resolve_xref itself is currently "healthy".

alternative	server
mcp-registry/io.github.pipeworx-io/cbioportal/get_gene	io.github.pipeworx-io/cbioportal	live status →
mcp-registry/io.github.pipeworx-io/ensembl/xrefs	io.github.pipeworx-io/ensembl	live status →
mcp-registry/io.github.pipeworx-io/ensembl/lookup_symbol	io.github.pipeworx-io/ensembl	live status →
mcp-registry/io.github.pipeworx-io/ensembl/lookup	io.github.pipeworx-io/ensembl	live status →
mcp-registry/io.github.pipeworx-io/gnomad/gene	io.github.pipeworx-io/gnomad	live status →
mcp-registry/io.github.pipeworx-io/string-db/resolve	io.github.pipeworx-io/string-db	live status →
mcp-registry/io.github.pipeworx-io/ncbi-eutils/esearch	io.github.pipeworx-io/ncbi-eutils	live status →
mcp-registry/io.github.pipeworx-io/gnomad/search	io.github.pipeworx-io/gnomad	live status →
mcp-registry/io.github.pipeworx-io/protein-atlas/search_genes	io.github.pipeworx-io/protein-atlas	live status →
mcp-registry/io.github.pipeworx-io/gwas-catalog/get_snp	io.github.pipeworx-io/gwas-catalog	live status →
mcp-registry/io.github.pipeworx-io/kegg/get_entry	io.github.pipeworx-io/kegg	live status →
mcp-registry/io.github.pipeworx-io/complex-portal/search_complexes	io.github.pipeworx-io/complex-portal	live status →

FAQ

What is the best alternative to mcp-registry/io.github.pipeworx-io/hgnc/resolve_xref?

mcp-registry/io.github.pipeworx-io/cbioportal/get_gene is the top capability-matched alternative that's live right now. Other options: mcp-registry/io.github.pipeworx-io/ensembl/xrefs, mcp-registry/io.github.pipeworx-io/ensembl/lookup_symbol, mcp-registry/io.github.pipeworx-io/ensembl/lookup, mcp-registry/io.github.pipeworx-io/gnomad/gene. Glimind ranks alternatives by semantic similarity and live health.

Is mcp-registry/io.github.pipeworx-io/hgnc/resolve_xref down right now?

mcp-registry/io.github.pipeworx-io/hgnc/resolve_xref's current verdict is "healthy". See its live status and score at https://glimind.com/tool/mcp-registry%2Fio.github.pipeworx-io%2Fhgnc%2Fresolve_xref.

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%2Fhgnc%2Fresolve_xref or MCP find_alternatives. Check mcp-registry/io.github.pipeworx-io/hgnc/resolve_xref's live status: https://glimind.com/tool/mcp-registry/io.github.pipeworx-io/hgnc/resolve_xref.