MCP.so
Sign In

VI+ MCP Server

@jgamblin

About VI+ MCP Server

An MCP Server for Cisco Vulnerability Management VI+ API

Basic information

Category

Developer Tools

License

MIT license

Runtime

python

Transports

stdio

Publisher

jgamblin

Config

Add this server to your MCP-compatible client using the configuration below.

{
  "mcpServers": {
    "VI-MCP": {
      "command": "docker",
      "args": [
        "build",
        "-t",
        "vi_mcp_server",
        "."
      ]
    }
  }
}

Tools

No tools detected

We auto-extract tools from the README. The maintainer can list them under a ## Tools heading to populate this section.

Overview

What is VI+ MCP Server?

The VI+ MCP Server is a Python-based application that fetches and formats details about Common Vulnerabilities and Exposures (CVEs) using the Cisco CVM API, providing structured summaries including risk scores, exploitability, and fixes.

How to use VI+ MCP Server?

Configure it as an MCP server in VS Code by adding a JSON entry under the "mcp" key in settings.json, specifying the command python and the path to vi-mcp.py. Alternatively, serve it via Open‑WebUI by cloning the repository, building the Docker image, and running the MCP‑to‑OpenAPI proxy (mcpo) with a command that includes the environment file.

Key features of VI+ MCP Server

  • Fetches CVE details using the Cisco CVM API.
  • Returns risk scores, exploitability, and fix information.
  • Runs as a Python‑based MCP server over stdio.
  • Can be exposed as REST APIs via Open‑WebUI and mcpo.
  • Suggests using the Gemma 3:12B model for Open‑WebUI.

Use cases of VI+ MCP Server

  • Querying CVE summaries and risk scores during security analysis.
  • Integrating vulnerability data into AI‑assisted code review (e.g., VS Code Copilot Chat).
  • Exposing CVE information as RESTful endpoints for broader toolchains.
  • Automating retrieval of Cisco CVM vulnerability insights.

FAQ from VI+ MCP Server

What runtime does VI+ MCP Server require?

Python must be installed and accessible from the terminal. A .env file with a RISK_TOKEN environment variable is required in the project root.

How can I expose VI+ MCP Server as a REST API?

Use the MCP‑to‑OpenAPI proxy (mcpo) with a Docker container: run uvx mcpo --port 8000 -- docker run -i --rm --env-file .env vi_mcp_server, then access the auto‑generated OpenAPI documentation at http://localhost:8000/docs.

What transport does VI+ MCP Server use?

It communicates via stdio when configured as an MCP server in VS Code, and can also be run inside a Docker container for HTTP‑based serving via mcpo.

Which model is recommended for use with Open‑WebUI?

The README suggests the Gemma 3:12B model (128K context window, multimodal) for optimal performance with MCP in Open‑WebUI.

How do I test the server?

Run the provided vi-mcp-test.py script after configuring the .env file. It fetches and displays details for a hardcoded CVE ID (CVE-2023-35078).

Comments

More Developer Tools MCP servers