mcp-server-remote
MCP server that serves a remote MCP client, ready-to-run tools and preset configuration files.
Intended for use within private network for Cybersecurity purposes.
System: {user} <--> mcp-client-console <--> network <--> {box} <--> mcp-server-remote <--> tools
Server: mcp-client-console <--> {mcp SDK} <--> * <--> auth.py <--> server.py <--> tools.py
User Guide | Installation
Users:
pipx install mcp-server-remote
mcp-server-remote
Developers:
git clone https://github.com/geomux/mcp-server-remote.git
cd mcp-server-remote
python3 -m venv .venv && source .venv/bin/activate
pip install -e .
mcp-server-remote
User Guide | Configuration
First run creates a default config.toml and prints its filepath (the /config command in the terminal chat prints it too). Edit it — populate with server name, url, token:
[server]
name = "Box_1" # Label for this machine
host = "127.0.0.1" # IP/Domain for this machine
port = 9000 # Choose port nginx proxies to
path = "/mcp" # Leave this alone. /mcp is default for dependencies.
| OS | Config filepath |
|---|---|
| Linux | ~/.config/mcp-server-remote/config.toml |
| macOS | ~/Library/Application Support/mcp-server-remote/config.toml |
| Windows | %LOCALAPPDATA%\mcp-server-remote\config.toml |
User Guide | Operation
Configure the MCP server first, then confirm the MCP client (see repos below) is configured to connect to it. The server accepts the connection, performs the MCP handshake, and lists the available tools to the client.
Model will have UNRESTRICTED shell access on remote host. Recommended to only run the MCP Server in a sandboxed environment.
Related / Required Repos
Project Status
- Create MCP server repo
- Connect to MCP client locally
- Connect to MCP client remotely (over the internet)
- Connect to MCP server remotely with TLS + bearer auth as requirement
- Add additional tools to tools.py
- Add CORS middleware integration so browser-based MCP clients can connect
Metadata
Release files for mcp-server-remote 0.4.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 | Actions |
|---|---|---|---|---|
| mcp_server_remote-0.4.0.tar.gz | 17.6 kB | With provenance | Details for mcp_server_remote-0.4.0.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| mcp_server_remote-0.4.0-py3-none-any.whl | Python 3 | none | any | Details for mcp_server_remote-0.4.0-py3-none-any.whl |
Total release size: 41.1 kB
Release files / mcp_server_remote-0.4.0.tar.gz
| Download URL | mcp_server_remote-0.4.0.tar.gz |
|---|---|
| Size | 17.6 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
f4d978120a177511c3e8e14b3243ba416782b16447b5c45c83920a1781a47ce5
|
|
BLAKE2b-256 checksum How to use checksums |
8c760880cf784f4a8c5886f0c32079a8deaaa470aef171cfad5f147dc40f00b0
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
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.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Sep 19, 2026.
Transparency logRelease files / mcp_server_remote-0.4.0-py3-none-any.whl
| Download URL | mcp_server_remote-0.4.0-py3-none-any.whl |
|---|---|
| Size | 23.5 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
78be71c80cd90f29cb16ff6b5d2eab28d723c9325a2ad7c61e25634188ba8c52
|
|
BLAKE2b-256 checksum How to use checksums |
308da4d14151d7ed41c0634f3a5f63ec0f582b68578ce6c9097440d37a07ffbe
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
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.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Sep 19, 2026.
Transparency logSecurity for mcp-server-remote 0.4.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.
Full provenance
Both files in this release have been uploaded with provenance metadata.
Attestation for mcp_server_remote-0.4.0.tar.gz
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Sep 19, 2026.
Transparency logA 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.