mcp-registry/com.adbutler/mcp-server/get_demand_source / alternatives

Live alternatives to mcp-registry/com.adbutler/mcp-server/get_demand_source

The best live alternatives to mcp-registry/com.adbutler/mcp-server/get_demand_source right now are mcp-registry/io.github.pipeworx-io/arcgis-sanjose/deep_research, mcp-registry/io.github.pipeworx-io/arcgis-tallahassee/deep_research, mcp-registry/io.github.pipeworx-io/arcgis-seattle/deep_research, mcp-registry/io.github.pipeworx-io/arcgis-princewilliam/deep_research, mcp-registry/io.github.pipeworx-io/arcgis-peoria/deep_research — capability-matched and ranked by current reliability. mcp-registry/com.adbutler/mcp-server/get_demand_source itself is currently "healthy".

alternative	server
mcp-registry/io.github.pipeworx-io/arcgis-sanjose/deep_research	io.github.pipeworx-io/arcgis-sanjose	live status →
mcp-registry/io.github.pipeworx-io/arcgis-tallahassee/deep_research	io.github.pipeworx-io/arcgis-tallahassee	live status →
mcp-registry/io.github.pipeworx-io/arcgis-seattle/deep_research	io.github.pipeworx-io/arcgis-seattle	live status →
mcp-registry/io.github.pipeworx-io/arcgis-princewilliam/deep_research	io.github.pipeworx-io/arcgis-princewilliam	live status →
mcp-registry/io.github.pipeworx-io/arcgis-peoria/deep_research	io.github.pipeworx-io/arcgis-peoria	live status →
mcp-registry/io.github.pipeworx-io/arcgis-montana/deep_research	io.github.pipeworx-io/arcgis-montana	live status →
mcp-registry/io.github.pipeworx-io/arcgis-lakeland/deep_research	io.github.pipeworx-io/arcgis-lakeland	live status →
mcp-registry/io.github.pipeworx-io/arcgis-lincolncountync/deep_research	io.github.pipeworx-io/arcgis-lincolncountync	live status →
mcp-registry/io.github.pipeworx-io/us-iso-grid/deep_research	io.github.pipeworx-io/us-iso-grid	live status →
mcp-registry/io.github.pipeworx-io/stocktwits/deep_research	io.github.pipeworx-io/stocktwits	live status →
mcp-registry/io.github.pipeworx-io/stratz/deep_research	io.github.pipeworx-io/stratz	live status →
mcp-registry/io.github.pipeworx-io/swisstransport/deep_research	io.github.pipeworx-io/swisstransport	live status →

FAQ

What is the best alternative to mcp-registry/com.adbutler/mcp-server/get_demand_source?

mcp-registry/io.github.pipeworx-io/arcgis-sanjose/deep_research is the top capability-matched alternative that's live right now. Other options: mcp-registry/io.github.pipeworx-io/arcgis-tallahassee/deep_research, mcp-registry/io.github.pipeworx-io/arcgis-seattle/deep_research, mcp-registry/io.github.pipeworx-io/arcgis-princewilliam/deep_research, mcp-registry/io.github.pipeworx-io/arcgis-peoria/deep_research. Glimind ranks alternatives by semantic similarity and live health.

Is mcp-registry/com.adbutler/mcp-server/get_demand_source down right now?

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

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.adbutler%2Fmcp-server%2Fget_demand_source or MCP find_alternatives. Check mcp-registry/com.adbutler/mcp-server/get_demand_source's live status: https://glimind.com/tool/mcp-registry/com.adbutler/mcp-server/get_demand_source.