mcp-registry/io.github.pipeworx-io/trove/work / alternatives

Live alternatives to mcp-registry/io.github.pipeworx-io/trove/work

The best live alternatives to mcp-registry/io.github.pipeworx-io/trove/work right now are mcp-registry/io.github.pipeworx-io/nypl/item, mcp-registry/io.github.pipeworx-io/smithsonian/object, mcp-registry/io.github.pipeworx-io/harvard-art/object, mcp-registry/io.github.pipeworx-io/europeana/record, mcp-registry/io.github.pipeworx-io/digitalnz/record — capability-matched and ranked by current reliability. mcp-registry/io.github.pipeworx-io/trove/work itself is currently "healthy".

alternative	server
mcp-registry/io.github.pipeworx-io/nypl/item	io.github.pipeworx-io/nypl	live status →
mcp-registry/io.github.pipeworx-io/smithsonian/object	io.github.pipeworx-io/smithsonian	live status →
mcp-registry/io.github.pipeworx-io/harvard-art/object	io.github.pipeworx-io/harvard-art	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/art/get_artwork	io.github.pipeworx-io/art	live status →
mcp-registry/io.github.pipeworx-io/guild-wars-2/items	io.github.pipeworx-io/guild-wars-2	live status →
mcp-registry/to.plate/mcp/get_task	to.plate/mcp	live status →
mcp-registry/io.github.pipeworx-io/books/get_book_work	io.github.pipeworx-io/books	live status →
mcp-registry/io.github.olijboyd/tomevault/get_vault_item	io.github.olijboyd/tomevault	live status →
mcp-registry/com.1stdibs/1stdibs/item_details	com.1stdibs/1stDibs	live status →
mcp-registry/io.github.branch-docs/ai/fetch	io.github.branch-docs/ai	live status →

FAQ

What is the best alternative to mcp-registry/io.github.pipeworx-io/trove/work?

mcp-registry/io.github.pipeworx-io/nypl/item is the top capability-matched alternative that's live right now. Other options: mcp-registry/io.github.pipeworx-io/smithsonian/object, mcp-registry/io.github.pipeworx-io/harvard-art/object, mcp-registry/io.github.pipeworx-io/europeana/record, mcp-registry/io.github.pipeworx-io/digitalnz/record. Glimind ranks alternatives by semantic similarity and live health.

Is mcp-registry/io.github.pipeworx-io/trove/work down right now?

mcp-registry/io.github.pipeworx-io/trove/work's current verdict is "healthy". See its live status and score at https://glimind.com/tool/mcp-registry%2Fio.github.pipeworx-io%2Ftrove%2Fwork.

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%2Ftrove%2Fwork or MCP find_alternatives. Check mcp-registry/io.github.pipeworx-io/trove/work's live status: https://glimind.com/tool/mcp-registry/io.github.pipeworx-io/trove/work.