mcp-registry/com.quintadb/mcp/get_column_total / alternatives

Live alternatives to mcp-registry/com.quintadb/mcp/get_column_total

The best live alternatives to mcp-registry/com.quintadb/mcp/get_column_total right now are mcp-registry/io.github.pipeworx-io/healthdata/polymarket_fill_risk, mcp-registry/io.github.pipeworx-io/entreprises-fr/polymarket_fill_risk, mcp-registry/io.github.pipeworx-io/wikidata-sparql/polymarket_fill_risk, mcp-registry/io.github.pipeworx-io/dane-gov-pl/polymarket_fill_risk, mcp-registry/io.github.pipeworx-io/onedrive/polymarket_fill_risk — capability-matched and ranked by current reliability. mcp-registry/com.quintadb/mcp/get_column_total itself is currently "healthy".

alternative	server
mcp-registry/io.github.pipeworx-io/healthdata/polymarket_fill_risk	io.github.pipeworx-io/healthdata	live status →
mcp-registry/io.github.pipeworx-io/entreprises-fr/polymarket_fill_risk	io.github.pipeworx-io/entreprises-fr	live status →
mcp-registry/io.github.pipeworx-io/wikidata-sparql/polymarket_fill_risk	io.github.pipeworx-io/wikidata-sparql	live status →
mcp-registry/io.github.pipeworx-io/dane-gov-pl/polymarket_fill_risk	io.github.pipeworx-io/dane-gov-pl	live status →
mcp-registry/io.github.pipeworx-io/onedrive/polymarket_fill_risk	io.github.pipeworx-io/onedrive	live status →
mcp-registry/io.github.pipeworx-io/balldontlie/polymarket_fill_risk	io.github.pipeworx-io/balldontlie	live status →
mcp-registry/io.github.pipeworx-io/unpaywall/polymarket_fill_risk	io.github.pipeworx-io/unpaywall	live status →
mcp-registry/io.github.pipeworx-io/storting-no/polymarket_fill_risk	io.github.pipeworx-io/storting-no	live status →
mcp-registry/io.github.pipeworx-io/poetry/polymarket_fill_risk	io.github.pipeworx-io/poetry	live status →
mcp-registry/io.github.pipeworx-io/ticketmaster/polymarket_fill_risk	io.github.pipeworx-io/ticketmaster	live status →
mcp-registry/io.github.pipeworx-io/data-vermont/polymarket_fill_risk	io.github.pipeworx-io/data-vermont	live status →
mcp-registry/io.github.pipeworx-io/czso-cz/polymarket_fill_risk	io.github.pipeworx-io/czso-cz	live status →

FAQ

What is the best alternative to mcp-registry/com.quintadb/mcp/get_column_total?

mcp-registry/io.github.pipeworx-io/healthdata/polymarket_fill_risk is the top capability-matched alternative that's live right now. Other options: mcp-registry/io.github.pipeworx-io/entreprises-fr/polymarket_fill_risk, mcp-registry/io.github.pipeworx-io/wikidata-sparql/polymarket_fill_risk, mcp-registry/io.github.pipeworx-io/dane-gov-pl/polymarket_fill_risk, mcp-registry/io.github.pipeworx-io/onedrive/polymarket_fill_risk. Glimind ranks alternatives by semantic similarity and live health.

Is mcp-registry/com.quintadb/mcp/get_column_total down right now?

mcp-registry/com.quintadb/mcp/get_column_total's current verdict is "healthy". See its live status and score at https://glimind.com/tool/mcp-registry%2Fcom.quintadb%2Fmcp%2Fget_column_total.

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%2Fcom.quintadb%2Fmcp%2Fget_column_total or MCP find_alternatives. Check mcp-registry/com.quintadb/mcp/get_column_total's live status: https://glimind.com/tool/mcp-registry/com.quintadb/mcp/get_column_total.