glama/grinv/tmdb-mcp/find_by_imdb_id / alternatives

Live alternatives to glama/grinv/tmdb-mcp/find_by_imdb_id

The best live alternatives to glama/grinv/tmdb-mcp/find_by_imdb_id right now are mcp-registry/io.github.pipeworx-io/simbad/object, mcp-registry/io.github.pipeworx-io/bioregistry/resolve, mcp-registry/io.github.pipeworx-io/rdap/resolve_entity, mcp-registry/io.github.pipeworx-io/arcgis-novi/resolve_entity, mcp-registry/io.github.pipeworx-io/oqmd/resolve_entity — capability-matched and ranked by current reliability. glama/grinv/tmdb-mcp/find_by_imdb_id itself is currently "unknown".

alternative	server
mcp-registry/io.github.pipeworx-io/simbad/object	io.github.pipeworx-io/simbad	live status →
mcp-registry/io.github.pipeworx-io/bioregistry/resolve	io.github.pipeworx-io/bioregistry	live status →
mcp-registry/io.github.pipeworx-io/rdap/resolve_entity	io.github.pipeworx-io/rdap	live status →
mcp-registry/io.github.pipeworx-io/arcgis-novi/resolve_entity	io.github.pipeworx-io/arcgis-novi	live status →
mcp-registry/io.github.pipeworx-io/oqmd/resolve_entity	io.github.pipeworx-io/oqmd	live status →
mcp-registry/io.github.pipeworx-io/ssb-no/resolve_entity	io.github.pipeworx-io/ssb-no	live status →
mcp-registry/io.github.pipeworx-io/data-kcmo/resolve_entity	io.github.pipeworx-io/data-kcmo	live status →
mcp-registry/io.github.pipeworx-io/zenodo/resolve_entity	io.github.pipeworx-io/zenodo	live status →
mcp-registry/io.github.pipeworx-io/data-austin/resolve_entity	io.github.pipeworx-io/data-austin	live status →
mcp-registry/io.github.pipeworx-io/arcgis-glasgow/resolve_entity	io.github.pipeworx-io/arcgis-glasgow	live status →
mcp-registry/io.github.pipeworx-io/statscan/resolve_entity	io.github.pipeworx-io/statscan	live status →
mcp-registry/io.github.pipeworx-io/clickup/resolve_entity	io.github.pipeworx-io/clickup	live status →

FAQ

What is the best alternative to glama/grinv/tmdb-mcp/find_by_imdb_id?

mcp-registry/io.github.pipeworx-io/simbad/object is the top capability-matched alternative that's live right now. Other options: mcp-registry/io.github.pipeworx-io/bioregistry/resolve, mcp-registry/io.github.pipeworx-io/rdap/resolve_entity, mcp-registry/io.github.pipeworx-io/arcgis-novi/resolve_entity, mcp-registry/io.github.pipeworx-io/oqmd/resolve_entity. Glimind ranks alternatives by semantic similarity and live health.

Is glama/grinv/tmdb-mcp/find_by_imdb_id down right now?

glama/grinv/tmdb-mcp/find_by_imdb_id's current verdict is "unknown". See its live status and score at https://glimind.com/tool/glama%2Fgrinv%2Ftmdb-mcp%2Ffind_by_imdb_id.

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/glama%2Fgrinv%2Ftmdb-mcp%2Ffind_by_imdb_id or MCP find_alternatives. Check glama/grinv/tmdb-mcp/find_by_imdb_id's live status: https://glimind.com/tool/glama/grinv/tmdb-mcp/find_by_imdb_id.