mcp-registry/io.github.pipeworx-io/odoo/odoo_query_model / alternatives

Live alternatives to mcp-registry/io.github.pipeworx-io/odoo/odoo_query_model

The best live alternatives to mcp-registry/io.github.pipeworx-io/odoo/odoo_query_model right now are mcp-registry/fyi.iwant/iwant/demand.search, mcp-registry/io.corpusiq/multi-source-mcp/odoo_connector, mcp-registry/io.github.pipeworx-io/data-issy/query, mcp-registry/io.github.pipeworx-io/opendatasoft/records, mcp-registry/io.github.pipeworx-io/data-toulouse/query — capability-matched and ranked by current reliability. mcp-registry/io.github.pipeworx-io/odoo/odoo_query_model itself is currently "healthy".

alternativeserver
mcp-registry/fyi.iwant/iwant/demand.searchfyi.iwant/iwantlive status →
mcp-registry/io.corpusiq/multi-source-mcp/odoo_connectorio.corpusiq/multi-source-mcplive status →
mcp-registry/io.github.pipeworx-io/data-issy/queryio.github.pipeworx-io/data-issylive status →
mcp-registry/io.github.pipeworx-io/opendatasoft/recordsio.github.pipeworx-io/opendatasoftlive status →
mcp-registry/io.github.pipeworx-io/data-toulouse/queryio.github.pipeworx-io/data-toulouselive status →
mcp-registry/io.github.a7om-ai/atom-mcp-server/search_modelsio.github.A7OM-AI/atom-mcp-serverlive status →
pulsemcp/atom-pricing-intelligence/search_modelsATOM Pricing Intelligencelive status →
mcp-registry/io.github.pipeworx-io/data-reunion/queryio.github.pipeworx-io/data-reunionlive status →
mcp-registry/io.github.pipeworx-io/data-nantes/queryio.github.pipeworx-io/data-nanteslive status →
mcp-registry/com.windowsforum/mcp-server/search_userscom.windowsforum/mcp-serverlive status →
mcp-registry/io.github.pipeworx-io/data-brussels/queryio.github.pipeworx-io/data-brusselslive status →
mcp-registry/io.github.pipeworx-io/data-rennes/queryio.github.pipeworx-io/data-renneslive status →

FAQ

What is the best alternative to mcp-registry/io.github.pipeworx-io/odoo/odoo_query_model?

mcp-registry/fyi.iwant/iwant/demand.search is the top capability-matched alternative that's live right now. Other options: mcp-registry/io.corpusiq/multi-source-mcp/odoo_connector, mcp-registry/io.github.pipeworx-io/data-issy/query, mcp-registry/io.github.pipeworx-io/opendatasoft/records, mcp-registry/io.github.pipeworx-io/data-toulouse/query. Glimind ranks alternatives by semantic similarity and live health.

Is mcp-registry/io.github.pipeworx-io/odoo/odoo_query_model down right now?

mcp-registry/io.github.pipeworx-io/odoo/odoo_query_model's current verdict is "healthy". See its live status and score at https://glimind.com/tool/mcp-registry%2Fio.github.pipeworx-io%2Fodoo%2Fodoo_query_model.

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%2Fodoo%2Fodoo_query_model or MCP find_alternatives. Check mcp-registry/io.github.pipeworx-io/odoo/odoo_query_model's live status: https://glimind.com/tool/mcp-registry/io.github.pipeworx-io/odoo/odoo_query_model.