Official description๐ โ๏ธ ๐ ๐ ๐ช ๐ง - Enforces critical rules for Claude to prevent documented failure patterns, with a compliance verification checklist and rules summary.
Config template (adjust for your client)
claude mcp add claude-critical-rules-mcp -- npx -y claude-critical-rules-mcp
A pasteable skeleton generated from the repository name. Check the project README for the exact package and arguments.
Star count
7 โ ยท optimaquantum/claude-critical-rules-mcp ยท read from the GitHub search API ยท (checked 2026-10-16 20:00:20)
Source
collected from the punkpeye/awesome-mcp-servers list ยท type: MCP server
Harvest history
first seen 2026-10-09 ยท last seen 2026-10-16 ยท seen 32ร ยท listed by 7 sources
Score
score 703 ยท 7 โ ยท 7 sources ยท mcp
FAQ (answers come from our records)
How do I install it?
We did not find an install command for this repository (our install coverage is only about 4%). Check its README or releases page.
Who is it for?
We filed it under these tags: MCP ๆๅก. The tags come from the entry itself, not a taxonomy we imposed.
Who maintains it?
repository optimaquantum/claude-critical-rules-mcp๏ผfirst catalogued 2026-10-09๏ผlast seen 2026-10-16ใThere is no official certification or quality rating here โ we record sources and dates only.
> **MCP server providing automatic enforcement of 21 critical rules for Claude AI, based on 96+ documented failure patterns** ๐ฏ What is this? An MCP (Model Context Protocol) server that makes critical best practices automatically available to Claude AI in every conversation. Based on exhaustive analysis of **96+ real documented failures** over 6+ months of intensive production usage. The system provides **21 numbered rules** organized into 5 categories, with automatic verification checklists, rule summaries, and auto-update capabilities. โจ Features - **21 Critical Rules** - Comprehensive checklist preventing common AI assistant failures - **5 Rule Categories** - Organized by: Verification, Backups, Execution, Database, Advanced - **Pre-flight Verification** - Mandatory checklist before technical tasks - **Auto-Update System** - Check and install rule updates from GitHub automatically - **Version Tracking** - SHA256 verification and changelog integration - **Evidence-based** - Every rule derived from real production failures โก Quick Install Via npx (Recommended) Add to your claude_desktop_config.json: **macOS:** ~/Library/Application Support/Claude/claude_desktop_config.json **Windows:** %APPDATA%\Claude\claude_desktop_config.json **Linux:** ~/.config/Claude/claude_desktop_config.json Via Global Install Then configure: Restart Claude Desktop After configuration, restart Claude Desktop to load the MCP server. ๐ Usage Instructions **CRITICAL: Two Mandatory Steps Before Any Technical Task** 1. **ALWAYS Read, Understand, and Execute Compliance Check** 2. **ALWAYS Read Appropriate Skill Documentation** **Example Workflow:** ๐ ๏ธ Available Tools verify_compliance Displays mandatory 21-rule checklist before technical tasks. **Usage:** **Returns:** - 21-point checklist organized by category - Rule numbers and descriptions - Confirmation requirements - Version information get_rules_summary Quick reference of all 21 rules with descriptions. **Usage:** **Returns:** - Core principles (5 items) - All 21 rules by category - 6-step mandatory workflow - Update instructions get_version_info Display current version and check for updates. **Usage:** **Returns:** - Current version details - Remote version comparison - Update availability status - SHA256 hash information check_for_updates Check GitHub for new rule versions. **Usage:** **Returns:** - Update availability status - Version comparison - Release date - Changelog reference update_rules Download and install latest rules from GitHub. **Usage:** **Returns:** - Update status - SHA256 verification - Backup location - Next steps ๐ Available Resources critical-rules://instructions Complete CRITICAL-RULES.md document with all 21 rules, examples, and detailed explanations. critical-rules://changelog Full changelog with version history and update details. ๐ The 21 Rules (Quick Reference) ๐ VERIFICATION (Rules 0-5) 0. Never act without reading instructions completely 1. Search current best practices (web_search mandatory) 2. Read skills before creating documents 3. Read ENTIRE file before modifying 4. VERIFY, not assume structures/locations 5. Check correct file/server ๐พ BACKUPS & PERMISSIONS (Rules 6-8) 6. Search previous context if mentioned