Is record_decision_context working right now?

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

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

Working alternatives

• create_decision com.decision-anchor/da
• create_decision AIOProductOS
• create_decision com.aioproductos/mcp
• decision_log_create_decision ai.decisionlog/mcp

See all live alternatives to record_decision_context →

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

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

FAQ

Is record_decision_context working right now?

As of the latest check, record_decision_context (mcp-registry/io.github.cuecrux/vaultcrux-memory-core/record_decision_context) 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 record_decision_context?

record_decision_context 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 record_decision_context 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 2661ms. Live alternatives that do a similar job: create_decision, create_decision, create_decision, decision_log_create_decision.

What are the best alternatives to record_decision_context?

Working alternatives ranked by capability similarity and live health: create_decision, create_decision, create_decision, decision_log_create_decision. See each one's live status on Glimind.

How do I call record_decision_context reliably?

Before calling, check record_decision_context with Glimind (MCP: prepare_tool_call, or GET https://glimind.com/v1/prepare/mcp-registry%2Fio.github.cuecrux%2Fvaultcrux-memory-core%2Frecord_decision_context) to get a known-good input shape, the expected output, a suggested timeout (~2661ms), 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](https://glimind.com/v1/badge/mcp-registry%2Fio.github.cuecrux%2Fvaultcrux-memory-core%2Frecord_decision_context.svg)](https://glimind.com/tool/mcp-registry%2Fio.github.cuecrux%2Fvaultcrux-memory-core%2Frecord_decision_context?ref=badge)

<a href="https://glimind.com/tool/mcp-registry%2Fio.github.cuecrux%2Fvaultcrux-memory-core%2Frecord_decision_context?ref=badge"><img src="https://glimind.com/v1/badge/mcp-registry%2Fio.github.cuecrux%2Fvaultcrux-memory-core%2Frecord_decision_context.svg" alt="Glimind reliability"></a>

.. image:: https://glimind.com/v1/badge/mcp-registry%2Fio.github.cuecrux%2Fvaultcrux-memory-core%2Frecord_decision_context.svg
   :target: https://glimind.com/tool/mcp-registry%2Fio.github.cuecrux%2Fvaultcrux-memory-core%2Frecord_decision_context?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%2Frecord_decision_context. 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-16T20:42:12.576Z.

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.