Loading...

Cve Search Review, Pricing & Alternatives (2026) | Flaex AI

Back to MCP Directory

Model Context Protocol low risk

Cve Search

This MCP server provides access to CVE-Search API, enabling users to query vulnerability information, vendor/product details, and database statistics.

Connections & Capabilities

Connects To

GitHub

Capabilities

read

Exposed MCP Tools (6)

safe

get_vendors

Retrieves a JSON list of all vendors in the CVE database.

Read-only operation, no modification of data.

safe

get_products_by_vendor

Retrieves a JSON list of products associated with a specific vendor.

Read-only operation, no modification of data.

safe

get_vulnerabilities_by_vendor_product

Retrieves a JSON list of vulnerabilities for a specific vendor and product.

Read-only operation, no modification of data.

safe

get_cve_by_id

Retrieves a JSON representation of a specific CVE ID.

Read-only operation, no modification of data.

safe

get_last_30_cves

Retrieves a JSON list of the last 30 CVEs, including CAPEC, CWE, and CPE expansions.

Read-only operation, no modification of data.

safe

get_database_info

Retrieves a JSON with information about the current databases in use and when they were last updated.

Read-only operation, no modification of data.

Safety Assessment

This MCP server is generally safe due to its read-only nature and reliance on a well-established vulnerability database. Risks are primarily associated with the security and availability of the CVE-Search API itself. It is safe to use for querying vulnerability information but keep in mind the limitations of a third-party API.

Read-only access to CVE data.
No write or delete operations.
Queries are performed against a public API.
No local execution of code.

Reliance on the security of the CVE-Search API.
Potential for information disclosure if the API is compromised.
Rate limiting by the CVE-Search API could impact availability.