# Security Intel MCP (remote · security.datakoot.com)

CVE lookups (NVD) and dependency-manifest audits (OSV) for AI agents. No API keys.

- Trust score: 71/100 (medium)
- Change this week: +3
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-09-27

## Components

- remote · `security.datakoot.com`: 71/100 (this document), [markdown](https://verifymcp.io/servers/com-datakoot-cve-vulnerability-lookup/security.md), [page](https://verifymcp.io/servers/com-datakoot-cve-vulnerability-lookup/security)

## Channel facts

- Endpoint: `https://security.datakoot.com/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `2.1.0`

## Trust breakdown

How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-09-27.

- **Endpoint Security**: 51/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - Authorisation not fully verified: no authorisation is required to call this server, and 5 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe.
  - HTTPS enforcement could not be verified: the plaintext port answered with HTTP 405, which proves neither a plaintext path nor enforcement.
  - The HSTS (Strict-Transport-Security) header is present.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 72/100
  - AI-judged instruction clarity (excellent).
  - Context-footprint check failed: tool/resource definitions use about 729 tokens (~145/item across 5 items; 5 tools + 0 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 83/100
  - Stability observed for 25 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% of tool parameters carry a description.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 5 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 6 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 60/100
  - Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28.

## Install

### How do I install the Security Intel MCP server?

Security Intel MCP is a hosted endpoint at https://security.datakoot.com/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

### Claude

```bash
claude mcp add --transport http com-datakoot-cve-vulnerability-lookup 'https://security.datakoot.com/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "com-datakoot-cve-vulnerability-lookup": {
      "url": "https://security.datakoot.com/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "com-datakoot-cve-vulnerability-lookup": {
      "type": "http",
      "url": "https://security.datakoot.com/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.com-datakoot-cve-vulnerability-lookup]
url = "https://security.datakoot.com/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "com-datakoot-cve-vulnerability-lookup": {
      "type": "remote",
      "url": "https://security.datakoot.com/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add com-datakoot-cve-vulnerability-lookup --url 'https://security.datakoot.com/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  com-datakoot-cve-vulnerability-lookup:
    url: "https://security.datakoot.com/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "com-datakoot-cve-vulnerability-lookup": {
      "Transport": "http",
      "Url": "https://security.datakoot.com/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add com-datakoot-cve-vulnerability-lookup -t streamable-http -u 'https://security.datakoot.com/mcp'
```

### Other

```json
{
  "mcpServers": {
    "com-datakoot-cve-vulnerability-lookup": {
      "type": "http",
      "url": "https://security.datakoot.com/mcp"
    }
  }
}
```

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-09-25 (score 71, +1)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-09-23 (score 70, +1)

No change was recorded against any check on this day. Stability & Change Management went from 67 to 70. That category is still filling its 30-day observation window: 20 days of observed history at the previous scan, 21 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-09-21 (score 69, +1)

No change was recorded against any check on this day. Stability & Change Management went from 60 to 63. That category is still filling its 30-day observation window: 18 days of observed history at the previous scan, 19 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-09-19 (score 68, +1)

No change was recorded against any check on this day. Stability & Change Management went from 53 to 57. That category is still filling its 30-day observation window: 16 days of observed history at the previous scan, 17 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-09-17 (score 67, +1)

No change was recorded against any check on this day. Stability & Change Management went from 47 to 50. That category is still filling its 30-day observation window: 14 days of observed history at the previous scan, 15 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-09-16 (score 66, 0)

- [security] The server rewrote its instructions, which are the text every model session reads
- [security] Tool “cve_lookup” rewrote its description, which is the text the model reads
- [functional regression] Schema quality: pass → fail
- [functional] Schema quality: good → excellent
- [functional] Server version: 2.0.0 → 2.1.0
- [functional] New tool “epss_score”
- [functional] New tool “known_exploited”

### 2026-09-15 (score 66, +1)

No change was recorded against any check on this day. Stability & Change Management went from 40 to 43. That category is still filling its 30-day observation window: 12 days of observed history at the previous scan, 13 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-09-13 (score 65, +1)

No change was recorded against any check on this day. Stability & Change Management went from 33 to 37. That category is still filling its 30-day observation window: 10 days of observed history at the previous scan, 11 at this one. The score rises as the window fills, whether or not the server changes.

## MCP tools (5)

### `cve_lookup` (~107 tokens)

Look up a CVE by ID and get a compact summary: description, CVSS score & severity, vector, CWE weakness, publish date, references — plus whether it is on the CISA Known-Exploited list (actively exploited in the wild) and its EPSS exploit-probability. Sources: NVD (NIST), CISA KEV, FIRST EPSS.

Input parameters:

- `cve_id` (string, required): e.g. CVE-2021-44228

### `known_exploited` (~171 tokens)

Check whether a CVE is on the CISA Known Exploited Vulnerabilities (KEV) catalog — confirmed exploited in the wild — or list the most recently added exploited vulnerabilities. Pass cve_id to check one; omit it to list recent (optionally filter by vendor/product, or ransomware_only). Source: CISA KEV, updated ~daily.

Input parameters:

- `cve_id` (string): Optional. Check a single CVE, e.g. CVE-2021-44228.
- `limit` (number): When listing, how many newest entries to return (default 20, max 100).
- `ransomware_only` (boolean): Optional. Only vulns CISA links to known ransomware campaigns.
- `vendor` (string): Optional. Filter by vendor or product name substring.

### `epss_score` (~112 tokens)

Get the EPSS exploit-probability score (0-1) and percentile for one or more CVEs — the likelihood each is exploited in the next 30 days. Use it to prioritize patching. Pass cve_id for one, or cve_ids (array or comma-separated) for many. Source: FIRST.org EPSS.

Input parameters:

- `cve_id` (string): A single CVE id.
- `cve_ids` (array): Multiple CVE ids (or pass a comma-separated string).

### `package_vulnerabilities` (~146 tokens)

List known vulnerabilities for a software package (optionally a specific version) via OSV. Ecosystems: npm, pypi, cargo, go, maven, rubygems, nuget, composer, pub, hex.

Input parameters:

- `ecosystem` (string, required): Package registry to look in. One of: npm, pypi, cargo, go, maven, rubygems, nuget, composer, pub, hex.
- `name` (string, required): Exact package name as published in that registry, e.g. lodash for npm, requests for pypi.
- `version` (string): Optional; if given, only vulns affecting that version are returned

### `audit_dependencies` (~91 tokens)

Audit a whole dependency manifest for known vulnerabilities in one call. Paste a package.json (as 'manifest'), or pass a 'dependencies' array of {name, version} objects. Returns per-package findings and a summary. Ecosystem defaults to npm.

Input parameters:

- `dependencies` (array): [{name, version}] entries
- `ecosystem` (string): Default npm
- `manifest` (string): Raw package.json contents

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/com-datakoot-cve-vulnerability-lookup/security#diagnostics

## Score history

- 2026-09-27: 71
- 2026-09-26: 71
- 2026-09-25: 71
- 2026-09-24: 70
- 2026-09-23: 70
- 2026-09-22: 69
- 2026-09-21: 69
- 2026-09-20: 68
- 2026-09-19: 68
- 2026-09-18: 67
- 2026-09-17: 67
- 2026-09-16: 66
- 2026-09-15: 66
- 2026-09-14: 65
- 2026-09-13: 65
- 2026-09-12: 64
- 2026-09-11: 64
- 2026-09-10: 63
- 2026-09-09: 63
- 2026-09-08: 62
- 2026-09-07: 62
- 2026-09-06: 61
- 2026-09-05: 61
- 2026-09-04: 61
- 2026-09-03: 60
- 2026-09-02: 56

## Common questions

### What is the Security Intel MCP server?

Security Intel MCP is listed in the public MCP registry as com.datakoot/cve-vulnerability-lookup. CVE lookups (NVD) and dependency-manifest audits (OSV) for AI agents. No API keys. This page covers its hosted endpoint (https://security.datakoot.com/mcp).

### Is the Security Intel MCP server safe to use?

Security Intel MCP scores 71 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

### What tools does the Security Intel MCP server expose?

Security Intel MCP exposes 5 tools: cve_lookup, known_exploited, epss_score, package_vulnerabilities, audit_dependencies. Their descriptions and schemas cost roughly 627 tokens of context every time the server is loaded.

### Does the Security Intel MCP server require authentication?

No. We connected to Security Intel MCP without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

### Is the Security Intel MCP server still maintained?

Security Intel MCP is still listed as active in the MCP registry. We last reached this channel on 27 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

## Links

- Remote endpoint: https://security.datakoot.com/mcp
- Repository: https://github.com/datakoot/security-intel-mcp
- Changelog RSS feed: https://verifymcp.io/servers/com-datakoot-cve-vulnerability-lookup/security.xml
- Changelog JSON feed: https://verifymcp.io/servers/com-datakoot-cve-vulnerability-lookup/security.json
- HTML version of this page: https://verifymcp.io/servers/com-datakoot-cve-vulnerability-lookup/security