mcp-registry/com.weverlabs/agentic-rails/get_movement_fee_schedule working right now?See all live alternatives to mcp-registry/com.weverlabs/agentic-rails/get_movement_fee_schedule →
As of the latest check, mcp-registry/com.weverlabs/agentic-rails/get_movement_fee_schedule has a Glimind reliability score of 85/100 (grade B) and its current verdict is "healthy" — recommendation: proceed. Glimind tracks this live from safe liveness probes plus privacy-clean real-usage outcomes.
mcp-registry/com.weverlabs/agentic-rails/get_movement_fee_schedule scores 85/100 (grade B) on the Glimind reliability standard. The score is neutral and unconflicted — Glimind sells no tools.
Healthy — standard retry (1–2x) with jitter on transient errors. Use a timeout around 1527ms. Check Glimind for a live alternative before retrying.
Glimind surfaces live, capability-matched alternatives the moment mcp-registry/com.weverlabs/agentic-rails/get_movement_fee_schedule degrades — query https://glimind.com/v1/alternatives/mcp-registry%2Fcom.weverlabs%2Fagentic-rails%2Fget_movement_fee_schedule.
Before calling, check mcp-registry/com.weverlabs/agentic-rails/get_movement_fee_schedule with Glimind (MCP: prepare_tool_call, or GET https://glimind.com/v1/prepare/mcp-registry%2Fcom.weverlabs%2Fagentic-rails%2Fget_movement_fee_schedule) to get a known-good input shape, the expected output, a suggested timeout (~1527ms), and a live fallback.
Show live reliability in your README or status page:
[](https://glimind.com/tool/mcp-registry%2Fcom.weverlabs%2Fagentic-rails%2Fget_movement_fee_schedule)
Agents: query https://glimind.com/mcp (MCP) or GET https://glimind.com/v1/health/mcp-registry%2Fcom.weverlabs%2Fagentic-rails%2Fget_movement_fee_schedule. 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-30T09:08:33.078Z.