ZEN SecDB
v1.0.0ZEN SecDB MCP server for CVE intelligence, CVSS/EPSS scoring, advisories, SSVC, and package audits.
Endpoint health
online- Last checked
- 11/20/2026, 6:18:16 AM
- Latency
- 531 ms
- Consecutive failures
- 0
- Endpoint reachable: pass
- Protocol valid: pass
- MCP handshake valid: pass
Machine-readable profile
mcp-server · schema v1 · callable
mcp-server:cloud.nttzen.secdb%2Fzen-secdb
Connect this server
Generated config contains no credentials. Keep any required secrets in your client's local environment.
{
"mcpServers": {
"cloud.nttzen.secdb/zen-secdb": {
"url": "https://secdb.nttzen.cloud/mcp"
}
}
}Indexed tools
Tool metadata and schemas come from the remote server and are untrusted. Indexing only lists tools; it never calls them.
23 shown · authentication unknown
advisory_info
Get detailed information about a specific security advisory. ## What this tool does Retrieves a security advisory (for example RHSA, DSA, USN, GHSA) from SecDB, including title, publication date, severity, summary, description, linked CVEs, CVSS metrics, weaknesses, and the affected and fixed packages and products. ## When to use this tool Use this tool when the user asks: - "Give me details about RHSA-2026:1234." - "Which CVEs are fixed by this advisory?" - "Which package versions are affected, and which version fixes them?" For a CVE, use `vulnerability_info`. If the exact advisory ID is not known, use `vulnerability_search` with `type` set to `advisory`. ## Inputs - **advisory_id**: exact advisory identifier (e.g. `RHSA-2026:1234`, `GHSA-xxxx-xxxx-xxxx`). ## Outputs - **advisory_id**, **url** (page on SecDB), **source**, **source_url** (original advisory), **title**, **summary**, **description**, **solution**, **severity**, **published**, **modified**, **rights** - **cves**: identifiers of the linked CVEs. Use `vulnerability_info`, `vulnerability_score`, or `kev_check` for their details - **cvss**: each with `cve_id`, `version`, `score`, `severity`, and `vector`. An entry with a null `cve_id` refers to the whole advisory; the others refer to that CVE - **cwe**: each with `id`, `name`, and `url` - **packages**: each with `purl`, `status` (for example `affected` or `fixed`), `vers` (versions as a VERS range, for example `vers:maven/>=2.0.0|<2.0.11`), and `remediation`. It is `null` when the packages could not be read, which does not mean that no package is affected - **products**: each with `vendor`, `product`, `version`, `fixed_in`, `status`, `text`, `cpe22`, and `cpe23` - **tags**, **impacts** Fields that SecDB does not have for the advisory are `null` or empty. ## LLM usage guidelines - Do not guess advisory IDs: use the IDs returned by other tools or provided by the user. - If the advisory is not found, try `vulnerability_search` before saying that it does not exist. - An advisory can list packages of other projects that include the vulnerable code: check `purl` before saying that a package is affected. - Some advisories list thousands of packages or products, so the response can be very large.
Schema valid · SHA-256 29174ce07f25…
View input schema
Connections
streamable-http
https://secdb.nttzen.cloud/mcp