claude-critical-rules

This MCP server enforces Claude AI safety and reliability by automatically applying and verifying 21 critical rules across five categories: Verification, Backups & Permissions, Execution & Validation, Database & Security, and Advanced. The server exposes a compact set of tools that you can invoke from Claude or via your MCP client integration. The key utilities are: verify_compliance, get_rules_summary, get_version_info, check_for_updates, and update_rules. Begin by loading the MCP into Claude Desktop (or your MCP-enabled workflow) using the recommended npx installation, then use verify_compliance to generate and review the mandatory 21-point checklist before any technical task. Use get_rules_summary for a quick reference of all rules, and keep the rule set up-to-date with check_for_updates and update_rules. The 21 rules guide consistent behavior, evidence-based validation, and safe execution practices during deployments or complex tasks.

Prerequisites:

• Node.js and npm installed on your system
• Access to the internet to fetch the MCP package from npm

Option A: Install and run via npx (recommended)

1. Ensure your environment is ready and Claude Desktop is configured to load MCP servers.
2. Add or update your Claude config to include the MCP server (see example below).
3. Use the MCP via npx as part of your Claude workflow.

Example steps:

# Ensure Node.js is installed
node -v
npm -v

# Use the MCP via npx (no global install required)
npx -y @optima-quantum/claude-critical-rules-mcp-new

Option B: Global install (alternative)

1. Install the MCP package globally so you can run it as a command:

npm install -g @optima-quantum/claude-critical-rules-mcp-new

2. Configure Claude to use the global command:

{
  "mcpServers": {
    "critical-rules": {
      "command": "claude-critical-rules-mcp"
    }
  }
}

Configure Claude Desktop to load the MCP server and restart Claude Desktop to apply changes.

Notes and tips:

• The MCP package provides automatic updates of the 21 rules from GitHub; ensure network access for update checks.
• The 21 rules are categorized for quick reference and include mandatory verification steps before performing technical tasks.
• If you use the npx approach, you don’t install the package globally; the MCP is fetched on demand.
• If you modify CLAUDE.Desktop configuration, verify the mcpServers section aligns with your local Claude installation paths.
• Keep an eye on version info (critical-rules:get_version_info) to know when updates are available and what changed (changelog reference).
• The MCP setup relies on standard environment variables for your overall environment; there are no required env vars explicitly documented for the server itself in the README.