Local MCP capabilities provider for Expo
ZEN SecDB is installed from its publisher's own source and answers where it runs, so this marketplace is not in the path of a single call. There is no address here to send one to, and a panel that pretended otherwise would be showing you an answer we made up. Install it and call it from your own client — the Installation tab has the entry for each one.
What it does
ZEN SecDB MCP server for CVE intelligence, CVSS/EPSS scoring, advisories, SSVC, and package audits.
Quickstart
# 1 — add it to Claude Code
claude mcp add --scope user --transport http zen-secdb-mcp https://secdb.nttzen.cloud/mcp
# 2 — ask your agent for something these tools do
# epss_timeseries, linux_audit, linux_os and 8 more
ZEN SecDB costs nothing on mcprush: there is no plan to choose here, no cap to set and nothing mcprush can bill you for.
Collected from a public index. Nobody has claimed this account, so nothing here was written by its author — claim it if it is yours.
Where are you running it?
Every route below installs the same thing and ends at the same approval screen. Nothing here runs on your machine and nothing runs on ours: this server answers at its publisher’s own address, and what you install is the connection straight to it.
This is a public server: it answers at its publisher’s own address and this marketplace is not in the path. Claude Code registers it in one command; --scope user makes it available in every project. The transport below is http, as the publisher's own manifest declares it.
claude mcp add --scope user --transport http zen-secdb-mcp https://secdb.nttzen.cloud/mcpReconnect, or start a new session, and the tools appear in the model’s tool list.
One config entry pointing straight at the publisher’s own address — this marketplace is not in the path, and nothing from this listing executes on your machine.
11 tools, with what each one reads, writes and reaches shown before you agree — the same list on every route above. Read the tool surface.
Tool surface
What the model actually sees. Descriptions are diffed on every release — see version history.
Get the historical EPSS time series for a specific CVE. ## What this tool does Returns the historical EPSS score, percentile, and model version available for a CVE across time, ordered by date. Useful for analyzing how exploitability likelihood has evolved over time. ## When to use this tool Use this tool when the user asks about: - EPSS trend over time - how exploitability probability changed -
| Parameter | Type | Required | Notes |
|---|---|---|---|
| cve_id | string | yes | CVE identification (CVE-YYYY-NNNNN) |
Perform a Linux package vulnerability audit using SecDB. ## What this tool does Analyzes the installed packages of a Linux system-identified by OS and OS version-and returns vulnerability information plus a Markdown summary. The audit results are based exclusively on the package list provided by the user. ## When to use this tool Use this tool when the user wants to determine: - whether installe
| Parameter | Type | Required | Notes |
|---|---|---|---|
| os | string | yes | Linux distribution identifier supported by SecDB (use linux_os to obtain allowed values) |
| packages | string | yes | list of installed packages, one per line, generated using the appropriate system command |
| version | string | yes | OS version or codename corresponding to the selected distribution |
List supported Linux operating systems and their corresponding versions for use with the linux_audit tool. ## What this tool does Returns an array of supported OS/version pairs, each in the form: {"os":"name", "versions":["version or codename"]} This allows the LLM and the user to know exactly which inputs are valid for the linux_audit tool. ## When to use this tool Use this tool when:
No parameter schema on file.
Search real-world vulnerability sightings in SecDB. ## What this tool does Retrieves information about where and how a vulnerability appears in the real world, including: - Exploit-DB, Metasploit modules, PoCs - Scanner plugins (Nessus, OpenVAS/Greenbone) - Vendor advisories - Social/media references (Reddit, Mastodon, Bluesky) - MISP threat-intel sightings ## When to use this tool Use this tool
| Parameter | Type | Required | Notes |
|---|---|---|---|
| category | string | no | Sighting category (scanner, exploit, advisory, nasl, etc.) |
| cve_id | string | no | CVE identification (CVE-YYYY-NNNN) |
| query | string | no | Full-text-search for vulnerability name, CVE ID or Advisory ID, categories, etc. |
| status | string | no | Sighting status |
Compute CISA SSVC (Stakeholder-Specific Vulnerability Categorization) for a CVE. ## What this tool does Calculates the SSVC decision (Track, Track*, Attend, Act) using: - exploitation status - technical impact - automatable exploitation - mission prevalence (user-provided) - public well-being impact (user-provided) This reflects CISA's official SSVC prioritization model. ## When to use this too
| Parameter | Type | Required | Notes |
|---|---|---|---|
| cve_id | string | yes | CVE ID |
| mission_prevalence | string | yes | # Mission Prevalence A mission essential function (MEF) is a function directly related to accomplishing the organization's mission as set forth in its statutory or executive charter. Identifying MEFs |
| public_well_being_impact | string | yes | # Public Well-being Impact ## Possible values - "M" or "Minimal" Type of Harm -> All, The effect is below the threshold for all aspects described in material. - "A" or "Material" **Type of Ha |
Get detailed information about a specific CVE. ## What this tool does Retrieves the full vulnerability record for a CVE from SecDB, including: - official description and summary - CVSS metrics (all versions available) - EPSS metadata (if present) - affected products and versions - vendor/security advisories - references and upstream sources - weakness classification (CWE) - exploit and patch info
| Parameter | Type | Required | Notes |
|---|---|---|---|
| cve_id | string | yes | CVE identification (CVE-YYYY-NNNNN) |
Get CVSS and current EPSS score for a specific CVE. ## What this tool does Returns a full risk snapshot for a CVE, including: - CVSS version - CVSS base score - CVSS severity - CVSS vector string - human-readable explanation of the CVSS vector - current EPSS score The field cvss_explain provides a natural-language interpretation of the CVSS vector (attack conditions, privileges, user inter
| Parameter | Type | Required | Notes |
|---|---|---|---|
| cve_id | string | yes | CVE identification (CVE-YYYY-NNNNN) |
Perform a full-text vulnerability search in SecDB. ## What this tool does Searches across: - CVE entries - Security advisories - Exploit references - Product and vendor vulnerability data Results are formatted in Markdown and include a search summary. ## Searchable fields (Lucene syntax supported): - type: result type - cve, cwe, advisory, nasl, exploitdb, nuclei - id: exact identifier (e.g. id
| Parameter | Type | Required | Notes |
|---|---|---|---|
| query | string | yes | CVE ID, vulnerability name, Advisory ID, Exploit, etc. |
List available public ZEN SecDB feed reports. ## What this tool does Returns the catalog of available ZEN SecDB public feed reports, including their identifiers, descriptions, and supported input parameters. This tool helps discover which reports can be executed through feed_report. ## When to use this tool Use this tool when: - the user asks what public reports are available - you need to di
No parameter schema on file.
Run a public ZEN SecDB feed report. ## What this tool does Executes a predefined report on ZEN SecDB public feed data and returns structured results for analytics, trends, distributions, and top-N summaries. Supported reports can cover public datasets such as: - CVEs - security advisories - EPSS - weaknesses - CPE vendors and products - exploit references - sightings and IOC-related data Use `f
| Parameter | Type | Required | Notes |
|---|---|---|---|
| filters | object | no | optional object with report-specific filters |
| limit | string | no | optional maximum number of results to return, when supported by the selected report |
| report_id | string | yes | identifier of the report to execute |
Perform a software package vulnerability audit using SecDB. ## What this tool does Analyzes a list of software packages identified by PURL (Package URL) and returns vulnerability information plus a Markdown summary. The audit results are based exclusively on the package list provided. ## When to use this tool Use this tool when the user wants to determine: - whether application dependencies cont
| Parameter | Type | Required | Notes |
|---|---|---|---|
| purls | array | yes | List of Package URLs (PURL) to audit |
- Every tool — any call limit is its publisher’s, not ours
- No card, and mcprush charges nothing for it
- Runs at its publisher’s own address — this marketplace is not in the path
- Nothing to cap, because mcprush bills nothing
What counts against your monthly calls
| Tool | Unit | Calls used | Out of the allowance |
|---|
Nothing here is billable: mcprush charges nothing to install ZEN SecDB or to call it, at any volume.
Two independent axes, because powerful and malicious are different questions. The grade is threat only. The capability level is blast radius, and it is never a penalty on the grade — it is priced as one subtract-only term in the score, where you can see it.
This listing is an address its publisher runs, and you connect to it directly — this marketplace is not in the path. The scanner reads packages and public source, and an address is neither. So there is no grade — not a withheld one, an unmeasured one.
Release history
This is an address its publisher runs: which release it serves is theirs to choose, so there is nothing here to pin. The history below is for reading; the current release on file is 26.8.1.
No release note was published with this version.
One review per account, from a signed-in account that does not publish this listing. Nothing else is asked — you can say what you think before you install it. Publishers can reply once per review, and a review can be edited or deleted by whoever wrote it.
Any signed-in account that does not publish ZEN SecDB can review it, once — before installing it or after. A review from an account that has installed it is marked as one.
Nobody has reviewed this listing. The rating on the card is the mean of the reviews written here and nothing else, so there is no rating until somebody writes the first — which takes a signed-in account that does not publish it, and nothing else.