CIRCL CVE SEARCH MCP Server

Created By
Cyreslab-AIa year ago
MCP server for CIRCL CVE Search API with intelligent risk assessment and comprehensive vulnerability analysis.
Overview

What is CIRCL CVE SEARCH MCP Server?

CIRCL CVE SEARCH MCP Server is a Model Context Protocol (MCP) server designed to access the CIRCL CVE SEARCH API, providing comprehensive vulnerability and security information.

How to use CIRCL CVE SEARCH MCP Server?

To use the server, install it via npm and configure it in your MCP client. You can access various tools to retrieve CVE, CWE, and CAPEC information.

Key features of CIRCL CVE SEARCH MCP Server?

  • Access to detailed CVE information
  • Vendor browsing for CVEs
  • CWE and CAPEC information retrieval
  • Enhanced error handling and input validation

Use cases of CIRCL CVE SEARCH MCP Server?

  1. Security analysts can retrieve detailed vulnerability information for risk assessment.
  2. Developers can browse CVEs by vendor to identify security issues in their products.
  3. Researchers can analyze attack patterns using CAPEC data.

FAQ from CIRCL CVE SEARCH MCP Server?

  • Is the server free to use?

Yes, the CIRCL CVE SEARCH API is free to use without authentication.

  • What programming language is it built with?

The server is built using JavaScript.

  • How can I report issues?

You can report issues on the GitHub repository under the Issues section.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
Cyreslab-AI
Star
0
Language
JavaScript
License
MIT license

Recommend Servers

View All
Bring your real authenticated browser session to AI coding agents. Local-first MCP server + Chrome MV3 extension. No cloud. No telemetry.
@Cubenest

peek records the user's actual logged-in browser (DOM via rrweb, console events, network metadata, optional response bodies via opt-in Deep capture) through a Chrome MV3 extension. The extension ships events through a native-messaging stdio bridge to a local MCP server (peek-mcp), which persists them to a SQLite database at ~/.peek/sessions.db. AI coding agents (Claude Code, Cursor, Cline, Windsurf) read sessions from the database via 10 MCP tools: Tool What it does list_recent_sessions List recently recorded sessions (id, origin, ts, event count). get_session_summary LLM-readable narrative summary of a session. get_session_console_errors Console errors recorded in a session. get_session_network_errors Failed/notable network requests in a session. get_user_action_before_error Last N user actions before a console error. generate_playwright_repro Generate a runnable Playwright test from a session. get_dom_snapshot Reconstruct the DOM at a given timestamp. query_dom_history Timeline of attribute/text changes for a selector. request_authorization Side-panel consent for write actions (Level 3). execute_action Dispatch a UI action (gated by permission level + destructive blocklist). Why local-first matters Every other "browser session for AI" tool ships to a vendor cloud. peek's SQLite + extension live on the user's machine — no remote endpoints, no telemetry. The privacy policy (docs/peek/PRIVACY_POLICY.md) is the source of truth. Install # 1. Add the MCP server to Claude Code claude mcp add peek -- npx -y @peekdev/mcp # 2. Install the Chrome extension from the Chrome Web Store # (link added once the CWS listing is approved)

4 hours ago
Gpt Scrambler

a day ago