MCP server exposing Intercept supply chain security data to MCP-compatible clients.
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":"intercept-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.
# intercept-mcp Model Context Protocol (MCP) server that exposes an [Intercept](https://intercept.hijacksecurity.com) tenant's repositories, findings, scans, resolutions, and AI advisory output to MCP-compatible AI clients. ## Tools 22 tools (18 read, 4 write). Read tools cover repositories, findings (SAST, secrets, container, IaC, pipeline, SBOM/dependency), scans, organizations, and posture. Two per-repository AI tools surface Intercept's already-computed advisory output: - `get_ai_advisors` — latest AI Advisors panel: persona lens recommendations and the Lead Advisor action plan. - `get_ai_insights` — latest AI Insights code analysis: architecture, security review, tech stack, and threat model. Write tools update finding-resolution status, add notes, and trigger scans. ## Installation ```bash uvx intercept-mcp ``` `uv` ships native wheels for macOS, Linux, and Windows, so the same command works on every supported platform. ## Configuration Minimal env: `INTERCEPT_MCP_API_KEY` — generated from the Intercept web UI: **Settings → Integrations → Generate MCP API Key**. ### macOS / Linux Export the key from your shell profile (`~/.zshrc`, `~/.bashrc`): ```bash export INTERCEPT_MCP_API_KEY="hsk_..." ``` Claude Desktop config path: ``` ~/Library/Application Support/Claude/claude_desktop_config.json ``` ### Windows Set the key in PowerShell for the current session: ```powershell $env:INTERCEPT_MCP_API_KEY = "hsk_..." ``` Or persist it for new shells with `setx` (PowerShell or cmd): ```powershell setx INTERCEPT_MCP_API_KEY "hsk_..." ``` Note: `setx` writes to the user environment so future shells see the value, but it does **not** update the current shell. Open a new terminal after running it. For a GUI alternative, use **System Properties → Advanced → Environment Variables**. Claude Desktop config path: ``` %APPDATA%\Claude\claude_desktop_config.json ``` which resolves to `C:\Users\<you>\AppData\Roaming\Claude\claude_desktop_config.json`. If you…
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.