mcp-registry/io.github.pipeworx-io/guidetopharmacology/target_interactions / alternatives

Live alternatives to mcp-registry/io.github.pipeworx-io/guidetopharmacology/target_interactions

The best live alternatives to mcp-registry/io.github.pipeworx-io/guidetopharmacology/target_interactions right now are mcp-registry/io.github.pipeworx-io/opentargets/target, mcp-registry/io.github.pipeworx-io/intact/find_interactions, mcp-registry/io.github.pipeworx-io/opentargets/drug, mcp-registry/io.github.pipeworx-io/rcsb-pdb/ligand, mcp-registry/io.github.pipeworx-io/opentargets/target_known_drugs — capability-matched and ranked by current reliability. mcp-registry/io.github.pipeworx-io/guidetopharmacology/target_interactions itself is currently "healthy".

alternative	server
mcp-registry/io.github.pipeworx-io/opentargets/target	io.github.pipeworx-io/opentargets	live status →
mcp-registry/io.github.pipeworx-io/intact/find_interactions	io.github.pipeworx-io/intact	live status →
mcp-registry/io.github.pipeworx-io/opentargets/drug	io.github.pipeworx-io/opentargets	live status →
mcp-registry/io.github.pipeworx-io/rcsb-pdb/ligand	io.github.pipeworx-io/rcsb-pdb	live status →
mcp-registry/io.github.pipeworx-io/opentargets/target_known_drugs	io.github.pipeworx-io/opentargets	live status →
mcp-registry/io.github.pipeworx-io/opentargets/target_associations	io.github.pipeworx-io/opentargets	live status →
mcp-registry/io.github.nhoverte/biocosm/find_by_target	io.github.nhoverte/biocosm	live status →
mcp-registry/io.github.pipeworx-io/opentargets/search	io.github.pipeworx-io/opentargets	live status →
mcp-registry/io.github.pipeworx-io/opentargets/disease_associations	io.github.pipeworx-io/opentargets	live status →
mcp-registry/io.github.pipeworx-io/string-db/interactions	io.github.pipeworx-io/string-db	live status →
mcp-registry/com.claidex/failure-intelligence/query_opentargets	com.claidex/failure-intelligence	live status →
mcp-registry/io.github.pipeworx-io/intact/interaction_count	io.github.pipeworx-io/intact	live status →

FAQ

What is the best alternative to mcp-registry/io.github.pipeworx-io/guidetopharmacology/target_interactions?

mcp-registry/io.github.pipeworx-io/opentargets/target is the top capability-matched alternative that's live right now. Other options: mcp-registry/io.github.pipeworx-io/intact/find_interactions, mcp-registry/io.github.pipeworx-io/opentargets/drug, mcp-registry/io.github.pipeworx-io/rcsb-pdb/ligand, mcp-registry/io.github.pipeworx-io/opentargets/target_known_drugs. Glimind ranks alternatives by semantic similarity and live health.

Is mcp-registry/io.github.pipeworx-io/guidetopharmacology/target_interactions down right now?

mcp-registry/io.github.pipeworx-io/guidetopharmacology/target_interactions's current verdict is "healthy". See its live status and score at https://glimind.com/tool/mcp-registry%2Fio.github.pipeworx-io%2Fguidetopharmacology%2Ftarget_interactions.

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%2Fguidetopharmacology%2Ftarget_interactions or MCP find_alternatives. Check mcp-registry/io.github.pipeworx-io/guidetopharmacology/target_interactions's live status: https://glimind.com/tool/mcp-registry/io.github.pipeworx-io/guidetopharmacology/target_interactions.