remote-server-mcp
Security-first MCP server for Docker service management over SSH or on the local host.
Part of the Server MCP suite. It exposes a fixed catalog of 21 tools (directory and container discovery, container and host-service logs, status and health, start/stop/restart, scoped Compose operations, confined file reads, server health and read-only InfluxDB/Prometheus queries). No generic command execution.
The container CLI is configurable (docker, podman or nerdctl). restart_service,
stop_service, compose_pull, compose_up and compose_down require confirm=true and
are bounded by a per-process rate limit. 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, smartd and docker are systemd units,
not containers. get_host_service_status and get_host_service_logs read them with
systemctl/journalctl and only accept units listed in security.host_units.
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.
uv run --directory apps/remote-server-mcp remote-server-mcp
Requires a config file; see config.example.yaml in this directory.
1 maintainer
Metadata
1 maintainer
Release files for remote-server-mcp 0.2.0
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | |
|---|---|---|---|---|
| remote_server_mcp-0.2.0.tar.gz | 48.8 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| remote_server_mcp-0.2.0-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 69.9 kB
Release files / remote_server_mcp-0.2.0.tar.gz
| Download URL | remote_server_mcp-0.2.0.tar.gz |
|---|---|
| Size | 48.8 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
557ca768f569de49a97786ef619e6b2c2a26a8aea89243a9574f46366eeefe3d
|
|
BLAKE2b-256 checksum How to use checksums |
b934b8bd8bb8d77593e920c222406a1e36fcbdf7eaa1952861f4fce2d855df1e
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
uv/0.13.3 {"installer":{"name":"uv","version":"0.13.3","subcommand":["publish"]},"python":null,"implementation":{"name":null,"version":null},"distro":{"name":"Arch Linux","version":null,"id":null,"libc":null},"system":{"name":null,"release":null},"cpu":null,"openssl_version":null,"setuptools_version":null,"rustc_version":null,"ci":null}
|
Release files / remote_server_mcp-0.2.0-py3-none-any.whl
| Download URL | remote_server_mcp-0.2.0-py3-none-any.whl |
|---|---|
| Size | 21.1 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
bbd9ebb52f628ab233c1c1cad518f401b114e5fbf7e1c17c40095c71d0e6f9f8
|
|
BLAKE2b-256 checksum How to use checksums |
3c0e0f7662fb97698ea38b0813e156aa2ee1f3138615759a2a8a6eef2c6cd8d6
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
uv/0.13.3 {"installer":{"name":"uv","version":"0.13.3","subcommand":["publish"]},"python":null,"implementation":{"name":null,"version":null},"distro":{"name":"Arch Linux","version":null,"id":null,"libc":null},"system":{"name":null,"release":null},"cpu":null,"openssl_version":null,"setuptools_version":null,"rustc_version":null,"ci":null}
|
Security for remote-server-mcp 0.2.0
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.
