com.bluecat/livewiremcp
com.bluecat/livewiremcp
LiveAction LiveWire MCP Server
not probed in the official registry, not probed
- Run it
- docker run -i --rm quay.io/bluecat/livewiremcp@sha256:c1614cbe6bca212d0287c5fdfafc09b83579b38eb7e5f9b1fc4011902d41d385 (stdio, probed in a container with the network off)
- Host
- quay.io
- Registry
- active, updated 2026-09-24 · registry entry
Compare this server with others.
More servers
Other registry entries on quay.io.
- com.bluecat/integritymcp · not probed
- com.bluecat/livenxmcp · not probed
- com.bluecat/micetromcp · not probed
Servers that mention liveaction or livewire.
- Aura UI io.github.BlueStarSystem/aura-ui · alive
- io.github.jmshinhwa/livewire-client-surface-audit · alive
- io.github.jmshinhwa/livewire3-upgrade-blocker-lint · alive
- io.github.leMaur/livewire-flux-mcp · alive
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
- The entry has only an OCI image that serves streamable-http. The probe starts packages that talk over stdio only. The entry is on the board so that the list holds the whole registry and says what it does not check.