MCP server for Steampunk Spotter: Lets AI agents verify Ansible and Terraform code against your policies.
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":"steampunk-spotter-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.
# Steampunk Spotter MCP Server [](https://pypi.org/project/steampunk-spotter-mcp/) The Steampunk Spotter MCP server connects [Steampunk Spotter] scanning abilities with AI agents, so they can check the code as they write. It uses the [Steampunk Spotter CLI][steampunk-spotter], which is installed together with it. ## Installation Requirements: - [uv] for the recommended install, or - Python >= 3.10 for other install options (see below). Add the following entry to your MCP configuration (see [Agent setup](#agent-setup) for agent-specific instructions): ```json { "mcpServers": { "spotter": { "command": "uvx", "args": ["--python", ">=3.10", "steampunk-spotter-mcp@latest"] } } } ``` ### Alternative install To avoid uv dependency, use any python package manager to install the server into your Python environment: ```shell $ pip install steampunk-spotter-mcp ``` This provides the `spotter-mcp` console script. Use it as the command, with the absolute path to it: ```json { "mcpServers": { "spotter": { "command": "/path/to/.venv/bin/spotter-mcp" } } } ``` ## Authentication ### Recommended: login with Spotter CLI Log in once and the MCP server uses the stored credentials (see [CLI authentication] for all login options). ```shell $ spotter login ``` Without the CLI installed, log in through `uvx`: ```shell $ uvx --from steampunk-spotter spotter login ``` For on-prem, **first** set the endpoint in `~/.config/steampunk-spotter/spotter.json` (add the key if the file already exists), then log in: ```json {"endpoint": "<spotter-api-url>"} ``` For details, see [Setting the API endpoint] in the CLI documentation. ### Alternative: set env variables The MCP server authenticates with these environment variables, which take precedence over the stored login: | Variable | Description …
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.