Security-first MCP server for managing Docker services on a remote server or on the local host.
Wellknown found it in public sources; nobody has proven control of it yet. Claiming takes one click if the repository is under your GitHub account, or a small file on your domain otherwise. Verified owners get the badge, 15-minute checks, status alerts, edits that outrank crawled data, and a ranking boost.
Agents can do it too: POST https://wellknown.network/api/v1/claims with {"agent":"remote-server-mcp","method":"well_known_file"} — machine-readable steps at claim.json, guide at /docs/claim.
Everything here was measured by our prober or read from a registry. Nothing is self-reported.
Attributed to the source that supplied each field. Treated as claims, not facts.
# remote-server-mcp Security-first MCP server for Docker service management over SSH or on the local host. Part of the [Server MCP suite](../../README.md). It exposes a fixed catalog of 23 tools (directory and container discovery, container and host-service logs, status and health, start/stop/restart, scoped Compose operations, confined file reads, server health, read-only InfluxDB/Prometheus queries and InfluxDB schema discovery). No generic command execution. The container CLI is configurable (`docker`, `podman` or `nerdctl`). `start_service`, `restart_service`, `stop_service`, `compose_pull`, `compose_up` and `compose_down` require `confirm=true` and are bounded by a per-process rate limit; `start_service` reports an already-running container without calling `docker start`. Streamable HTTP is available with `--transport streamable-http`: it binds to loopback by default and requires a bearer token for any other address. Host infrastructure services such as `telegraf`, `smartmontools` and `docker` are systemd units, not containers. `get_host_service_status`, `get_host_service_logs` and `search_host_service_logs` read them with `systemctl`/`journalctl` and only accept units listed in `security.host_units`. Journal reads accept a `since` window and search matches the exact literal pattern locally. Container logs always include timestamps. A log request can add a `since`/`until` window and target one container in a compose project; search matches the exact literal pattern. Every tool publishes a structured `ToolResponse` next to the readable text. Composite and listing responses receive a final `output.max_bytes` cap. When the audit log is enabled, InfluxDB and Prometheus queries are recorded by length/SHA-256 fingerprint rather than by query text. Prometheus is optional. Its metric endpoints can be reached through an HTTPS reverse proxy or a loopback-only `ssh_tunnel` created by the MCP; see [configuration](../../docs/configuration.md#database-endpoints). - […
Mapped onto the structured taxonomy from declared text and observed tool names. Confidence shown for derived entries.
Every source is kept verbatim. Field changes are logged as events.