Is waveguard_mechanism_probe working right now?

io.github.gpartin/waveguard · mcp-registry/io.github.gpartin/waveguard/waveguard_mechanism_probe

degraded
Recommendation: proceed with caution
uptime (30d probes)
93.5%
checks observed
3,466
p50 latency
8.6s
data basis
probe-history (3466 checks, 93.5% up)

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

Working alternatives

See all live alternatives to waveguard_mechanism_probe →

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:

One click:

Add to Cursor Add to VS Code

Claude Code

claude mcp add --transport http glimind https://glimind.com/mcp

Claude Desktop · Windsurf · Cline (mcpServers JSON)

{
  "mcpServers": {
    "glimind": {
      "type": "http",
      "url": "https://glimind.com/mcp"
    }
  }
}

Or wrap your calls with the SDK: npm i glimind · pip install glimind. See how it works

FAQ

Is waveguard_mechanism_probe working right now?

As of the latest check, waveguard_mechanism_probe (mcp-registry/io.github.gpartin/waveguard/waveguard_mechanism_probe) has a Glimind reliability score of 50/100 (grade D) and its current verdict is "degraded" — recommendation: proceed with caution. Glimind tracks this live from safe liveness probes plus privacy-clean real-usage outcomes.

How reliable is waveguard_mechanism_probe?

waveguard_mechanism_probe scores 50/100 (grade D) on the Glimind reliability standard. The score is neutral and unconflicted — Glimind sells no tools.

What should I do if waveguard_mechanism_probe is down or failing?

Degraded — retry at most once with backoff and a longer timeout; line up an alternative. Use a timeout around 25785ms. Live alternatives that do a similar job: waveguard_mechanism_probe, waveguard_counterfactual, waveguard_instability, waveguard_action_surface.

What are the best alternatives to waveguard_mechanism_probe?

Working alternatives ranked by capability similarity and live health: waveguard_mechanism_probe, waveguard_counterfactual, waveguard_instability, waveguard_action_surface. See each one's live status on Glimind.

How do I call waveguard_mechanism_probe reliably?

Before calling, check waveguard_mechanism_probe with Glimind (MCP: prepare_tool_call, or GET https://glimind.com/v1/prepare/mcp-registry%2Fio.github.gpartin%2Fwaveguard%2Fwaveguard_mechanism_probe) to get a known-good input shape, the expected output, a suggested timeout (~25785ms), 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/io.github.gpartin/waveguard/waveguard_mechanism_probe

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

Operator of io.github.gpartin/waveguard?

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%2Fio.github.gpartin%2Fwaveguard%2Fwaveguard_mechanism_probe. 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-10-16T23:28:08.347Z.

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.