com.bluecat/micetromcp
com.bluecat/micetromcp
BlueCat Micetro MCP Server
not probed in the official registry, not probed
- Run it
- docker run -i --rm quay.io/bluecat/micetromcp@sha256:04d929d2f292ca8514ba26a0cfe9178068b591ae7b5f70b93fb4807e7bed70ba (stdio, probed in a container with the network off)
- Host
- quay.io
- Registry
- active, updated 2026-11-02 · 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/livewiremcp · not probed
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.