Rules MCP
NPM · @AKR1166ORG/RULES-MCP · SCANNED AUG 19
MCP for rules/skills/knowledge evaluation for Cursor, Claude, VS Code, and Antigravity.
Available components
How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score →
Supply Chain Security98
- No malware found by supply-chain analysis.Pass
- No known CVEs affecting this package version or its production dependencies.Pass
- No install/post-install scripts declared.Pass
- 30 of 96 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency19
- Repository check failed: the declared repository URL returned HTTP 404. See how to fix → View diagnostics → Fail
- Provenance check failed: no build-provenance attestation is published. See how to fix → View diagnostics → Fail
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 7 days ago).Pass
- Security-disclosure policy not yet verified: we couldn't inspect the source repository.Unverified
Schema Quality & AI Usability85
- 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
- AI-judged instruction clarity (good).Pass
- Tool/resource definitions use about 1578 tokens (~75/item across 21 items; 19 tools + 2 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management27
- Stability observed for 8 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage86
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 58% of tool parameters carry a description.Partial
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Add this component to your MCP client. Where a client-specific snippet is available, pick your client below and copy it straight into your config; otherwise use the connection detail shown.
npm · @akr1166org/rules-mcp
claude mcp add akr1166-rules-mcp -- npx -y @akr1166org/rules-mcp
codex mcp add akr1166-rules-mcp -- npx -y @akr1166org/rules-mcp
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"akr1166-rules-mcp": {
"type": "local",
"command": [
"npx",
"-y",
"@akr1166org/rules-mcp"
],
"enabled": true
}
}
} openclaw mcp add akr1166-rules-mcp --command npx --arg -y --arg @akr1166org/rules-mcp
mcp_servers:
akr1166-rules-mcp:
command: "npx"
args: ["-y", "@akr1166org/rules-mcp"] {
"mcpServers": {
"akr1166-rules-mcp": {
"command": "npx",
"args": [
"-y",
"@akr1166org/rules-mcp"
]
}
}
} Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 19 Aug 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 23 to 27. That category is still filling its 30-day observation window: 7 days of observed history at the previous scan, 8 at this one. The score rises as the window fills, whether or not the server changes.
- 18 Aug 26 +3
- Stability: unverified → 0.23 ▲ functional
- 12 Aug 26 +15
- Malware scan: unverified → pass ▲ security
- 11 Aug 26 49
First indexed and scored.
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 19 Aug 2026 · Analysed npm/@akr1166org/rules-mcp@0.3.1
Provenance No attestation
The registry publishes no build provenance for this version, so there is nothing to verify.
| Result | No attestation |
|---|---|
| Ecosystem | npm |
Dependencies 96 packages
| Packages resolved | 96 |
|---|---|
| Stale | 30 |
| Tree resolution | Complete |
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability.
enrich_prompt Enrich prompt ~79
Turn a short feature request into a full governed instruction set using project YAML rules, cursor skills (MD/MDC), and knowledge. Includes skillsDisclosure — the agent must open the user-visible reply with that section (skills chosen + why).
| Name | Type | Req | Description |
|---|---|---|---|
| files | array | – | – |
| intent | string | yes | Short user request |
| profile | string | – | – |
No output schema declared.
No examples provided.
explain_violation Explain violation ~66
Explain a rule/violation by ID: rule text, reason, good/bad examples, exceptions, and related knowledge. Use when the user asks why a rule failed or what TS001/SEC001 means.
| Name | Type | Req | Description |
|---|---|---|---|
| ruleId | string | yes | Rule ID such as TS001 |
No output schema declared.
No examples provided.
generate_artifacts Generate artifacts ~97
Generate agent instruction files from the YAML rule source of truth: .cursor/rules, AGENTS.md, CLAUDE.md, STYLEGUIDE.md, SECURITY.md, CONTRIBUTING.md, PR checklist, and prompt templates. Use when the user asks to sync or regenerate governance artifacts.
| Name | Type | Req | Description |
|---|---|---|---|
| outputDir | string | – | Directory to write into (default: process.cwd()) |
| targets | array | – | Defaults to all Phase 2 targets |
No output schema declared.
No examples provided.
get_context Get context ~115
Gather relevant YAML rules, Markdown/MDC skills (from cursor skills/), and knowledge for a coding task. Returns skillsDisclosure — paste that block at the start of your reply before answering. Prefer calling this or select_skills first on every coding prompt.
| Name | Type | Req | Description |
|---|---|---|---|
| files | array | – | Relevant file paths |
| profile | string | – | AI profile id: cursor, claude, default |
| tags | array | – | – |
| task | string | yes | What the agent is trying to do |
| tokenBudget | integer | – | – |
No output schema declared.
No examples provided.
get_knowledge Get knowledge ~57
Retrieve project knowledge (architecture, FAQs, module docs). Use when the user asks how the project is structured or about architecture/domain knowledge.
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | – | – |
| query | string | – | – |
| tags | array | – | – |
No output schema declared.
No examples provided.
get_rule Get rule ~61
Fetch full details for one YAML governance rule by ID (e.g. TS001, SEC001). For Markdown skills, use get_skill with a skill slug (e.g. typescript-expert).
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | Rule ID such as TS001 |
No output schema declared.
No examples provided.
get_skill Get skill ~65
Fetch one skill by slug/id from cursor skills/ (e.g. typescript-expert, nestjs-best-practices/security-validate-all-input). Skills are MD/MDC, not YAML.
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | Skill id/slug such as typescript-expert |
No output schema declared.
No examples provided.
list_rules List rules ~105
List project coding/governance rules from rules/*.yaml (enforceable standards and policies). For Cursor agent skills (Markdown/MDC under cursor skills/), use list_skills instead.
| Name | Type | Req | Description |
|---|---|---|---|
| category | string | – | – |
| kind | string | – | – |
| priority | string | – | – |
| status | string | – | – |
| summary | boolean | – | If true (default), return compact summaries instead of full rules |
| tags | array | – | Tags that must all match |
No output schema declared.
No examples provided.
list_skills List skills ~99
List Cursor agent skills loaded from cursor skills/ as Markdown (.md) or MDC (.mdc). Use when the user asks what skills exist or which skill guidance applies.
| Name | Type | Req | Description |
|---|---|---|---|
| category | string | – | – |
| kind | string | – | – |
| parentId | string | – | Parent skill id for nested skill-rules |
| summary | boolean | – | If true (default), return compact summaries instead of full bodies |
| tags | array | – | – |
No output schema declared.
No examples provided.
ping Ping ~35
Health check for Rules MCP. Returns server version, phase, and configured paths.
| Name | Type | Req | Description |
|---|---|---|---|
| message | string | – | Optional message to echo back |
No output schema declared.
No examples provided.
review_diff Review diff ~98
Review a unified git diff/patch against project rules. Reports violations on new/changed lines. Use when the user asks to review a PR diff, patch, or staged changes for standards compliance.
| Name | Type | Req | Description |
|---|---|---|---|
| baseFiles | object | – | Optional map of path → full file content when the patch lacks full context |
| newViolationsOnly | boolean | – | Only report violations on added lines (default true) |
| patch | string | yes | Unified diff text |
No output schema declared.
No examples provided.
score_output Score output ~74
Produce a governance scorecard (aiScore, category scores, blocking, failedCritical) for code. Use when the user asks for a quality/compliance score.
| Name | Type | Req | Description |
|---|---|---|---|
| code | string | – | Source code to score |
| filePath | string | – | – |
| language | string | – | – |
| runExternal | boolean | – | – |
No output schema declared.
No examples provided.
search_knowledge Search knowledge ~60
Ranked search across project knowledge docs (architecture, FAQ, modules). Use when the user asks to find docs about a topic with relevance ranking.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | – |
| query | string | yes | Search query |
| tags | array | – | – |
No output schema declared.
No examples provided.
search_rules Search rules ~46
Search YAML governance rules by keyword (security, logging, python, secrets, etc.). For Cursor skills under cursor skills/, use search_skills.
| Name | Type | Req | Description |
|---|---|---|---|
| query | string | yes | Search query |
No output schema declared.
No examples provided.
search_skills Search skills ~41
Search Markdown/MDC skills under cursor skills/ by keyword (nestjs, typescript, prompt, security, etc.).
| Name | Type | Req | Description |
|---|---|---|---|
| query | string | yes | Search query |
No output schema declared.
No examples provided.
select_skills Select skills ~98
PRIMARY first step for any coding/governance prompt: automatically pick relevant cursor skills for the user's task and return a ready-to-paste 'Skills used' disclosure (id, why, score). Call this (or get_context) before answering, then paste skillsDisclosure at the start of your reply.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | – |
| tags | array | – | – |
| task | string | yes | The user's prompt / what they asked for |
No output schema declared.
No examples provided.
server_info Server info ~18
Describe Rules MCP capabilities available in the current phase.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
validate_code Validate code ~158
Check a single code snippet against enforceable YAML rules under rules/ and return line-level issues (rule id, message, suggestion). Markdown skills are advisory via list_skills/get_context — they are not machine-validated here. For folders or multiple files, use the multi-file evaluation tool instead.
| Name | Type | Req | Description |
|---|---|---|---|
| code | string | yes | Source code to validate |
| filePath | string | – | Virtual or real path for glob/exception/language detection |
| language | string | – | Any language id/alias: typescript, python, java, go, rust, csharp, … Detected from filePath if omitted. |
| runExternal | boolean | – | Also run optional external checkers (tsc/complexity/secrets) with timeouts |
No output schema declared.
No examples provided.
validate_paths Evaluate files against rules ~184
PRIMARY tool when the user wants to evaluate, review, scan, audit, or check source files/folders for enforceable YAML rule violations (any languages: js, ts, py, java, go, …). Reads files from disk, applies matching rules under rules/ as ground truth, and returns every issue with file, line, ruleId, rule text, and suggestion. Skills under cursor skills/ are MD/MDC guidance (use list_skills / get_context), not validators. Prefer this over single-snippet validation whenever paths or folders are involved.
| Name | Type | Req | Description |
|---|---|---|---|
| cwd | string | – | Base directory for relative paths (default: process.cwd() / project root) |
| paths | array | yes | File or directory paths to evaluate (e.g. ['src/demo'] or ['src']) |
| recursive | boolean | – | When a path is a directory, scan recursively (default true) |
No output schema declared.
No examples provided.