mcp-registry/io.github.jsonbored/metagraphed/list_fixtures / alternatives

Live alternatives to mcp-registry/io.github.jsonbored/metagraphed/list_fixtures

The best live alternatives to mcp-registry/io.github.jsonbored/metagraphed/list_fixtures right now are mcp-registry/io.github.pipeworx-io/opentopodata/search_within, mcp-registry/io.github.pipeworx-io/nypl/search_within, mcp-registry/io.github.pipeworx-io/data-sncf/search_within, mcp-registry/io.github.pipeworx-io/arcgis-linncounty/search_within, mcp-registry/io.github.pipeworx-io/arcgis-kansas/search_within — capability-matched and ranked by current reliability. mcp-registry/io.github.jsonbored/metagraphed/list_fixtures itself is currently "healthy".

alternative	server
mcp-registry/io.github.pipeworx-io/opentopodata/search_within	io.github.pipeworx-io/opentopodata	live status →
mcp-registry/io.github.pipeworx-io/nypl/search_within	io.github.pipeworx-io/nypl	live status →
mcp-registry/io.github.pipeworx-io/data-sncf/search_within	io.github.pipeworx-io/data-sncf	live status →
mcp-registry/io.github.pipeworx-io/arcgis-linncounty/search_within	io.github.pipeworx-io/arcgis-linncounty	live status →
mcp-registry/io.github.pipeworx-io/arcgis-kansas/search_within	io.github.pipeworx-io/arcgis-kansas	live status →
mcp-registry/io.github.pipeworx-io/arcgis-greenwood/search_within	io.github.pipeworx-io/arcgis-greenwood	live status →
mcp-registry/io.github.pipeworx-io/arcgis-detroit/search_within	io.github.pipeworx-io/arcgis-detroit	live status →
mcp-registry/io.github.pipeworx-io/arcgis-delawareco/search_within	io.github.pipeworx-io/arcgis-delawareco	live status →
mcp-registry/io.github.pipeworx-io/alchemy-eth/search_within	io.github.pipeworx-io/alchemy-eth	live status →
mcp-registry/io.github.pipeworx-io/airtable/search_within	io.github.pipeworx-io/airtable	live status →
mcp-registry/io.github.pipeworx-io/opentargets/search_within	io.github.pipeworx-io/opentargets	live status →
mcp-registry/io.github.pipeworx-io/npi-registry/search_within	io.github.pipeworx-io/npi-registry	live status →

FAQ

What is the best alternative to mcp-registry/io.github.jsonbored/metagraphed/list_fixtures?

mcp-registry/io.github.pipeworx-io/opentopodata/search_within is the top capability-matched alternative that's live right now. Other options: mcp-registry/io.github.pipeworx-io/nypl/search_within, mcp-registry/io.github.pipeworx-io/data-sncf/search_within, mcp-registry/io.github.pipeworx-io/arcgis-linncounty/search_within, mcp-registry/io.github.pipeworx-io/arcgis-kansas/search_within. Glimind ranks alternatives by semantic similarity and live health.

Is mcp-registry/io.github.jsonbored/metagraphed/list_fixtures down right now?

mcp-registry/io.github.jsonbored/metagraphed/list_fixtures's current verdict is "healthy". See its live status and score at https://glimind.com/tool/mcp-registry%2Fio.github.jsonbored%2Fmetagraphed%2Flist_fixtures.

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.jsonbored%2Fmetagraphed%2Flist_fixtures or MCP find_alternatives. Check mcp-registry/io.github.jsonbored/metagraphed/list_fixtures's live status: https://glimind.com/tool/mcp-registry/io.github.jsonbored/metagraphed/list_fixtures.