io.github.Runewardd/runeward
io.github.Runewardd/runeward
Is the io.github.Runewardd/runeward MCP server down? Yes. It has given no valid answer since 2026-10-30: not found.
Governed execution cells for AI agents: Docker/K8s sandboxes with policy, audit, and approvals.
not found down since 2026-10-30 · probed 2026-11-14 · unchanged since 2026-11-06
Error response from daemon: error from registry: denied denied
- Run it
- docker run -i --rm ghcr.io/runewardd/runeward:v0.1.4 (stdio, probed in a container with the network off)
- Host
- ghcr.io
- Repository
- https://github.com/Runewardd/runeward
- Registry
- active, updated 2026-07-08 · registry entry
Compare this server with others.
More servers
Other registry entries on ghcr.io, the ones next to this name; all of them.
- Red Hat Lightspeed MCP io.github.RedHatInsights/insights-mcp · crashed on start
- GMO Coin FX MCP Server io.github.RikitoNoto/gmocoin-fx-mcp · needs network
- TractorBeeam365 MCP io.github.Ringosystems/tractorbeeam-mcp · alive
- MaxGraph io.github.RuMemory/maxgraph · not probed
- io.github.SamYuan1990/i18n-agent-action · not probed
- whyreach io.github.SandstromPL/whyreach · alive
- ScienceLogo io.github.ScienceLogo/sciencelogo-mcp · alive
- io.github.STR-Consulting/pacer-mcp · alive
Servers that mention approvals or execution.
- AgenticBooks ai.agenticbooks/books · needs auth
- ai.argushq/enforcement-database · no DNS
- DJZS Trust MCP ai.djzs/trust-mcp · alive
- Elicitly Pro ai.elicitly/pro · needs auth
- Foliora Managed AI Search ai.foliora/search · needs auth
- ai.geodesiclabs/governance-platform · alive
- InfraPulse ai.infrapulse/infrapulse · rejects our protocol version
- ai.syntitan/syntitan-mcp · needs auth
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-10-30, 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.