Is eyepup_ask working right now?

io.github.edholofy/eyepup · mcp-registry/io.github.edholofy/eyepup/eyepup_ask

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

See all live alternatives to eyepup_ask →

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

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

FAQ

Is eyepup_ask working right now?

As of the latest check, eyepup_ask (mcp-registry/io.github.edholofy/eyepup/eyepup_ask) has a Glimind reliability score of 90/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 eyepup_ask?

eyepup_ask scores 90/100 (grade A) on the Glimind reliability standard. The score is neutral and unconflicted — Glimind sells no tools.

What should I do if eyepup_ask is down or failing?

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

What are the best alternatives to eyepup_ask?

Glimind surfaces live, capability-matched alternatives the moment eyepup_ask degrades — query https://glimind.com/v1/alternatives/mcp-registry%2Fio.github.edholofy%2Feyepup%2Feyepup_ask.

How do I call eyepup_ask reliably?

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

<a href="https://glimind.com/tool/mcp-registry%2Fio.github.edholofy%2Feyepup%2Feyepup_ask?ref=badge"><img src="https://glimind.com/v1/badge/mcp-registry%2Fio.github.edholofy%2Feyepup%2Feyepup_ask.svg" alt="Glimind reliability"></a>

.. image:: https://glimind.com/v1/badge/mcp-registry%2Fio.github.edholofy%2Feyepup%2Feyepup_ask.svg
   :target: https://glimind.com/tool/mcp-registry%2Fio.github.edholofy%2Feyepup%2Feyepup_ask?ref=badge
   :alt: Glimind reliability

Operator of io.github.edholofy/eyepup?

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.edholofy%2Feyepup%2Feyepup_ask. 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-16T19:49:04.244Z.

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.