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

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

The best live alternatives to mcp-registry/com.adbutler/mcp-server/create_demand_source right now are mcp-registry/io.github.pipeworx-io/wordnik/subscribe, mcp-registry/io.github.pipeworx-io/19hz/subscribe, mcp-registry/io.github.pipeworx-io/todoist/subscribe, mcp-registry/io.github.pipeworx-io/japan-law/subscribe, mcp-registry/io.github.pipeworx-io/ecb/subscribe — capability-matched and ranked by current reliability. mcp-registry/com.adbutler/mcp-server/create_demand_source itself is currently "healthy".

alternative	server
mcp-registry/io.github.pipeworx-io/wordnik/subscribe	io.github.pipeworx-io/wordnik	live status →
mcp-registry/io.github.pipeworx-io/19hz/subscribe	io.github.pipeworx-io/19hz	live status →
mcp-registry/io.github.pipeworx-io/todoist/subscribe	io.github.pipeworx-io/todoist	live status →
mcp-registry/io.github.pipeworx-io/japan-law/subscribe	io.github.pipeworx-io/japan-law	live status →
mcp-registry/io.github.pipeworx-io/ecb/subscribe	io.github.pipeworx-io/ecb	live status →
mcp-registry/io.github.pipeworx-io/arcgis-roanoke/subscribe	io.github.pipeworx-io/arcgis-roanoke	live status →
mcp-registry/io.github.pipeworx-io/statfin-fi/subscribe	io.github.pipeworx-io/statfin-fi	live status →
mcp-registry/io.github.pipeworx-io/statbank-md/subscribe	io.github.pipeworx-io/statbank-md	live status →
mcp-registry/io.github.pipeworx-io/manifold/subscribe	io.github.pipeworx-io/manifold	live status →
mcp-registry/io.github.pipeworx-io/anilist/subscribe	io.github.pipeworx-io/anilist	live status →
mcp-registry/io.github.pipeworx-io/launches/subscribe	io.github.pipeworx-io/launches	live status →
mcp-registry/io.github.pipeworx-io/salesforce/subscribe	io.github.pipeworx-io/salesforce	live status →

FAQ

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

mcp-registry/io.github.pipeworx-io/wordnik/subscribe is the top capability-matched alternative that's live right now. Other options: mcp-registry/io.github.pipeworx-io/19hz/subscribe, mcp-registry/io.github.pipeworx-io/todoist/subscribe, mcp-registry/io.github.pipeworx-io/japan-law/subscribe, mcp-registry/io.github.pipeworx-io/ecb/subscribe. Glimind ranks alternatives by semantic similarity and live health.

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

mcp-registry/com.adbutler/mcp-server/create_demand_source's current verdict is "healthy". See its live status and score at https://glimind.com/tool/mcp-registry%2Fcom.adbutler%2Fmcp-server%2Fcreate_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%2Fcreate_demand_source or MCP find_alternatives. Check mcp-registry/com.adbutler/mcp-server/create_demand_source's live status: https://glimind.com/tool/mcp-registry/com.adbutler/mcp-server/create_demand_source.