MCP client that connects to a remote MCP server
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-client-console","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-client-console MCP client that connects to a remote MCP server, LLM backend (API key or local model) and preset configuration files. *Intended for use within private network for Cybersecurity purposes.* ``` System: {user} <--> mcp-client-console <--> network <--> {box} <--> mcp-server-remote <--> tools Client: {user} <--> cli.py <--> client.py <--> mcp SDK <--> * <--> mcp-server-remote ``` ## User Guide | LLM Backend Setup *Skip this section if using an API LLM connection.* For a local model, set up Ollama before installing the client: ```bash curl -fsSL https://ollama.com/install.sh | sh # Linux. macOS: brew install ollama. Windows: winget install Ollama.Ollama ollama pull qwen2.5:14b # default model in config_default.toml ollama list # confirm Ollama is running and the model is pulled ``` To use a different model, pull it the same way and update `model` under `[llm.local]` in your `config.toml` to match the tag exactly. `host` under `[llm.local]` must include the full scheme: `http://127.0.0.1:11434`... not `127.0.0.1:11434`. ## User Guide | Installation Users: ```bash pipx install mcp-client-console mcp-client-console ``` Developers: ```bash git clone https://github.com/geomux/mcp-client-console.git cd mcp-client-console python3 -m venv .venv && source .venv/bin/activate pip install -e . mcp-client-console ``` ## 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" url = "http://127.0.0.1:9000/mcp" ``` | OS | Config filepath | | ------- | -------------------------------------------------------------- | | Linux | `~/.config/mcp-client-console/config.toml` | | macOS | `~/Library/Application Support/mcp-client-console/config.to…
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.