noevika-mcp
A Model Context Protocol server that gives AI assistants and agents direct access to Noevika — the deduplicated record of cyber incidents (breaches, ransomware claims, exploited CVEs, advisories) from government registries and security news. No browser needed: ask Claude, Cursor, or your own agent "has Acme Health filed a breach before?" and it queries Noevika.
Tools
| Tool | What it answers |
|---|---|
search_incidents(sector, type, keyword, limit, sort) |
What happened recently, filtered |
get_incident(incident_id) |
One incident with every source that covered it and CVE context |
organisation_timeline(name) |
Everything about one company — news → HHS → state AG → SEC |
threat_actor(name) |
A ransomware group's claims by sector and month |
directory(kind, limit) |
Most-reported organisations or actors |
cve_context(cve) |
KEV status, EPSS, due date, ransomware use, vendor advisory |
| `trends(period | start,end)` |
watchlist(), watch(kind, value) |
Your watchlist — needs an API key |
vendors() |
Your vendor portfolio — needs an API key |
Public tools work without a key. For account tools, create a key at https://noevika.com/preferences/ and set NOEVIKA_API_KEY.
Claude Desktop / Cursor / Claude Code
Add to the client's MCP configuration (claude_desktop_config.json, .cursor/mcp.json, …). Requires uv (pip install uv).
{
"mcpServers": {
"noevika": {
"command": "uvx",
"args": ["noevika-mcp"],
"env": { "NOEVIKA_API_KEY": "nvk_…" }
}
}
}
Or install once and run noevika-mcp as the command: pip install noevika-mcp.
Remote endpoint — nothing to install
Noevika also serves MCP directly at https://api.noevika.com/mcp (Streamable HTTP, stateless). Add it as a remote/custom connector in any client that supports URLs:
- Claude Code:
claude mcp add --transport http noevika https://api.noevika.com/mcp --header "X-Api-Key: nvk_…" - Claude.ai / Claude Desktop → Settings → Connectors → Add custom connector: URL
https://api.noevika.com/mcp(public tools work without a key; account tools need the header, where the client supports custom headers) - Cursor / other clients:
{"url": "https://api.noevika.com/mcp", "headers": {"X-Api-Key": "nvk_…"}}
Same ten tools; the remote endpoint reads the record directly, so it is the faster of the two. The stdio package remains for clients that only run local servers, and for self-hosted instances. You can also run this package as a local HTTP server: noevika-mcp --http --port 8787.
Attribution
Every result includes url (the original publisher) and page (the Noevika page). Keep the publisher link when you relay an item — it is what the sources are owed.
Environment
| Variable | Default | Purpose |
|---|---|---|
NOEVIKA_API_KEY |
— | Account tools; raises read page size to 500 |
NOEVIKA_API_URL |
https://api.noevika.com |
Point at a self-hosted instance |
Apache-2.0. Source and issues: https://github.com/pvovveti/noevika
Metadata
Release files for noevika-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 | Actions |
|---|---|---|---|---|
| noevika_mcp-0.1.0.tar.gz | 6.6 kB | With provenance | Details for noevika_mcp-0.1.0.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| noevika_mcp-0.1.0-py3-none-any.whl | Python 3 | none | any | Details for noevika_mcp-0.1.0-py3-none-any.whl |
Total release size: 13.2 kB
Release files / noevika_mcp-0.1.0.tar.gz
| Download URL | noevika_mcp-0.1.0.tar.gz |
|---|---|
| Size | 6.6 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
f142905f70fe42e5dd06ff2dfee8f5472d07b6ae441c1d64ea5d80c8447b5586
|
|
BLAKE2b-256 checksum How to use checksums |
ab1e1460472a04ac7b7ee367063ff87a408de65d4b346dcc9aee27131a2b5942
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.16
|
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 Nov 2, 2026.
Transparency logRelease files / noevika_mcp-0.1.0-py3-none-any.whl
| Download URL | noevika_mcp-0.1.0-py3-none-any.whl |
|---|---|
| Size | 6.5 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
c912786d69092ab344a318e0edc730224406a6a3a5a2d766ed3c0a9c75ad34ac
|
|
BLAKE2b-256 checksum How to use checksums |
2dbc10c3f3bb9de223e346185ffefc68a494051b2431cfc254acb2eb365a3c3f
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.16
|
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 Nov 2, 2026.
Transparency logSecurity for noevika-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.
Full provenance
All 2 files in this release have been uploaded with provenance metadata.
Attestation for noevika_mcp-0.1.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 Nov 2, 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.