ZEN SecDB MCP server for CVE intelligence, CVSS/EPSS scoring, advisories, SSVC, and package audits.
Securityv1.0.0streamable-httpsecdb.nttzen.cloud
| Criterion | Points | Observed |
|---|---|---|
| reachability | 25 / 25 | HTTP 200, initialize accepted in 1189ms |
| protocol | 15 / 15 | valid JSON-RPC initialize result, protocolVersion 2025-11-25, serverInfo NTT DATA ZEN SecDB Portal - MCP Server@26.4.90 |
| tooling | 35 / 35 | tools/list OK: 11 tools e.g. "epss_timeseries"; 11/11 described, 11/11 fully-typed schemas, median description 1483 chars |
| latency | 7 / 10 | initialize round-trip 1189ms |
| provenance | 12 / 15 | description present; no repository URL; version 1.0.0; namespace cloud.nttzen.secdb matches endpoint/repo |
Score 94/100 · latency 1189ms · 11 tools · auth: open
Claude Code:
claude mcp add --transport http zen-secdb https://secdb.nttzen.cloud/mcp
Generic MCP client config:
{ "mcpServers": { "zen-secdb": { "type": "http", "url": "https://secdb.nttzen.cloud/mcp" } } }
MCP Queen is a graded index, not a middleman — your agent connects directly to the server above. Check the grade and evidence first; that's the point.
Share this server: permalink https://mcpqueen.com/s/cloud.nttzen.secdb/zen-secdb · referral link https://mcpqueen.com/go/cloud.nttzen.secdb/zen-secdb (counts as “routed via the queen”).
Live badge, re-probed continuously — put it in your README:
[](https://mcpqueen.com/s/cloud.nttzen.secdb/zen-secdb)
Think the grade is wrong? Fix the finding the evidence shows, then the next probe cycle picks it up automatically (full cycle ≈ 3 days) — or open a dispute via the MCP endpoint.
Email alerts when the grade changes or the endpoint stops answering. Double-opt-in, one-click unwatch, free while in beta.
| When (UTC) | Grade | Score | Latency |
|---|---|---|---|
| 2026-07-12 21:15 | A | 94 | 1189ms |