patrowl-intel-mcp
An MCP server that exposes PatrowlIntel vulnerability intelligence (CVEs, EPSS, CISA KEV, public exploits, trending attacks) to any MCP client. It is a thin, read-only stdio wrapper over the public PatrowlIntel API.
v0 — three tools:
search_cves,get_cve,list_trending_attacks.
Tools
| Tool | Purpose |
|---|---|
search_cves |
Filter/rank the CVE feed (risk score, EPSS, KEV, exploited, technology, dates). |
get_cve |
Full record for one CVE (CVSS, EPSS, KEV, SSVC, exploits, references). |
list_trending_attacks |
Recent trending threats, filterable by severity and date. |
Configuration (environment)
| Variable | Default | Purpose |
|---|---|---|
PATROWL_INTEL_API_BASE |
https://intel.patrowl.io |
Backend API base URL. |
PATROWL_INTEL_WEB_BASE |
= API base | Public site base used for CVE citation links. |
PATROWL_INTEL_API_KEY |
(unset) | Reserved for the future authenticated tier. |
PATROWL_INTEL_TIMEOUT |
15 |
Per-request timeout (seconds). |
PATROWL_INTEL_MCP_TRANSPORT |
stdio |
stdio (local clients) or streamable-http (networked service). |
PATROWL_INTEL_MCP_HOST |
127.0.0.1 |
Bind host for streamable-http. |
PATROWL_INTEL_MCP_PORT |
8790 |
Bind port for streamable-http. |
Run
# stdio (default) — for local MCP clients that launch the process
uv run patrowl-intel-mcp # or: pip install -e . && patrowl-intel-mcp
# streamable-http — as a networked service (e.g. Docker); serves at /mcp
PATROWL_INTEL_MCP_TRANSPORT=streamable-http PATROWL_INTEL_MCP_HOST=0.0.0.0 \
uv run patrowl-intel-mcp
Client config
{
"mcpServers": {
"patrowl-intel": {
"command": "uvx",
"args": ["patrowl-intel-mcp"],
"env": { "PATROWL_INTEL_API_BASE": "https://<your-intel-host>" }
}
}
}
During local development, point command at your checkout instead:
{ "command": "uv", "args": ["--directory", "/path/to/PatrowlIntelMCP", "run", "patrowl-intel-mcp"] }
1 maintainer
Metadata
1 maintainer
Release files for patrowl-intel-mcp 0.1.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 | |
|---|---|---|---|---|
| patrowl_intel_mcp-0.1.0.tar.gz | 61.5 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| patrowl_intel_mcp-0.1.0-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 69.2 kB
Release files / patrowl_intel_mcp-0.1.0.tar.gz
| Download URL | patrowl_intel_mcp-0.1.0.tar.gz |
|---|---|
| Size | 61.5 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
1b65104a93e8ef9a621d7edbcdb4848be4586ccbe0380ae8bcbbf6e3e9f33ff2
|
|
BLAKE2b-256 checksum How to use checksums |
43197107ea61ae6acb19767ca664bf52b88ee1390b127cfa6641df10ddded604
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
uv/0.8.17
|
Release files / patrowl_intel_mcp-0.1.0-py3-none-any.whl
| Download URL | patrowl_intel_mcp-0.1.0-py3-none-any.whl |
|---|---|
| Size | 7.7 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
14d6557b76b57f9852388b167721502f6ebfb3092e8be9cb4c9e0204f1f1523f
|
|
BLAKE2b-256 checksum How to use checksums |
74b289b433e65ba16b02a31dd98e7e962494926bb9f97cca594cbb9127129bb8
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
uv/0.8.17
|
Security for patrowl-intel-mcp 0.1.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.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A 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.
