mcp-registry/io.revise/mcp-server/rename_document / alternatives

Live alternatives to mcp-registry/io.revise/mcp-server/rename_document

The best live alternatives to mcp-registry/io.revise/mcp-server/rename_document right now are mcp-registry/io.famulor/famulor-mcp/update_document, mcp-registry/io.github.mila-gg/mcp-server/update_document, mcp-registry/to.plate/mcp/update_section, mcp-registry/io.github.rationalbloks/rationalbloks-mcp/rename_project, mcp-registry/io.github.itsmalware/the-lounge/ruby_update_doc — capability-matched and ranked by current reliability. mcp-registry/io.revise/mcp-server/rename_document itself is currently "healthy".

alternative	server
mcp-registry/io.famulor/famulor-mcp/update_document	io.famulor/famulor-mcp	live status →
mcp-registry/io.github.mila-gg/mcp-server/update_document	io.github.mila-gg/mcp-server	live status →
mcp-registry/to.plate/mcp/update_section	to.plate/mcp	live status →
mcp-registry/io.github.rationalbloks/rationalbloks-mcp/rename_project	io.github.rationalbloks/rationalbloks-mcp	live status →
mcp-registry/io.github.itsmalware/the-lounge/ruby_update_doc	io.github.ItsMalware/the-lounge	live status →
mcp-registry/to.plate/mcp/update_project	to.plate/mcp	live status →
mcp-registry/io.github.philipand/mkdshare/update_document	io.github.PhilipAnd/mkdshare	live status →
mcp-registry/io.tinyfn/tinyfn/title_case	io.tinyfn/tinyfn	live status →
mcp-registry/io.stablebaseline/sb/deleteDocument	io.stablebaseline/sb	live status →
mcp-registry/com.googleapis.firestore/mcp/update_document	com.googleapis.firestore/mcp	live status →
mcp-registry/io.famulor/famulor-mcp/update_label	io.famulor/famulor-mcp	live status →
mcp-registry/io.tinyfn/tinyfn/to_title_case	io.tinyfn/tinyfn	live status →

FAQ

What is the best alternative to mcp-registry/io.revise/mcp-server/rename_document?

mcp-registry/io.famulor/famulor-mcp/update_document is the top capability-matched alternative that's live right now. Other options: mcp-registry/io.github.mila-gg/mcp-server/update_document, mcp-registry/to.plate/mcp/update_section, mcp-registry/io.github.rationalbloks/rationalbloks-mcp/rename_project, mcp-registry/io.github.itsmalware/the-lounge/ruby_update_doc. Glimind ranks alternatives by semantic similarity and live health.

Is mcp-registry/io.revise/mcp-server/rename_document down right now?

mcp-registry/io.revise/mcp-server/rename_document's current verdict is "healthy". See its live status and score at https://glimind.com/tool/mcp-registry%2Fio.revise%2Fmcp-server%2Frename_document.

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.revise%2Fmcp-server%2Frename_document or MCP find_alternatives. Check mcp-registry/io.revise/mcp-server/rename_document's live status: https://glimind.com/tool/mcp-registry/io.revise/mcp-server/rename_document.