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":"llm-tools-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.
<div align="center"> # `llm-tools-mcp`  **Connect to MCP servers right from your shell. Plugin for [llm](https://github.com/simonw/llm) (by [@simonw](https://github.com/simonw)).** [](https://pypi.org/project/llm-tools-mcp/) [](https://github.com/VirtusLab/llm-tools-mcp/releases) [](https://github.com/VirtusLab/llm-tools-mcp/actions/workflows/test.yml) [](https://github.com/VirtusLab/llm-tools-mcp/blob/main/LICENSE)  </div> > [!Note] > Current focus: [Authorization #4](https://github.com/VirtusLab/llm-tools-mcp/issues/4) ## Installation Install this plugin in the same environment as [LLM](https://llm.datasette.io/): ```bash llm install llm-tools-mcp ``` ## Usage > [!WARNING] > It's recommended to use the `--ta` flag and approve each tool execution. 1. Create `mcp.json` file in `~/.llm-tools-mcp`. Example file: ```json { "mcpServers": { "filesystem": { "command": "npx", "args": [ "-y", "@modelcontextprotocol/server-filesystem", "~/demo" ] } } } ``` 2. List available tools. > [!WARNING] > `llm tools` is not implemented for dynamic toolboxes ([see this](https://github.com/simonw/llm/issues/1111#issuecomment-2992280193)), > so tools loaded as part of MCP won't be visible. ```sh llm tools list ``` 3. Run `llm` with tools. ```sh llm --ta -T MCP "what files are in the demo directory? show me contents of one of the files (…
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.