io.github.wyre-technology/keeper-mcp

Keeper Secrets Manager

Is the Keeper Secrets Manager MCP server down? It gave no valid answer in the probe of 2026-11-12: timeout. One failed probe is not an outage.

Read-only multitenant Streamable HTTP bridge over Keeper Secrets Manager's MCP server.

timeout no valid answer since 2026-11-12 · probed 2026-11-14 · unchanged since 2026-11-12

probe timed out after 45000 ms
[ksm] keeper-mcp bridge listening on http://0.0.0.0:8080/mcp (read-only)
[ksm] received SIGTERM, shutting down

Run it: docker run -i --rm ghcr.io/wyre-technology/keeper-mcp:v1.0.0 (stdio, probed in a container with the network off)
Host: ghcr.io
Repository: https://github.com/wyre-technology/keeper-mcp
Website: https://github.com/wyre-technology/keeper-mcp
Registry: active, updated 2026-09-17 · registry entry
Changes: 3 recorded, reachable in 0 of them. A row is added when the result, the tool count or the cost changes.

More servers

Other registry entries on ghcr.io, the ones next to this name; all of them.

Servers that mention keeper.

SessionKeeper ai.sessionkeeper/mcp · needs auth
GeezerKeeper Referral Exit Routes and Deadlines com.geezerkeeper/referral-exit-routes · alive
Scrykeeper Royal Road Intelligence com.scrykeeper/royal-road-intelligence · alive
alink ink.al/alink · needs auth
Context Keeper (remote) io.github.jarmstrong158/context-keeper-remote · needs your URL
io.github.techops-services/keeperhub-mcp · needs auth
Tommy Accounting uk.co.tommyaccounting/tools · alive
Zeno ch.zeno-works/zeno · alive

We add a row when the result changes. A server with no change keeps its last row.

The result of the latest probe, the tool count and the token cost. The feed has an entry for every probe that changed them.

Stops answering, comes back, tool set or cost changes. One confirmation mail first, a stop link in every mail.

The package did not start as an MCP server at its probe on 2026-11-12. One failed probe is not an outage: the board calls a package down when it fails again at its next probe, a week later.
No answer within 15 seconds. The server is up but slow, or the request hangs. Some servers stall tools/list while a GET stream is open; the probe opens none.