Python MCP server for Ciphra. Lets AI coding agents call Ciphra's secret scanner via the Model Context Protocol.
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":"ciphra-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.
# ciphra-mcp Python MCP server exposing Ciphra's secret scanner to AI agents. ## What this is The agent-facing layer for [Ciphra](../README.md). The actual scanning is done by the TypeScript CLI at the repo root; this Python project spawns the CLI as a subprocess and translates between MCP's JSON-RPC protocol and Ciphra's JSON output. With this server registered, agents like Claude Code and Cursor can scan a codebase, validate a key, or audit git history without the user typing CLI commands. ## Prerequisites - **Node 20+** — needed for the underlying `ciphra` CLI, which this MCP server shells out to - **Python 3.11+** — for the MCP server itself - **[uv](https://github.com/astral-sh/uv)** (recommended) or `pip + venv` - **`ciphra` on `$PATH`.** The MCP server resolves the CLI via `shutil.which("ciphra")`, so it must be installed globally: ```bash npm install -g ciphra ``` If you get an `EACCES` error on `npm install -g`, your npm prefix is root-owned. The cleanest fix: ```bash mkdir -p ~/.npm-global npm config set prefix ~/.npm-global echo 'export PATH=~/.npm-global/bin:$PATH' >> ~/.zshrc source ~/.zshrc npm install -g ciphra ``` ## Installation ```bash uvx ciphra-mcp # ephemeral; runs the published wheel on demand ``` That's it — `uvx` downloads the wheel from PyPI on first invocation, then runs the entry point. No clone required. If you'd rather have it permanently installed in a project-local venv: ```bash uv pip install ciphra-mcp ``` ### Building from source (contributors) ```bash cd /path/to/ciphra npm install && npm run build # build the TS CLI cd mcp-server uv sync --extra dev # creates .venv, installs deps ``` (pip alternative: `python3.11 -m venv .venv && source .venv/bin/activate && pip install -e ".[dev]"`) ## Running the server **Standalone (sanity check that it launches):** ```bash uv run ciphra-mcp ``` The server speaks MCP over stdio and isn't useful interactively. Send…
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.