在一个 MCP 服务器中整合来自 4 个政府数据源的统一漏洞情报。通过单次调用即可获取包含 CVSS 评分、主动利用状态、利用概率和 ATT&CK 技术的丰富 CVE 查询结果。
数据源 | 提供内容 | 更新频率 |
NIST NVD 2.0 | CVE 详情、CVSS 评分、描述、参考资料、CWE 分类 | 持续更新 |
CISA KEV | 已被主动利用的漏洞目录、修复截止日期 | 每日 |
FIRST.org EPSS | 利用概率评分 (0-1)，预测未来 30 天内被利用的可能性 | 每日 |
MITRE ATT&CK | 映射到 CVE 的攻击者技术 | 每季度 |
vuln_lookup_cve — 丰富的 CVE 查询核心功能。查询任何 CVE 并通过单次调用获取来自所有 4 个数据源的情报。
输入: { cveId: "CVE-2021-44228" }
返回: NVD 详情 + CVSS 评分 + KEV 利用状态 + EPSS 概率 + ATT&CK 技术
vuln_search — 搜索 CVE按关键字、严重程度和日期范围搜索 NVD。可选择仅筛选已被主动利用 (KEV) 的漏洞。
输入: { keyword: "apache log4j", severity: "CRITICAL", hasKev: true, limit: 20 }
vuln_kev_latest — 最近被利用的漏洞获取最近添加到 CISA“已知被利用漏洞”目录中的漏洞。
输入: { days: 7, limit: 20 }
vuln_kev_due_soon — 即将到期的修复截止日期获取修复截止日期临近的 KEV 条目。对于联邦合规性至关重要。
输入: { days: 14, limit: 20 }
vuln_epss_top — 最高利用概率基于 EPSS 机器学习模型，获取未来 30 天内最可能被利用的 CVE。
输入: { threshold: 0.7, limit: 20 }
vuln_trending — 新发布的严重 CVE从 NVD 获取最近发布的高/严重级别 CVE。
输入: { days: 3, severity: "CRITICAL", limit: 20 }
vuln_by_vendor — 供应商漏洞评估搜索特定供应商/产品的 CVE。与 CISA KEV 进行交叉引用，以标记已被主动利用的问题。
输入: { vendor: "microsoft", product: "windows", limit: 20 }
Related MCP server: NVD MCP Server
漏洞分类: 查询 CVE 并立即了解其是否被主动利用、其 EPSS 评分以及适用的 ATT&CK 技术
补丁优先级排序: 结合 KEV 状态 + EPSS 评分来确定修复优先级
合规性跟踪: 监控即将到来的 CISA KEV 修复截止日期
威胁情报: 跟踪热门 CVE 和新出现的武器化漏洞
供应商风险评估: 评估供应商的漏洞暴露情况和主动利用状态
从 Glama.ai 安装。
{
"mcpServers": {
"cybersecurity": {
"url": "https://cybersecurity-vuln-mcp.apify.actor/mcp"
}
}
}{
"mcpServers": {
"cybersecurity": {
"command": "node",
"args": ["path/to/servers/cybersecurity-vuln-mcp/dist/stdio.js"],
"env": {
"NVD_API_KEY": "your-key-here"
}
}
}
}git clone https://github.com/martc03/gov-mcp-servers.git
cd gov-mcp-servers/servers/cybersecurity-vuln-mcp
npm install && npm run build
node dist/stdio.js变量 | 必需 | 描述 |
| 否 | 用于更高速率限制的 NVD API 密钥（50 次请求/30秒 vs 5 次请求/30秒）。在此注册。 |
数据源 | TTL | 备注 |
NVD CVE 查询 | 1 小时 | 每个 CVE |
CISA KEV 目录 | 2 小时 | 完整目录 |
EPSS 评分 | 24 小时 | 每个 CVE |
ATT&CK 映射 | 静态 | 随服务器捆绑 |
协议: 基于 stdio 的 MCP (Glama/本地) 或 Streamable HTTP (Apify)
运行时: Node.js 18+, TypeScript
数据: 直接调用免费政府数据源 API，零成本
缓存: 内存中缓存，具有可配置的 TTL
本仓库包含 13 个用于美国政府数据的 MCP 服务器。详情请参阅各服务器的 README。
服务器 | 工具 | 数据源 |
4 | NHTSA 召回, FDA 召回 | |
4 | FEMA 灾害, NOAA 天气, USGS 地震 | |
4 | SEC EDGAR, CFPB 投诉, BLS 就业 | |
3 | 签证公告, 边境等待时间 | |
3 | EPA 空气质量, HUD 止赎 | |
4 | SAM.gov 合同, USAspending | |
4 | PACER, 联邦法院记录 | |
4 | NIH 临床试验, FDA 不良事件 | |
4 | SEC 公司搜索, SBA 资源 | |
4 | 联邦公报, regulations.gov | |
4 | Grants.gov, USAspending | |
4 | SEC 文件, 专利数据, 贸易数据 |
一个包含 45 个端点的 REST API 网关 也可在 govdata-api.netlify.app 获取。
NVD: 本产品使用 NVD API 的数据，但未经 NVD 背书或认证。
EPSS: 数据由 FIRST.org 提供 (https://www.first.org/epss/)。
ATT&CK: The MITRE Corporation 的注册商标。根据 Apache 2.0 许可授权。
KEV: CISA 已知被利用漏洞目录，美国政府公共领域数据。
需要为您的业务定制 MCP 服务器吗？请访问 mcpdev.netlify.app 或发送电子邮件至 codee.mcpdev@gmail.com。
MIT
Search CVEs for a specific vendor/product, cross-referenced with CISA KEV.
| Name | Required | Description | Default |
|---|---|---|---|
| vendor | Yes | Vendor name (e.g., 'microsoft', 'apache') | |
| product | No | Product name (e.g., 'windows', 'log4j') | |
| limit | No |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations, the description carries full behavioral burden. It mentions cross-referencing with KEV but does not disclose side effects, rate limits, error handling, or whether results are limited to KEV entries.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
Single sentence, front-loaded with action and resource, no wasted words.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
The description is too brief given 3 parameters and no output schema. Missing details on required fields, optional parameter purpose, return format, and cross-reference behavior.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema coverage is 67% (vendor and product described, limit not). The description adds no extra meaning beyond the schema; limit parameter remains undocumented. Baseline 3 as schema covers most.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description clearly states the tool searches for CVEs by vendor/product and cross-references with CISA KEV, which distinguishes it from sibling tools like vuln_search or vuln_lookup_cve.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
The description provides no explicit guidance on when to use this tool versus alternatives, nor does it mention prerequisites or excluded use cases. Sibling tools are listed but not referenced.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Get CVEs with highest EPSS exploitation probability scores.
| Name | Required | Description | Default |
|---|---|---|---|
| threshold | No | Minimum EPSS score (0-1) | |
| limit | No |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations, the description must fully disclose behavior. It only states the tool retrieves top-scoring CVEs but does not explain the role of threshold and limit parameters, or describe the output format. Important behavioral aspects like pagination or sorting order are omitted.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is a single, efficient sentence. However, its brevity sacrifices necessary detail, making it feel incomplete rather than concise.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
Given the tool's simplicity (2 parameters, no output schema), the description is insufficient. It does not explain the return value structure, how the threshold and limit interact, or typical usage. A more complete description would include the output format and the relationship between parameters.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
The input schema already describes both 'threshold' and 'limit' parameters, but the context indicates only 50% schema description coverage. The description does not add any additional meaning or context for the parameters beyond what is in the schema, failing to compensate for the coverage gap.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description 'Get CVEs with highest EPSS exploitation probability scores' clearly indicates the tool returns top CVEs ranked by EPSS score. It is a specific verb-resource combination that distinguishes it from sibling tools like vuln_search or vuln_lookup_cve. However, it could be more explicit about the descending order and the inclusion of parameters.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
No guidance is provided on when to use this tool versus alternatives, such as vuln_search or vuln_by_vendor. There is no mention of prerequisites, limitations, or scenarios where this tool is not appropriate.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Get CISA KEV vulnerabilities with upcoming remediation deadlines.
| Name | Required | Description | Default |
|---|---|---|---|
| days | No | Deadline within next N days | |
| limit | No |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations provided. Description describes a read operation ('Get') but lacks details on authentication, rate limits, result ordering, pagination, or behavior when no results are found. Minimal behavioral disclosure.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
Single sentence, no unnecessary words. However, it may be too concise, sacrificing completeness. Structure is fine.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
Given no output schema, no annotations, and partial schema coverage, the description is insufficient. Missing information on return format, sorting, or interpretation of 'upcoming remediation deadlines'. Incomplete for effective tool selection.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema coverage is 50% (days parameter has description, limit does not). The tool description does not add any meaning beyond the schema; it does not explain how 'days' relates to 'due soon' or the role of 'limit'. No enrichment provided.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
Description clearly states the tool retrieves CISA KEV vulnerabilities with upcoming remediation deadlines. It uses specific verb 'Get' and resource 'CISA KEV vulnerabilities', distinguishing it from siblings like vuln_kev_latest which focuses on latest entries.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
The description implies usage for upcoming deadlines but provides no explicit guidance on when to use this tool versus alternatives like vuln_kev_latest or other sister tools. No when-not-to-use or contextual prerequisites are mentioned.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Get recently added CISA KEV entries (actively exploited vulnerabilities).
| Name | Required | Description | Default |
|---|---|---|---|
| days | No | Look back N days | |
| limit | No |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are provided, so the description carries the full burden. It correctly indicates a read operation returning vulnerability entries, but lacks details on output format, pagination, or rate limits. The description is adequate but not comprehensive.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
A single, concise sentence of 7 words contains all essential information without fluff. Every word earns its place.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
The tool is simple (2 optional params, no output schema), and the description provides a basic understanding. However, it does not explain the return format or pagination behavior (implied by 'limit'), and lacks annotation context. Given the absence of output schema, more detail would help, but the description is minimally functional.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema coverage is 50% (only 'days' has a description). The tool description does not add any parameter details beyond the schema's 'Look back N days' for 'days' and leaves 'limit' with no semantic explanation. No extra meaning is provided to compensate for the coverage gap.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description clearly states 'Get recently added CISA KEV entries', specifying the verb (Get), resource (CISA KEV entries), and temporal scope (recently added). This distinguishes it from sibling tools like vuln_by_vendor (vendor-specific) or vuln_epss_top (EPSS ranking).
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
No explicit guidance on when to use this tool versus alternatives. While the description implies usage for recent KEV entries, it does not mention exclusions or recommend sibling tools for other cases (e.g., vuln_lookup_cve for specific CVEs).
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Look up a CVE by ID and get enriched intelligence: NVD details (CVSS score, description, references), CISA KEV active exploitation status, EPSS exploitation probability score, and MITRE ATT&CK techniques.
| Name | Required | Description | Default |
|---|---|---|---|
| cveId | Yes | CVE identifier (e.g., CVE-2021-44228) |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are provided, so the description carries the full burden. It discloses that the tool aggregates data from NVD, CISA KEV, EPSS, and MITRE ATT&CK, indicating a read-only operation. Missing details like rate limits or response format, but the description is still informative.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is a single sentence that efficiently lists the tool's capabilities without any extraneous words. It is front-loaded with the purpose 'Look up a CVE by ID' and then enumerates sources.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
Given the complexity of aggregating multiple intelligence sources, the description covers the key outputs but doesn't detail return structure or potential pagination. Since output schema is absent, a slightly more detailed description of the return format would improve completeness.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
The input schema provides 100% coverage with a clear description and pattern for the cveId parameter. The description does not add additional semantics beyond what the schema already states, so baseline score of 3 applies.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description clearly states the tool looks up a CVE by ID and returns enriched intelligence from multiple sources (NVD, CISA KEV, EPSS, MITRE ATT&CK). It distinguishes from siblings like vuln_search or vuln_by_vendor by focusing on a single CVE identifier.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
The description explicitly says 'Look up a CVE by ID', providing clear context for when to use this tool. However, it does not explicitly mention when not to use it or contrast it with sibling tools, but the context is strong enough.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Search the NIST NVD for CVEs by keyword, severity, and date range.
| Name | Required | Description | Default |
|---|---|---|---|
| keyword | No | Search keyword (e.g., 'apache log4j') | |
| severity | No | CVSS v3.1 severity | |
| pubStartDate | No | Start date ISO format | |
| pubEndDate | No | End date ISO format | |
| hasKev | No | Only show actively exploited CVEs | |
| limit | No |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Without annotations, the description does not explicitly state the tool's read-only nature or any side effects. It merely describes the search functionality, leaving behavioral assumptions to the agent.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is a single 12-word sentence that efficiently conveys the core purpose with no redundant information.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
The description does not mention return format, pagination, or how results are ordered. With no output schema, this information is critical for an agent to understand how to use the output.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
The schema has 83% parameter description coverage, so the baseline is 3. The description only mentions three parameters (keyword, severity, date range) without adding new meaning beyond the schema.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description clearly states the tool searches the NIST NVD for CVEs by keyword, severity, and date range. It distinguishes itself from siblings like vuln_by_vendor (vendor-specific) and vuln_lookup_cve (single CVE lookup).
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
No guidance is provided on when to use this tool versus sibling tools like vuln_epss_top or vuln_kev_due_soon. The description lacks any context about alternatives or prerequisites.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Get recently published critical/high severity CVEs from the NVD.
| Name | Required | Description | Default |
|---|---|---|---|
| days | No | Published within last N days | |
| severity | No | CRITICAL | |
| limit | No |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations provided, the description must fully disclose behavior but only states the basic function. It omits details on rate limits, data freshness, response structure, or whether the operation is read-only.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is a single, concise sentence that conveys the main purpose without extraneous details. However, it could be expanded slightly for clarity without losing conciseness.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
Given the tool has 3 parameters, no output schema, and no annotations, the description is insufficient. It does not explain return values, pagination, or edge cases, leaving significant gaps for an agent.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
The description adds no value beyond the input schema. Schema coverage is low (33%), but the description doesn't explain parameter meanings or relationships, such as how 'days' and 'severity' interact.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description clearly states the verb 'Get' and the resource 'recently published critical/high severity CVEs from the NVD', effectively conveying the tool's purpose and distinguishing it from siblings like vuln_search. However, it inaccurately restricts severity to critical/high when the parameter allows all levels.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
No guidance on when to use this tool versus alternatives (e.g., vuln_by_vendor, vuln_search). The description does not specify contexts where this tool is preferred or when to avoid it.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
v0.1.0vuln_by_vendorvuln_epss_topvuln_kev_due_soonvuln_kev_latestvuln_lookup_cvevuln_searchvuln_trendingScored across 7 tools
Tools are mostly distinct, with slight overlap between vuln_kev_due_soon and vuln_kev_latest (both KEV-focused but different filters) and between vuln_trending and vuln_epss_top (different criteria for prioritizing CVEs). Descriptions clarify differences.
All tool names follow the pattern vuln_<descriptive_name>, using underscores and consistent noun/verb structure. No mixing of conventions.
7 tools cover the core vulnerability intelligence domain without being excessive. Each tool serves a clear purpose, and the count is well-scoped.
The surface covers search, lookup, trending, exploitation probability, and KEV monitoring comprehensively. Minor gaps exist, such as no tool for patch or fix version information, but overall the set is complete for its informational purpose.
CVE intelligence: exploitation (KEV/EPSS), detection coverage, fixed versions. All tools keyless.
Real-time CVE, exploit, and vulnerability intelligence for AI assistants (350K+ CVEs, 115K+ PoCs)
CVE search, vulnerability database, EPSS exploit prediction, KEV, IP reputation & threat feed.
Search and audit NIST NVD CVEs by keyword, severity, CWE, CISA KEV status, and CPE.
