MCP server that serves a remote MCP client.
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":"mcp-server-remote","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.
# 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: ```bash pipx install mcp-server-remote mcp-server-remote ``` Developers: ```bash 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: ```toml [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 - [mcp-client-console](https://github.com/geomux/mcp-client-console) - [mcp-sandbox-set…
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.