# Ossec MCP

> Ossec MCP is an MCP server for security. MCP server for validating OSSEC rule ids, levels, groups and descriptions. It runs locally on your machine and is started by your AI client.

- **Kind:** MCP server
- **Repository:** https://github.com/mrfentmen/awesome-servers
- **MCP Registry name:** io.github.mrfentmen/ossec-mcp
- **Categories:** [security](https://ai-powered.com/categories/security)
- **Listing updated:** 2026-11-19

## About

The npm package @mrfentmen/ossec-mcp is aimed at people who maintain OSSEC rule sets and want an AI client to check them. According to its registry entry, it parses rules and validates each one's id, level, group and description, so mistakes can be caught before a rule set is deployed.

It runs as a local process over the stdio transport, which means an MCP-capable client starts it and talks to it directly. The registry lists version 1.0.0 with no environment variables, so no credentials are declared for setup. The README in the linked repository covers a wider collection of servers and does not describe this package's tools in detail.

It suits security engineers and SIEM administrators who write or review OSSEC rules and want a quick structural check during editing.

## Features

- **Rule parsing:** Reads OSSEC rule definitions so their fields can be inspected.
- **Rule id validation:** Checks that rule ids are present and well formed.
- **Severity level validation:** Checks the level assigned to each rule.
- **Group and description checks:** Validates the groups and descriptions attached to rules.

## Good for

- Checking an OSSEC rule file for structural errors before deployment
- Reviewing rule ids and severity levels across a rule set
- Finding rules with missing or malformed groups or descriptions

## Install

### Claude Code (Terminal)

```sh
claude mcp add ossec-mcp -- npx -y @mrfentmen/ossec-mcp
```

### Claude Desktop (claude_desktop_config.json)

```json
{
  "mcpServers": {
    "ossec-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "@mrfentmen/ossec-mcp"
      ]
    }
  }
}
```

### Cursor (~/.cursor/mcp.json)

```json
{
  "mcpServers": {
    "ossec-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "@mrfentmen/ossec-mcp"
      ]
    }
  }
}
```

### VS Code (.vscode/mcp.json)

```json
{
  "servers": {
    "ossec-mcp": {
      "type": "stdio",
      "command": "npx",
      "args": [
        "-y",
        "@mrfentmen/ossec-mcp"
      ]
    }
  }
}
```

### Windsurf (~/.codeium/windsurf/mcp_config.json)

```json
{
  "mcpServers": {
    "ossec-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "@mrfentmen/ossec-mcp"
      ]
    }
  }
}
```

### Other clients (your client's MCP settings (most use this shape))

```json
{
  "mcpServers": {
    "ossec-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "@mrfentmen/ossec-mcp"
      ]
    }
  }
}
```

## FAQ

### How is it installed?

The registry entry gives the npm identifier @mrfentmen/ossec-mcp at version 1.0.0, using the stdio transport.

### Does it need any environment variables?

The registry entry declares no environment variables.

### How do I add Ossec MCP to Claude Code?

Run this command in your terminal: claude mcp add ossec-mcp -- npx -y @mrfentmen/ossec-mcp

## Where this comes from

- Description: written from the project's README and its MCP Registry entry.
- Install steps: from the official MCP Registry entry.

---
Source: https://ai-powered.com/mcp/ossec-mcp
