Is extend_memory working right now?
io.github.agtrepo/agtrepo-memory · mcp-registry/io.github.agtrepo/agtrepo-memory/extend_memory
Recent contract changes
Schema/catalog changes Glimind observed on this server — a changed contract can silently break a previously working call.
schema_changed—store_persistent_memory(2026-10-02)schema_changed—share_memory_key(2026-10-02)schema_changed—register_key_release(2026-10-02)schema_changed—register_key_release(2026-10-02)added—send_feedback(2026-09-10)
See all live alternatives to extend_memory →
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
FAQ
Is extend_memory working right now?
As of the latest check, extend_memory (mcp-registry/io.github.agtrepo/agtrepo-memory/extend_memory) has a Glimind reliability score of 95/100 (grade A) 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 extend_memory?
extend_memory scores 95/100 (grade A) on the Glimind reliability standard. The score is neutral and unconflicted — Glimind sells no tools.
What should I do if extend_memory is down or failing?
Healthy — standard retry (1–2x) with jitter on transient errors. Use a timeout around 14673ms. Check Glimind for a live alternative before retrying.
What are the best alternatives to extend_memory?
Glimind surfaces live, capability-matched alternatives the moment extend_memory degrades — query https://glimind.com/v1/alternatives/mcp-registry%2Fio.github.agtrepo%2Fagtrepo-memory%2Fextend_memory.
How do I call extend_memory reliably?
Before calling, check extend_memory with Glimind (MCP: prepare_tool_call, or GET https://glimind.com/v1/prepare/mcp-registry%2Fio.github.agtrepo%2Fagtrepo-memory%2Fextend_memory) to get a known-good input shape, the expected output, a suggested timeout (~14673ms), 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:
[](https://glimind.com/tool/mcp-registry%2Fio.github.agtrepo%2Fagtrepo-memory%2Fextend_memory?ref=badge)
<a href="https://glimind.com/tool/mcp-registry%2Fio.github.agtrepo%2Fagtrepo-memory%2Fextend_memory?ref=badge"><img src="https://glimind.com/v1/badge/mcp-registry%2Fio.github.agtrepo%2Fagtrepo-memory%2Fextend_memory.svg" alt="Glimind reliability"></a>
.. image:: https://glimind.com/v1/badge/mcp-registry%2Fio.github.agtrepo%2Fagtrepo-memory%2Fextend_memory.svg :target: https://glimind.com/tool/mcp-registry%2Fio.github.agtrepo%2Fagtrepo-memory%2Fextend_memory?ref=badge :alt: Glimind reliability
Operator of io.github.agtrepo/agtrepo-memory?
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.agtrepo%2Fagtrepo-memory%2Fextend_memory. 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-03T08:06:48.851Z.
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.