Is check_claim working right now?

io.github.cuecrux/vaultcrux-memory-core · mcp-registry/io.github.cuecrux/vaultcrux-memory-core/check_claim

healthy
Recommendation: proceed
uptime (30d probes)
99.9%
checks observed
3,714
p50 latency
2.6s
data basis
probe-history (3714 checks, 99.9% up)

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

See all live alternatives to check_claim →

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 check_claim working right now?

As of the latest check, check_claim (mcp-registry/io.github.cuecrux/vaultcrux-memory-core/check_claim) has a Glimind reliability score of 87/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.

How reliable is check_claim?

check_claim scores 87/100 (grade B) on the Glimind reliability standard. The score is neutral and unconflicted — Glimind sells no tools.

What should I do if check_claim is down or failing?

Healthy — standard retry (1–2x) with jitter on transient errors. Use a timeout around 7692ms. Check Glimind for a live alternative before retrying.

What are the best alternatives to check_claim?

Glimind surfaces live, capability-matched alternatives the moment check_claim degrades — query https://glimind.com/v1/alternatives/mcp-registry%2Fio.github.cuecrux%2Fvaultcrux-memory-core%2Fcheck_claim.

How do I call check_claim reliably?

Before calling, check check_claim with Glimind (MCP: prepare_tool_call, or GET https://glimind.com/v1/prepare/mcp-registry%2Fio.github.cuecrux%2Fvaultcrux-memory-core%2Fcheck_claim) to get a known-good input shape, the expected output, a suggested timeout (~7692ms), 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.cuecrux/vaultcrux-memory-core/check_claim

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

Operator of io.github.cuecrux/vaultcrux-memory-core?

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.cuecrux%2Fvaultcrux-memory-core%2Fcheck_claim. 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-03T20:10:16.720Z.

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.