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

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

The best live alternatives to mcp-registry/com.adbutler/mcp-server/get_data_key right now are mcp-registry/io.github.pipeworx-io/data-batonrouge/recall, mcp-registry/io.github.pipeworx-io/science-feeds/recall, mcp-registry/io.github.pipeworx-io/fcc/recall, mcp-registry/io.github.pipeworx-io/fbi-wanted/recall, mcp-registry/io.github.pipeworx-io/arcgis-maricopa/recall — capability-matched and ranked by current reliability. mcp-registry/com.adbutler/mcp-server/get_data_key itself is currently "healthy".

alternative	server
mcp-registry/io.github.pipeworx-io/data-batonrouge/recall	io.github.pipeworx-io/data-batonrouge	live status →
mcp-registry/io.github.pipeworx-io/science-feeds/recall	io.github.pipeworx-io/science-feeds	live status →
mcp-registry/io.github.pipeworx-io/fcc/recall	io.github.pipeworx-io/fcc	live status →
mcp-registry/io.github.pipeworx-io/fbi-wanted/recall	io.github.pipeworx-io/fbi-wanted	live status →
mcp-registry/io.github.pipeworx-io/arcgis-maricopa/recall	io.github.pipeworx-io/arcgis-maricopa	live status →
mcp-registry/io.github.pipeworx-io/dadjokes/recall	io.github.pipeworx-io/dadjokes	live status →
mcp-registry/io.github.pipeworx-io/arcgis-eagan/recall	io.github.pipeworx-io/arcgis-eagan	live status →
mcp-registry/io.github.pipeworx-io/openfigi/recall	io.github.pipeworx-io/openfigi	live status →
mcp-registry/io.github.pipeworx-io/fas/recall	io.github.pipeworx-io/fas	live status →
mcp-registry/io.github.pipeworx-io/stooq/recall	io.github.pipeworx-io/stooq	live status →
mcp-registry/io.github.pipeworx-io/arcgis-kamloops/recall	io.github.pipeworx-io/arcgis-kamloops	live status →
mcp-registry/io.github.pipeworx-io/owid/recall	io.github.pipeworx-io/owid	live status →

FAQ

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

mcp-registry/io.github.pipeworx-io/data-batonrouge/recall is the top capability-matched alternative that's live right now. Other options: mcp-registry/io.github.pipeworx-io/science-feeds/recall, mcp-registry/io.github.pipeworx-io/fcc/recall, mcp-registry/io.github.pipeworx-io/fbi-wanted/recall, mcp-registry/io.github.pipeworx-io/arcgis-maricopa/recall. Glimind ranks alternatives by semantic similarity and live health.

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

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

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_data_key or MCP find_alternatives. Check mcp-registry/com.adbutler/mcp-server/get_data_key's live status: https://glimind.com/tool/mcp-registry/com.adbutler/mcp-server/get_data_key.