Is workflow_step_compensate working right now?

xyz.tenzro/tenzro · mcp-registry/xyz.tenzro/tenzro/workflow_step_compensate

down
Recommendation: avoid
uptime (30d probes)
99.6%
checks observed
5,394
p50 latency
2.4s
data basis
probe-history (5394 checks, 99.6% up)

Recovery track record: 7 outages in 90 days, median time-to-recovery 10 min.

Recent contract changes

Schema/catalog changes Glimind observed on this server — a changed contract can silently break a previously working call.

Working alternatives

See all live alternatives to workflow_step_compensate →

Never call a dead tool again

Agents that check Glimind first make fewer failed calls, waste fewer tokens, and auto-route around outages like this one. Add it in ~10 seconds — free, no signup:

# MCP client — add one endpoint:
https://glimind.com/mcp

# or wrap your calls with the SDK:
npm i glimind          # pip install glimind

Get a free key See how it works

FAQ

Is workflow_step_compensate working right now?

As of the latest check, workflow_step_compensate (mcp-registry/xyz.tenzro/tenzro/workflow_step_compensate) has a Glimind reliability score of 38/100 (grade F) and its current verdict is "down" — recommendation: avoid. Glimind tracks this live from safe liveness probes plus privacy-clean real-usage outcomes.

How reliable is workflow_step_compensate?

workflow_step_compensate scores 38/100 (grade F) on the Glimind reliability standard. The score is neutral and unconflicted — Glimind sells no tools.

What should I do if workflow_step_compensate is down or failing?

Tool is down — don't retry now; switch to a live alternative or back off for minutes. Use a timeout around 7104ms. Live alternatives that do a similar job: util_step_budget_plan, execute_composition, run_workflow, build_stake_tx.

What are the best alternatives to workflow_step_compensate?

Working alternatives ranked by capability similarity and live health: util_step_budget_plan, execute_composition, run_workflow, build_stake_tx. See each one's live status on Glimind.

How do I call workflow_step_compensate reliably?

Before calling, check workflow_step_compensate with Glimind (MCP: prepare_tool_call, or GET https://glimind.com/v1/prepare/mcp-registry%2Fxyz.tenzro%2Ftenzro%2Fworkflow_step_compensate) to get a known-good input shape, the expected output, a suggested timeout (~7104ms), and a live fallback.

Embed this live badge

Show live reliability in your README or status page. It auto-updates and links back here — copy one:

Glimind reliability badge for mcp-registry/xyz.tenzro/tenzro/workflow_step_compensate

Markdown 
[![Glimind reliability](https://glimind.com/v1/badge/mcp-registry%2Fxyz.tenzro%2Ftenzro%2Fworkflow_step_compensate.svg)](https://glimind.com/tool/mcp-registry%2Fxyz.tenzro%2Ftenzro%2Fworkflow_step_compensate?ref=badge)
HTML 
<a href="https://glimind.com/tool/mcp-registry%2Fxyz.tenzro%2Ftenzro%2Fworkflow_step_compensate?ref=badge"><img src="https://glimind.com/v1/badge/mcp-registry%2Fxyz.tenzro%2Ftenzro%2Fworkflow_step_compensate.svg" alt="Glimind reliability"></a>
reStructuredText 
.. image:: https://glimind.com/v1/badge/mcp-registry%2Fxyz.tenzro%2Ftenzro%2Fworkflow_step_compensate.svg
   :target: https://glimind.com/tool/mcp-registry%2Fxyz.tenzro%2Ftenzro%2Fworkflow_step_compensate?ref=badge
   :alt: Glimind reliability

Operator of xyz.tenzro/tenzro?

Claim this listing → Prove you control this server (GitHub repo, live endpoint, or DNS — automated, ~1 min) to unlock the Verified operator marker, a remediation checklist (exactly why your score is what it is + how to raise it), and owner analytics. Or just embed the badge above and improve your score by having users report real outcomes (privacy-clean) via the free SDK. Glimind is neutral and sells no tools — the score is never for sale, so the fastest path to a better score is real uptime plus real usage.

Get the data (agents)

Query https://glimind.com/mcp (MCP) or GET https://glimind.com/v1/health/mcp-registry%2Fxyz.tenzro%2Ftenzro%2Fworkflow_step_compensate. The signed reliability feed for gateways/routers: GET https://glimind.com/v1/reliability/feed.

Rating methodology is transparent and neutral — Glimind sells no tools and runs no integrations; it only measures. Updated 2026-08-17T18:17:09.374Z.

This score is an automated estimate derived from safe liveness probes and privacy-clean outcomes reported by users; it may be incomplete, delayed, or inaccurate, and reflects reachability from Glimind's vantage point — not a statement of fact about the service. Glimind is not affiliated with, endorsed by, or acting for this tool or its operator; all names belong to their owners. Operator? Request a correction, or remove your server from measurement, via https://glimind.com/opt-out or [email protected] — we act promptly.