What is the key difference between Cisa Kev and GitHits?

Cisa Kev belongs to the Security category with local stdio execution, while GitHits belongs to the Security category with local stdio execution.

How do I install Cisa Kev or GitHits in Claude Desktop or Cursor?

Copy the mcpServers JSON configuration snippet provided on this page into your claude_desktop_config.json or ~/.cursor/mcp.json file and restart your AI client.

Are Cisa Kev and GitHits free or paid?

Cisa Kev operates under a Free / Open Source model (No auth required). GitHits operates under a Free / Open Source model (No auth required).

Which MCP server has more tools and community activity?

Cisa Kev lists 0 tools with 0 views and 0 GitHub stars. GitHits lists 0 tools with 0 views and 101 GitHub stars.

Can I use both Cisa Kev and GitHits together in the same MCP host?

Yes! MCP hosts like Claude Desktop, Cursor, Windsurf, Cline, and VS Code support configuring multiple servers under the mcpServers object simultaneously.

Side-by-Side Model Context Protocol Comparison

Cisa Kev vs GitHits

In-depth architectural comparison of the Cisa Kev and GitHits MCP servers. Compare execution transports, security boundaries, tool capabilities, quality scores, and ready-to-paste client installation snippets for Claude, Cursor, Windsurf, and VS Code.

At a Glance & Executive Verdict

Cisa Kev

Security · Local stdio

Quality: 32/100 (Emerging) | Auth: No auth required

GitHits

Security · Local stdio

Quality: 45/100 (Fair) | Auth: No auth required

Verdict Summary: Choose Cisa Kev if you need specialized Security tools running via a local process. Choose GitHits if your workspace requires Security integration with local subprocess execution. Both servers can be configured concurrently in your client's mcpServers manifest.

Which MCP Server Should You Choose?

Choose Cisa Kev when:

You need dedicated capabilities in the Security domain.
You prefer local stdio subprocess transport architecture.
Your security boundary fits: No auth required (Free / Open Source).

Explore Cisa Kev Details

Choose GitHits when:

You need dedicated capabilities in the Security domain.
You prefer local stdio subprocess transport architecture.
Your security boundary fits: No auth required (Free / Open Source).

Explore GitHits Details

Feature & Specification Comparison

Specification	C Cisa Kev Security	GitHits Security
Summary	CISA Known Exploited Vulnerabilities catalog	Search public open-source code, documentation, metadata, vulnerabilities, changelogs, and examples.
Category & Scope	Security	Security
Quality signal

Tools & Capabilities Breakdown

Cisa Kev Tools (0)

No explicit tool names declared in metadata yet. Check project README on main listing page.

GitHits Tools (0)

No explicit tool names declared in metadata yet. Check project README on main listing page.

Ready-to-Paste Client Configurations

Paste either (or both) of these JSON server blocks into your client config file (e.g. claude_desktop_config.json or ~/.cursor/mcp.json).

Cisa Kev Configuration

mcpServers (Claude Desktop / Cursor)

{
  "mcpServers": {
    "cisa-kev": {
      "command": "npx",
      "args": [
        "-y",
        "cisa-kev"
      ]
    }
  }
}

GitHits Configuration

mcpServers (Claude Desktop / Cursor)

{
  "mcpServers": {
    "githits": {
      "command": "npx",
      "args": [
        "-y",
        "githits@latest"
      ]
    }
  }
}

Frequently Asked Questions

Cisa Kev is categorized under Security and uses a local stdio subprocess. In contrast, GitHits belongs to Security using local stdio subprocess. Select Cisa Kev when you need capabilities focused on security and GitHits when you require tools for security.

More alternatives to Cisa Kev More alternatives to GitHits Security category hub