mcp-registry/io.github.pipeworx-io/zenodo/record / alternatives

Live alternatives to mcp-registry/io.github.pipeworx-io/zenodo/record

The best live alternatives to mcp-registry/io.github.pipeworx-io/zenodo/record right now are mcp-registry/io.github.pipeworx-io/orcid/record, mcp-registry/io.github.pipeworx-io/europeana/record, mcp-registry/io.github.pipeworx-io/digitalnz/record, mcp-registry/io.github.pipeworx-io/pangaea/dataset, mcp-registry/io.github.pipeworx-io/zoho_crm/zoho_get_record — capability-matched and ranked by current reliability. mcp-registry/io.github.pipeworx-io/zenodo/record itself is currently "healthy".

alternative	server
mcp-registry/io.github.pipeworx-io/orcid/record	io.github.pipeworx-io/orcid	live status →
mcp-registry/io.github.pipeworx-io/europeana/record	io.github.pipeworx-io/europeana	live status →
mcp-registry/io.github.pipeworx-io/digitalnz/record	io.github.pipeworx-io/digitalnz	live status →
mcp-registry/io.github.pipeworx-io/pangaea/dataset	io.github.pipeworx-io/pangaea	live status →
mcp-registry/io.github.pipeworx-io/zoho_crm/zoho_get_record	io.github.pipeworx-io/zoho_crm	live status →
mcp-registry/io.github.pipeworx-io/hathitrust/get_record	io.github.pipeworx-io/hathitrust	live status →
mcp-registry/io.github.pipeworx-io/monarch-initiative/entity	io.github.pipeworx-io/monarch-initiative	live status →
mcp-registry/io.github.pipeworx-io/inspire-hep/literature	io.github.pipeworx-io/inspire-hep	live status →
mcp-registry/io.github.pipeworx-io/orcid/work	io.github.pipeworx-io/orcid	live status →
mcp-registry/io.github.pipeworx-io/inspire-hep/author	io.github.pipeworx-io/inspire-hep	live status →
mcp-registry/io.github.pipeworx-io/datagov-au/resource	io.github.pipeworx-io/datagov-au	live status →
mcp-registry/ru.quintadb/mcp/get_record	ru.quintadb/mcp	live status →

FAQ

What is the best alternative to mcp-registry/io.github.pipeworx-io/zenodo/record?

mcp-registry/io.github.pipeworx-io/orcid/record is the top capability-matched alternative that's live right now. Other options: mcp-registry/io.github.pipeworx-io/europeana/record, mcp-registry/io.github.pipeworx-io/digitalnz/record, mcp-registry/io.github.pipeworx-io/pangaea/dataset, mcp-registry/io.github.pipeworx-io/zoho_crm/zoho_get_record. Glimind ranks alternatives by semantic similarity and live health.

Is mcp-registry/io.github.pipeworx-io/zenodo/record down right now?

mcp-registry/io.github.pipeworx-io/zenodo/record's current verdict is "healthy". See its live status and score at https://glimind.com/tool/mcp-registry%2Fio.github.pipeworx-io%2Fzenodo%2Frecord.

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.pipeworx-io%2Fzenodo%2Frecord or MCP find_alternatives. Check mcp-registry/io.github.pipeworx-io/zenodo/record's live status: https://glimind.com/tool/mcp-registry/io.github.pipeworx-io/zenodo/record.