io.github.hynix666/ultra-e2e-test
ultra-e2e-test tasks
Is the ultra-e2e-test tasks MCP server down? Yes. It has given no valid answer since 2026-11-01: not found.
List, create and move tasks through todo, in progress and done.
not found down since 2026-11-01 · probed 2026-11-14 · unchanged since 2026-11-08
Error response from daemon: error from registry: denied denied
- Run it
- docker run -i --rm ghcr.io/hynix666/ultra-e2e-test-mcp-server:0.1.1 (stdio, probed in a container with the network off)
- Host
- ghcr.io
- Repository
- https://github.com/hynix666/ultra-e2e-test
- Registry
- active, updated 2026-09-18 · registry entry
Compare this server with others.
More servers
Other registry entries on ghcr.io, the ones next to this name; all of them.
- Nordnet Portfolio io.github.hpasic/nordnet-mcp · crashed on start
- io.github.hughhan1/mysql · not probed
- droidmap io.github.hussainshirazi/droidmap · crashed on start
- HydraDNS io.github.hydradns/hydra-mcp · not found
- Polyglot Database MCP io.github.hyperpolymath/poly-db-mcp · not found
- Polyglot SSG MCP io.github.hyperpolymath/poly-ssg-mcp · not found
- io.github.ibeal/tidal-mcp · needs env
- io.github.iflytek/dolphin-mcp-pilot · not probed
Servers that mention ultra.
- Gossiper Shopify Admin MCP Server ai.gossiper/shopify-admin-mcp · needs auth
- Ultra Prompt co.ultraprompt/ultra-prompt · needs auth
- DefaultRank com.defaultrank/mcp · alive
- Due Date com.gumballtools/due-date · alive
- com.trailweights/trailweights-mcp · server error
- com.trycloudflare.candy-josh-writers-balance/yultrace-audit · no DNS
- com.trycloudflare.candy-josh-writers-balance/yultrace-bounty-feed · no DNS
- com.trycloudflare.urgent-clean-occupied-catalogs/yultrace-audit · no DNS
Badge for the README
The result of the latest probe, the tool count and the token cost. The feed has an entry for every probe that changed them.
A mail when this server changes
Stops answering, comes back, tool set or cost changes. One confirmation mail first, a stop link in every mail.
For the publisher
- No valid answer since 2026-11-01, in every probe since then.
- The endpoint answers HTTP 404. The registry entry points to a URL that is not an MCP endpoint any more. Publish a new version of the registry entry with the current URL.