Claude Critical Rules MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {} |
| resources | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| verify_complianceA | Verify if all mandatory checks from the critical rules have been completed before starting a technical task |
| get_rules_summaryA | Get a concise summary of the critical rules categories and main requirements |
| get_version_infoC | Get current version information and check if updates are available |
| check_for_updatesA | Check if a new version of the critical rules is available on GitHub |
| update_rulesB | Download and install the latest version of critical rules from GitHub |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
| Claude AI Critical Rules | Mandatory instructions to prevent 96 documented failure patterns |
| Rules Changelog | History of updates and changes to the critical rules |
TDQS
Scored across 5 tools
Tools are mostly distinct: check_for_updates and get_version_info have slight overlap (both check versions) but descriptions clarify differences. The other three tools have unique purposes.
All tool names follow a consistent verb_noun pattern in snake_case (e.g., check_for_updates, get_rules_summary), making them predictable and easy to distinguish.
Five tools is appropriate for a rules management server focused on checking, updating, and verifying compliance. Slightly more could be added (e.g., full rules listing), but the set is well-scoped.
Core operations are covered: checking updates, retrieving summary/version, updating rules, and verifying compliance. Missing a tool to fetch full rule details, but agents can work around with the summary.