ProdSec Compliance MCP Server

A Model Context Protocol (MCP) server that provides compliance information and tools through a standardized interface. This server enables AI agents to access and process compliance-related data efficiently.

Quick Start

Environment Configuration

The server uses the following environment variable:

• COMPLIANCE_API_HOST: Base URL for the compliance API (defaults to 'https://access.redhat.com' if not set)

Testing with MCP Inspector

Test the server using the official MCP Inspector:

# With custom API base URL
npx -y @modelcontextprotocol/inspector -e COMPLIANCE_API_HOST=https://your-compliance-api-url npx -y prodsec_compliance_mcp_server

# With default API base URL
npx -y @modelcontextprotocol/inspector npx -y prodsec_compliance_mcp_server

Integration with AI Agents

Add the server to your AI agent configuration:

{
  "mcpServers": {
    "compliance": {
      "command": "npx",
      "args": ["-y", "prodsec_compliance_mcp_server"],
      "env": {
        "COMPLIANCE_API_HOST": "https://your-compliance-api-url"
      }
    }
  }
}

Installation

Global Installation

Install the package globally for system-wide access:

npm install -g prodsec_compliance_mcp_server

Direct Usage

Run the server directly without installation:

# With custom API base URL
COMPLIANCE_API_HOST="https://your-compliance-api-url" npx prodsec_compliance_mcp_server

# With default API base URL
npx prodsec_compliance_mcp_server

Usage

Start the server:

# With custom API base URL
COMPLIANCE_API_HOST="https://your-compliance-api-url" prodsec_compliance_mcp_server

# With default API base URL
prodsec_compliance_mcp_server

The server will initialize and await MCP client connections.

Features

• Compliance Tools: Access compliance-related information and tools
  • search-compliance: Search for compliance information with optional keywords (defaults to "*")
• Parallel API Processing: Optimized performance with parallel API requests
• MCP Protocol: Full support for Model Context Protocol
• TypeScript: Built with TypeScript for type safety
• ES Modules: Modern JavaScript module system
• Cross-Platform: Works on Windows, macOS, and Linux

Available Tools

search-compliance

Search Red Hat product compliance information based on keywords. Returns detailed compliance documents containing product information, regional applicability, industry sectors, brief and long descriptions, links to resources, and attachments.

Parameters:

• keywords (optional): Keywords to search for in compliance information. Defaults to "*" which returns the first 5 compliances from the search results.

Example:

{
  "keywords": "GDPR"
}

Development

Prerequisites

• Node.js (v16 or higher)
• npm (v7 or higher)

SSL Certificate Verification

For development environments using self-signed certificates, you may need to disable SSL certificate verification. You can do this in two ways:

1. Uncomment the following line in src/index.ts:

// process.env.NODE_TLS_REJECT_UNAUTHORIZED = '0';

2. Set the environment variable manually when running the server:

# On Linux/macOS
NODE_TLS_REJECT_UNAUTHORIZED=0 node build/index.js

# On Windows (Command Prompt)
set NODE_TLS_REJECT_UNAUTHORIZED=0 && node build/index.js

# On Windows (PowerShell)
$env:NODE_TLS_REJECT_UNAUTHORIZED=0; node build/index.js

Warning: Never disable SSL certificate verification in production environments as it poses significant security risks. This setting should only be used during development.

Local Development

1. Clone the repository:

git clone <repository-url>
cd mcp_server

2. Install dependencies:

npm install

3. Build the project:

npm run build

Publishing

To publish a new version:

1. Update the version in package.json
2. Build the project: npm run build
3. Publish to npm: npm publish

Project Structure

mcp_server/
├── src/
│   └── index.ts      # Main server implementation
├── build/            # Compiled JavaScript output
├── package.json      # Project configuration
└── tsconfig.json     # TypeScript configuration

Dependencies

• @modelcontextprotocol/sdk: Official MCP SDK for server implementation
• zod: Runtime type checking and validation

License

ISC

Contributing

We welcome contributions! Please follow these steps:

1. Fork the repository
2. Create a feature branch (git checkout -b feature/amazing-feature)
3. Commit your changes (git commit -m 'Add amazing feature')
4. Push to the branch (git push origin feature/amazing-feature)
5. Open a Pull Request

Support

For issues and feature requests, please open an issue on GitHub.