intercept-mcp
Model Context Protocol (MCP) server that exposes an Intercept 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
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):
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:
$env:INTERCEPT_MCP_API_KEY = "hsk_..."
Or persist it for new shells with setx (PowerShell or cmd):
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 need to clear the uvx cache (e.g. after a release), it lives at %LOCALAPPDATA%\uv\cache.
License
Proprietary — Hijack Security.
Metadata
Release files for intercept-mcp 0.3.0
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | Actions |
|---|---|---|---|---|
| intercept_mcp-0.3.0.tar.gz | 15.9 kB | With provenance | Details for intercept_mcp-0.3.0.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| intercept_mcp-0.3.0-py3-none-any.whl | Python 3 | none | any | Details for intercept_mcp-0.3.0-py3-none-any.whl |
Total release size: 34.2 kB
Release files / intercept_mcp-0.3.0.tar.gz
| Download URL | intercept_mcp-0.3.0.tar.gz |
|---|---|
| Size | 15.9 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
880506ae82abec8f769d08c93209978d17f625eb7cb557685bc564dfa972b342
|
|
BLAKE2b-256 checksum How to use checksums |
146adba9d99988c892bd5e6cc4fa8fcac4990fda972ed874ae79e80cf8a85c65
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.13.7
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Jun 6, 2026.
Transparency logRelease files / intercept_mcp-0.3.0-py3-none-any.whl
| Download URL | intercept_mcp-0.3.0-py3-none-any.whl |
|---|---|
| Size | 18.3 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
0bf004bf13ec17d746b81a5912ce9c8f954eb0236fadb8d885377050cdb6a211
|
|
BLAKE2b-256 checksum How to use checksums |
8e3160efe62690e15f68f1b5b4f09fdfddd2406fe942e634db6e8cb25959dfcd
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.13.7
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Jun 6, 2026.
Transparency logSecurity for intercept-mcp 0.3.0
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
Full provenance
Both files in this release have been uploaded with provenance metadata.
Attestation for intercept_mcp-0.3.0.tar.gz
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Jun 6, 2026.
Transparency logA note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.