Is get_auth_logout working right now?
io.github.michal-lefler/secureflows-mcp-server · mcp-registry/io.github.michal-lefler/secureflows-mcp-server/get_auth_logout
Recent contract changes
Schema/catalog changes Glimind observed on this server — a changed contract can silently break a previously working call.
added—post_sessions_renew_session_token(2026-08-20)added—get_sessions_get_key(2026-08-20)added—post_sessions_set_key(2026-08-20)added—get_sessions(2026-08-20)added—post_sessions(2026-08-20)
See all live alternatives to get_auth_logout →
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 get_auth_logout working right now?
As of the latest check, get_auth_logout (mcp-registry/io.github.michal-lefler/secureflows-mcp-server/get_auth_logout) has a Glimind reliability score of 89/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 get_auth_logout?
get_auth_logout scores 89/100 (grade B) on the Glimind reliability standard. The score is neutral and unconflicted — Glimind sells no tools.
What should I do if get_auth_logout is down or failing?
Healthy — standard retry (1–2x) with jitter on transient errors. Use a timeout around 7512ms. Check Glimind for a live alternative before retrying.
What are the best alternatives to get_auth_logout?
Glimind surfaces live, capability-matched alternatives the moment get_auth_logout degrades — query https://glimind.com/v1/alternatives/mcp-registry%2Fio.github.michal-lefler%2Fsecureflows-mcp-server%2Fget_auth_logout.
How do I call get_auth_logout reliably?
Before calling, check get_auth_logout with Glimind (MCP: prepare_tool_call, or GET https://glimind.com/v1/prepare/mcp-registry%2Fio.github.michal-lefler%2Fsecureflows-mcp-server%2Fget_auth_logout) to get a known-good input shape, the expected output, a suggested timeout (~7512ms), 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.michal-lefler%2Fsecureflows-mcp-server%2Fget_auth_logout?ref=badge)
<a href="https://glimind.com/tool/mcp-registry%2Fio.github.michal-lefler%2Fsecureflows-mcp-server%2Fget_auth_logout?ref=badge"><img src="https://glimind.com/v1/badge/mcp-registry%2Fio.github.michal-lefler%2Fsecureflows-mcp-server%2Fget_auth_logout.svg" alt="Glimind reliability"></a>
.. image:: https://glimind.com/v1/badge/mcp-registry%2Fio.github.michal-lefler%2Fsecureflows-mcp-server%2Fget_auth_logout.svg :target: https://glimind.com/tool/mcp-registry%2Fio.github.michal-lefler%2Fsecureflows-mcp-server%2Fget_auth_logout?ref=badge :alt: Glimind reliability
Operator of io.github.michal-lefler/secureflows-mcp-server?
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.michal-lefler%2Fsecureflows-mcp-server%2Fget_auth_logout. 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-25T03:10:21.876Z.
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.