Developer · Remote MCP server
ZEN SecDB
ZEN SecDB MCP server for CVE intelligence, CVSS/EPSS scoring, advisories, SSVC, and package audits.
What the MCP Registry states
The entry as published to the official MCP Registry (read 2026-10-04), latest version.
- Registry name
cloud.nttzen.secdb/zen-secdb- Version
- 1.0.0
- Status
- Active
- Category
- developer
- Transport
- Streamable HTTP
- Published
- 2026-07-02
- Updated
- 2026-07-02
- Publisher
- cloud.nttzen.secdb
- Namespace
- Namespace verified by the MCP Registry via the domain secdb.nttzen.cloud or a parent domain of it · how
- Website
- secdb.nttzen.cloud/docs/integrations/mcp
- Source
- Registry API entry
Remote endpoints
| Transport | URL | Headers declared |
|---|---|---|
| Streamable HTTP | https://secdb.nttzen.cloud/mcp | None |
Live check
This directory connected to each remote endpoint and asked for its list of tools. The check connects and lists tools only; it doesn't run tools, sign in or test security.
- Reachable
- Yes (HTTP 200)
- Handshake
- NTT DATA ZEN SecDB Portal - MCP Server 26.8.2 · protocol 2025-11-25
- Tools discovered
- 11:
epss_timeseries,linux_audit,linux_os,sightings_search,ssvc_calculator,vulnerability_info,vulnerability_score,vulnerability_search,feed_report_catalog,feed_report,purl_audit - Checked on
- 2026-10-05
How to connect ZEN SecDB
ZEN SecDB is a remote MCP server: there is nothing to install. Its endpoint is https://secdb.nttzen.cloud/mcp, served over Streamable HTTP. In an assistant that accepts remote MCP servers (often under a setting named connectors, integrations or tools), add a new server and give it this URL; in a client configured by file, add it as a remote (HTTP) server with the same URL.
No headers are declared in the registry entry. If the server needs you to sign in, a client that supports MCP authorization opens the service's own sign-in page when it first connects.
Derived from the registry entry; the live check above only shows whether the endpoint answered. What the server does, and on what terms, is set by its publisher; check its repository or website before giving it access to your accounts or files. How to add an MCP server to an assistant · Before you connect
More developer servers
| Server | Runs |
|---|---|
| Zabbix AI CLI MCPTask-shaped Zabbix access for AI agents: problems, host triage, metrics, maintenance windows. | Local · stdio |
| Zapier Dev MCPFor Zapier integration developers: inspect, lint, and validate zapier-platform-cli projects. | Local · stdio |
| Zarla Website BuilderBuild, edit and publish websites from Claude, ChatGPT, Cursor and Gemini. No code - Zarla hosts it. | Remote · HTTPLive check: sign-in required |
| ZaxyEvent-sourced, auditable agent memory over MCP: cited checkout, replayable provenance. | Local · stdio |
| ZenBrain MemorySeven-layer agent memory: episodic, semantic, procedural and core. Local SQLite, no account. | Local · stdio |
| Zendriver MCPUndetectable browser automation for LLM agents, spoken over MCP. | Local · stdio |
| ZenLink MCPBrowser automation for MCP clients via Zen Browser. Parallel multi-tab, content extraction. | Local · stdio |
| Zenrows MCPZenrows MCP server - Fetch, Extract, Batch, and Browser Sessions for AI coding assistants. | Remote & Local · HTTP, stdioLive check: sign-in required |