Is mcp-registry/ai.adeu/adeu/read_docx working right now?
See all live alternatives to mcp-registry/ai.adeu/adeu/read_docx →
FAQ
Is mcp-registry/ai.adeu/adeu/read_docx working right now?
mcp-registry/ai.adeu/adeu/read_docx is currently unrated by Glimind (insufficient signal). Verdict: unknown. Glimind tracks this live from safe liveness probes plus privacy-clean real-usage outcomes.
How reliable is mcp-registry/ai.adeu/adeu/read_docx?
mcp-registry/ai.adeu/adeu/read_docx does not yet have enough data for a score. The score is neutral and unconflicted — Glimind sells no tools.
What should I do if mcp-registry/ai.adeu/adeu/read_docx is down or failing?
No signal yet — proceed; on failure retry once, then report the outcome. Check Glimind for a live alternative before retrying.
What are the best alternatives to mcp-registry/ai.adeu/adeu/read_docx?
Glimind surfaces live, capability-matched alternatives the moment mcp-registry/ai.adeu/adeu/read_docx degrades — query https://glimind.com/v1/alternatives/mcp-registry%2Fai.adeu%2Fadeu%2Fread_docx.
How do I call mcp-registry/ai.adeu/adeu/read_docx reliably?
Before calling, check mcp-registry/ai.adeu/adeu/read_docx with Glimind (MCP: prepare_tool_call, or GET https://glimind.com/v1/prepare/mcp-registry%2Fai.adeu%2Fadeu%2Fread_docx) to get a known-good input shape, the expected output, a suggested timeout, and a live fallback.
Embed this badge
Show live reliability in your README or status page:
[](https://glimind.com/tool/mcp-registry%2Fai.adeu%2Fadeu%2Fread_docx)
Get the data
Agents: query https://glimind.com/mcp (MCP) or GET https://glimind.com/v1/health/mcp-registry%2Fai.adeu%2Fadeu%2Fread_docx. Install the SDK to contribute outcomes (privacy-preserving) and sharpen this rating — free key · docs.
Rating methodology is transparent and neutral — Glimind sells no tools and runs no integrations; it only measures. Updated 2026-06-30T19:25:41.269Z.