@atlashub/smartstack-cli 1.4.1 → 1.5.1

package/templates/commands/efcore/db-status.md

@@ -6,13 +6,15 @@ model: haiku
 
 # EF Core Database Status
 
-Displays the complete status of EF Core migrations and database connection.
+Displays the complete status of EF Core migrations and database connection using **SmartStack MCP**.
 
 **Quick command, read-only, no modifications.**
 
+**INTEGRATION:** Uses `mcp__smartstack__check_migrations` for migration analysis.
+
 ---
 
-## STEP 1: Detect configuration
+## STEP 1: Detect Configuration
 
 ```bash
 # Check config files
@@ -36,7 +38,33 @@ PROJECT_NAME=$(basename "$CSPROJ" .csproj)
 
 ---
 
-## STEP 2: Test connection
+## STEP 2: Invoke MCP for Migration Status
+
+> **MCP INTEGRATION:** Get structured migration info from SmartStack MCP.
+
+```json
+{
+  "tool": "mcp__smartstack__check_migrations",
+  "parameters": {
+    "branch": "<current_branch>"
+  }
+}
+```
+
+**Claude instruction:** Call the MCP tool to get migration list:
+
+```
+CALL mcp__smartstack__check_migrations WITH:
+  - branch: {current_branch}
+
+EXTRACT from response:
+  - migrations[] -> list of all migrations
+  - conflicts[] -> any naming/ordering issues
+```
+
+---
+
+## STEP 3: Test Database Connection
 
 ```bash
 cd "$PROJECT_DIR"
@@ -44,30 +72,27 @@ cd "$PROJECT_DIR"
 # Test connection with EF Core
 CONNECTION_OK=$(dotnet ef database list 2>&1)
 if echo "$CONNECTION_OK" | grep -q "error\|Error\|failed"; then
-  CONNECTION_STATUS="❌ Failed"
+  CONNECTION_STATUS="FAILED"
   CONNECTION_ERROR="$CONNECTION_OK"
 else
-  CONNECTION_STATUS="✓ OK"
+  CONNECTION_STATUS="OK"
 fi
 ```
 
 ---
 
-## STEP 3: List migrations
+## STEP 4: Get Applied vs Pending
 
 ```bash
-# Migrations in code
+# Migrations in code vs applied
 CODE_MIGRATIONS=$(dotnet ef migrations list 2>/dev/null | grep -v "^Build" | grep -v "^$")
-TOTAL_MIGRATIONS=$(echo "$CODE_MIGRATIONS" | wc -l)
-
-# Applied vs pending migrations
-APPLIED=$(dotnet ef migrations list 2>/dev/null | grep "(Pending)" -v | grep -v "^Build" | wc -l)
+APPLIED=$(dotnet ef migrations list 2>/dev/null | grep -v "(Pending)" | grep -v "^Build" | wc -l)
 PENDING=$(dotnet ef migrations list 2>/dev/null | grep "(Pending)" | wc -l)
 ```
 
 ---
 
-## STEP 4: Display report
+## STEP 5: Display Report
 
 ```
 ================================================================================
@@ -77,130 +102,102 @@ PENDING=$(dotnet ef migrations list 2>/dev/null | grep "(Pending)" | wc -l)
 PROJECT
   Name:          {PROJECT_NAME}
   Config:        {CONFIG_USED}
-  DbContext:     {CONTEXT_NAME}
+  DbContext:     ApplicationDbContext
 
 CONNECTION
   Status:        {CONNECTION_STATUS}
   Server:        {SERVER}
   Database:      {DATABASE}
 
-MIGRATIONS
-  Total:         {TOTAL_MIGRATIONS}
-  Applied:       {APPLIED} ✓
-  Pending:       {PENDING} {⚠️ if > 0}
+MIGRATIONS (from MCP)
+  Total:         {migrations.length}
+  Applied:       {APPLIED}
+  Pending:       {PENDING} {if > 0: "-> /efcore:db-deploy"}
 
-================================================================================
-```
-
-**If pending migrations:**
+NAMING CONVENTION CHECK (from MCP)
+  Format:        {context}_v{version}_{sequence}_{Description}
+  Compliance:    {conflicts.filter(c => c.type === 'naming').length === 0 ? "OK" : "WARNINGS"}
 
+================================================================================
 ```
-PENDING MIGRATIONS
-────────────────────────────────────────────────────────────────────────────────
-  1. {MigrationName1}  (Pending)
-  2. {MigrationName2}  (Pending)
-────────────────────────────────────────────────────────────────────────────────
 
-→ Use /efcore:db-deploy to apply migrations
-```
+---
 
-**If connection error:**
+## STEP 5.1: Display Migration List (from MCP)
 
 ```
-⚠️  CONNECTION PROBLEM
-────────────────────────────────────────────────────────────────────────────────
-{CONNECTION_ERROR}
-────────────────────────────────────────────────────────────────────────────────
-
-CHECKS:
-  1. Is SQL Server running?
-  2. Is appsettings.Local.json configured?
-  3. Does the database exist?
-
-COMMANDS:
-  /efcore:db-reset   → Create/recreate database
-  /gitflow:10-start  → Configure appsettings.Local.json
+MIGRATIONS LIST
+--------------------------------------------------------------------------------
+  #  | Name                              | Context | Version | Sequence
+--------------------------------------------------------------------------------
+{for each migration in migrations}
+  {i} | {migration.name}                 | {migration.context} | {migration.version} | {migration.sequence}
+{end for}
+--------------------------------------------------------------------------------
 ```
 
 ---
 
-## STEP 4.5: Check "1 migration per feature" rule
+## STEP 5.2: Check "1 Migration per Feature" Rule
 
 ```bash
-# Current branch
 CURRENT_BRANCH=$(git branch --show-current)
 
 # Extract branch type
 if [[ "$CURRENT_BRANCH" == feature/* ]]; then
   BRANCH_TYPE="Feature"
-  BRANCH_NAME=$(echo "$CURRENT_BRANCH" | sed 's/feature\///' | sed 's/-/_/g')
 elif [[ "$CURRENT_BRANCH" == hotfix/* ]]; then
   BRANCH_TYPE="Hotfix"
-  BRANCH_NAME=$(echo "$CURRENT_BRANCH" | sed 's/hotfix\///' | sed 's/-/_/g')
-else
-  BRANCH_TYPE=""
-fi
-
-# If on a feature/hotfix, count migrations for this branch
-if [ -n "$BRANCH_TYPE" ]; then
-  # Search for migrations matching the branch pattern
-  BRANCH_MIGRATIONS=$(find "$MIGRATIONS_DIR" -name "*.cs" 2>/dev/null | grep -iE "${BRANCH_TYPE}.*${BRANCH_NAME}" | grep -v "Designer" | grep -v "Snapshot" | wc -l)
 fi
 ```
 
-**Display verification:**
+**Display:**
 
 ```
 "1 MIGRATION PER FEATURE" RULE
-────────────────────────────────────────────────────────────────────────────────
+--------------------------------------------------------------------------------
   Branch:       {CURRENT_BRANCH}
-  Migrations:   {BRANCH_MIGRATIONS} for this branch
-```
-
-**If BRANCH_MIGRATIONS > 1:**
-
-```
-  ⚠️  WARNING: {BRANCH_MIGRATIONS} migrations detected for this branch!
-      Rule: 1 migration only per feature/hotfix
-
-      RECOMMENDED ACTION:
-        /efcore:migration  → Recreate as single migration
-
-      Multiple migrations cause problems during merge.
-────────────────────────────────────────────────────────────────────────────────
+  Migrations:   {count for this branch}
+  Status:       {OK if count <= 1, else WARNING}
+--------------------------------------------------------------------------------
 ```
 
-**If BRANCH_MIGRATIONS == 1:**
+---
 
-```
-  ✓ Rule respected: 1 migration for this branch
-────────────────────────────────────────────────────────────────────────────────
-```
+## STEP 6: Show Warnings from MCP
 
-**If BRANCH_MIGRATIONS == 0 and pending modifications:**
+If MCP returned conflicts or warnings:
 
 ```
-  ○ No migrations for this branch
-    → Use /efcore:migration if you modified the model
-────────────────────────────────────────────────────────────────────────────────
+WARNINGS (from MCP analysis)
+--------------------------------------------------------------------------------
+{for each conflict in conflicts}
+  [{conflict.type}] {conflict.description}
+    Resolution: {conflict.resolution}
+{end for}
+--------------------------------------------------------------------------------
 ```
 
 ---
 
-## STEP 5: Additional info (optional)
+## STEP 7: Connection Error Handling
 
-```bash
-# Database size (if connection OK)
-DB_SIZE=$(sqlcmd -S "$SERVER" -E -Q "SELECT CAST(SUM(size * 8 / 1024.0) AS DECIMAL(10,2)) AS 'MB' FROM sys.master_files WHERE database_id = DB_ID('$DATABASE')" -h -1 2>/dev/null)
+**If connection error:**
 
-# Number of tables
-TABLE_COUNT=$(sqlcmd -S "$SERVER" -E -d "$DATABASE" -Q "SELECT COUNT(*) FROM INFORMATION_SCHEMA.TABLES WHERE TABLE_TYPE = 'BASE TABLE'" -h -1 2>/dev/null)
 ```
+CONNECTION PROBLEM
+--------------------------------------------------------------------------------
+{CONNECTION_ERROR}
+--------------------------------------------------------------------------------
 
-```
-STATISTICS
-  Size:          {DB_SIZE} MB
-  Tables:        {TABLE_COUNT}
+TROUBLESHOOTING:
+  1. Is SQL Server running?
+  2. Is appsettings.Local.json configured?
+  3. Does the database exist?
+
+COMMANDS:
+  /efcore:db-reset   -> Create/recreate database
+  /gitflow:10-start  -> Configure appsettings.Local.json
 ```
 
 ---
@@ -212,3 +209,18 @@ STATISTICS
 | `--verbose` | Display all migrations with details |
 | `--json` | JSON output for scripting |
 | `--context {name}` | Specify the DbContext |
+
+---
+
+## MCP Tool Reference
+
+**Tool:** `mcp__smartstack__check_migrations`
+
+**Used for:**
+- Getting structured list of migrations (name, context, version, sequence)
+- Detecting naming convention violations
+- Checking migration order
+
+**Response fields used:**
+- `migrations[]` - List of all migrations with parsed metadata
+- `conflicts[]` - Any issues detected (naming, order)

package/templates/commands/efcore/migration.md

@@ -236,24 +236,36 @@ AskUserQuestion({
 ## STEP 6: Generate Migration Name
 
 ```bash
-# Pattern: {BranchType}_{Version}_{BranchName}_{Description}
-# Example: Feature_1_2_0_UserAuth_AddRolesTable
+# Pattern: {context}_v{version}_{sequence}_{Description}
+# Example: core_v1.0.0_001_AddUserRoles
+# This format is aligned with SmartStack MCP conventions
 
-MIGRATION_NAME="${BRANCH_TYPE}_${VERSION_CLEAN}_${BRANCH_NAME}_${DESCRIPTION}"
+# Determine context based on branch type
+if [[ "$BRANCH_TYPE" == "Feature" ]] || [[ "$BRANCH_TYPE" == "Hotfix" ]]; then
+  CONTEXT="core"  # Default context for feature/hotfix
+else
+  CONTEXT="core"
+fi
+
+# Get next sequence number
+EXISTING_COUNT=$(find "$MIGRATIONS_DIR" -name "${CONTEXT}_v${VERSION}*.cs" | grep -v "Designer" | grep -v "Snapshot" | wc -l)
+SEQUENCE=$(printf "%03d" $((EXISTING_COUNT + 1)))
+
+MIGRATION_NAME="${CONTEXT}_v${VERSION}_${SEQUENCE}_${DESCRIPTION}"
 
-# Clean the name (no spaces, no special characters)
-MIGRATION_NAME=$(echo "$MIGRATION_NAME" | sed 's/[^a-zA-Z0-9_]//g')
+# Clean the name (no spaces, no special characters except underscore and dot)
+MIGRATION_NAME=$(echo "$MIGRATION_NAME" | sed 's/[^a-zA-Z0-9_.]//g')
 
 echo "Migration name: $MIGRATION_NAME"
 ```
 
-**Generated name examples:**
+**Generated name examples (aligned with MCP):**
 
-| Branch | Version | Description | Final Name |
-|--------|---------|-------------|------------|
-| feature/user-auth | 1.2.0 | AddRolesTable | Feature_1_2_0_UserAuth_AddRolesTable |
-| hotfix/login-fix | 1.2.1 | FixNullEmail | Hotfix_1_2_1_LoginFix_FixNullEmail |
-| release/v1.3.0 | 1.3.0 | Initial | Release_1_3_0_Initial |
+| Context | Version | Sequence | Description | Final Name |
+|---------|---------|----------|-------------|------------|
+| core | 1.2.0 | 001 | AddUserRoles | core_v1.2.0_001_AddUserRoles |
+| core | 1.2.0 | 002 | AddPermissions | core_v1.2.0_002_AddPermissions |
+| extensions | 1.3.0 | 001 | AddCustomFields | extensions_v1.3.0_001_AddCustomFields |
 
 ---
 

package/templates/commands/efcore/scan.md

@@ -6,27 +6,22 @@ model: sonnet
 
 # EF Core Scan - Cross-Branch Migration Scanner
 
-Scans all active branches to detect migrations and analyze conflict risks.
+Scans all active branches to detect migrations and analyze conflict risks using **SmartStack MCP**.
 
 **USAGE:** Before creating a migration or before a merge to check the status of other branches.
 
 **SECURITY:** Read-only - no modifications.
 
+**INTEGRATION:** Uses `mcp__smartstack__check_migrations` for each branch comparison.
+
 ---
 
-## STEP 1: List active worktrees
+## STEP 1: Detect Active Worktrees
 
 ```bash
-# Check that worktrees exist
-WORKTREE_BASE=$(git config --get gitflow.worktrees.basePath 2>/dev/null || echo "../worktrees")
-
-if [ ! -d "$WORKTREE_BASE" ]; then
-  echo "Worktrees structure not found: $WORKTREE_BASE"
-  echo "Run /gitflow:1-init to create structure"
-  exit 1
-fi
+# List all git worktrees
+WORKTREES=$(git worktree list --porcelain | grep "^worktree" | cut -d' ' -f2)
 
-# List all worktrees
 echo "DETECTED WORKTREES"
 echo "=================="
 git worktree list
@@ -35,142 +30,115 @@ echo ""
 
 ---
 
-## STEP 2: Scan migrations per branch
+## STEP 2: Invoke MCP for Each Branch
 
-```bash
-# For each worktree
-for worktree in $(git worktree list --porcelain | grep "^worktree" | cut -d' ' -f2); do
-  BRANCH=$(git -C "$worktree" branch --show-current 2>/dev/null)
-
-  if [ -z "$BRANCH" ]; then
-    continue
-  fi
-
-  # Find Migrations folder
-  MIGRATIONS_DIR=$(find "$worktree" -type d -name "Migrations" 2>/dev/null | head -1)
-
-  if [ -n "$MIGRATIONS_DIR" ]; then
-    # Count migrations
-    MIGRATION_COUNT=$(find "$MIGRATIONS_DIR" -name "*.cs" | grep -v "Designer" | grep -v "Snapshot" | wc -l)
-
-    # ModelSnapshot hash
-    SNAPSHOT=$(find "$MIGRATIONS_DIR" -name "*ModelSnapshot.cs" 2>/dev/null | head -1)
-    if [ -n "$SNAPSHOT" ]; then
-      SNAPSHOT_HASH=$(md5sum "$SNAPSHOT" 2>/dev/null | cut -d' ' -f1 | head -c 8)
-    else
-      SNAPSHOT_HASH="N/A"
-    fi
+> **MCP INTEGRATION:** For each active branch, call the MCP to get structured analysis.
 
-    echo "$BRANCH | $MIGRATION_COUNT migrations | Snapshot: $SNAPSHOT_HASH"
-  fi
-done
-```
+For each worktree/branch, call:
 
----
+```json
+{
+  "tool": "mcp__smartstack__check_migrations",
+  "parameters": {
+    "branch": "<branch_name>",
+    "compareBranch": "develop"
+  }
+}
+```
 
-## STEP 3: Compare with develop
+**Claude instruction:** Loop through detected branches and invoke MCP:
 
-```bash
-# Get develop's ModelSnapshot hash
-DEVELOP_WORKTREE="$WORKTREE_BASE/develop"
-
-if [ -d "$DEVELOP_WORKTREE" ]; then
-  DEVELOP_SNAPSHOT=$(find "$DEVELOP_WORKTREE" -name "*ModelSnapshot.cs" 2>/dev/null | head -1)
-
-  if [ -n "$DEVELOP_SNAPSHOT" ]; then
-    DEVELOP_HASH=$(md5sum "$DEVELOP_SNAPSHOT" 2>/dev/null | cut -d' ' -f1)
-    echo ""
-    echo "REFERENCE: develop ModelSnapshot = ${DEVELOP_HASH:0:8}"
-  fi
-fi
+```
+FOR each branch in [feature/*, hotfix/*, release/*]:
+  CALL mcp__smartstack__check_migrations WITH:
+    - branch: {branch}
+    - compareBranch: "develop"
+  STORE result in BRANCH_RESULTS[branch]
 ```
 
 ---
 
-## STEP 4: Analyze conflict risks
+## STEP 3: Aggregate Results
 
-```bash
-echo ""
-echo "RISK ANALYSIS"
-echo "==================="
-
-# Compare each branch with develop
-for worktree in $(git worktree list --porcelain | grep "^worktree" | cut -d' ' -f2); do
-  BRANCH=$(git -C "$worktree" branch --show-current 2>/dev/null)
-
-  if [ "$BRANCH" = "develop" ] || [ "$BRANCH" = "main" ]; then
-    continue
-  fi
-
-  SNAPSHOT=$(find "$worktree" -name "*ModelSnapshot.cs" 2>/dev/null | head -1)
-
-  if [ -n "$SNAPSHOT" ] && [ -n "$DEVELOP_SNAPSHOT" ]; then
-    # Compare snapshots
-    if diff -q "$SNAPSHOT" "$DEVELOP_SNAPSHOT" > /dev/null 2>&1; then
-      RISK="NONE"
-    else
-      # Analyze differences
-      DIFF_LINES=$(diff "$DEVELOP_SNAPSHOT" "$SNAPSHOT" 2>/dev/null | wc -l)
-
-      if [ "$DIFF_LINES" -lt 50 ]; then
-        RISK="LOW"
-      elif [ "$DIFF_LINES" -lt 200 ]; then
-        RISK="MEDIUM"
-      else
-        RISK="HIGH"
-      fi
-    fi
+Parse MCP responses to build summary:
 
-    echo "$BRANCH: $RISK"
-  fi
-done
+```typescript
+interface ScanSummary {
+  branches: BranchScan[];
+  totalMigrations: number;
+  conflictCount: number;
+  recommendedMergeOrder: string[];
+}
+
+interface BranchScan {
+  name: string;
+  migrationCount: number;
+  riskLevel: 'NONE' | 'LOW' | 'MEDIUM' | 'HIGH';
+  conflicts: MigrationConflict[];
+}
 ```
 
+**Risk Level Calculation:**
+
+| Condition | Risk Level |
+|-----------|------------|
+| Snapshot identical to develop | NONE |
+| Different tables modified | LOW |
+| FK to same tables | MEDIUM |
+| Same tables/columns modified | HIGH |
+
 ---
 
-## STEP 5: Recommend merge order
+## STEP 4: Calculate Merge Order
+
+Based on conflict analysis, recommend merge order:
 
-```bash
-echo ""
-echo "RECOMMENDED MERGE ORDER"
-echo "========================="
-echo "1. Branches with RISK=NONE (independent)"
-echo "2. Branches with RISK=LOW (minor modifications)"
-echo "3. Branches with RISK=MEDIUM (order matters)"
-echo "4. Branches with RISK=HIGH (rebase required before merge)"
+```
+1. Branches with RISK=NONE (can merge immediately)
+2. Branches with RISK=LOW (minor modifications, safe to merge)
+3. Branches with RISK=MEDIUM (order matters, merge carefully)
+4. Branches with RISK=HIGH (rebase required before merge)
 ```
 
 ---
 
-## Output Format
+## STEP 5: Display Report
 
 ```
 ================================================================================
-                    EF CORE CROSS-BRANCH SCAN
+                    EF CORE CROSS-BRANCH SCAN (via MCP)
 ================================================================================
 
-DETECTED WORKTREES (5)
+DETECTED WORKTREES ({count})
   main/                    [main]
-  develop/                 [develop]
+  develop/                 [develop]         <- REFERENCE
   features/user-auth/      [feature/user-auth]
   features/add-products/   [feature/add-products]
   hotfixes/login-fix/      [hotfix/login-fix]
 
 MIGRATIONS PER BRANCH
-  develop               | 12 migrations | Snapshot: a1b2c3d4 (REFERENCE)
-  feature/user-auth     | 13 migrations | Snapshot: e5f6g7h8
-  feature/add-products  | 13 migrations | Snapshot: i9j0k1l2
-  hotfix/login-fix      | 12 migrations | Snapshot: a1b2c3d4
+--------------------------------------------------------------------------------
+  Branch                  | Migrations | Snapshot   | vs Develop
+--------------------------------------------------------------------------------
+  develop                 | 12         | a1b2c3d4   | REFERENCE
+  feature/user-auth       | 13         | e5f6g7h8   | +1 migration
+  feature/add-products    | 13         | i9j0k1l2   | +1 migration
+  hotfix/login-fix        | 12         | a1b2c3d4   | identical
+--------------------------------------------------------------------------------
 
 RISK ANALYSIS
-  feature/user-auth     : LOW      (different table)
-  feature/add-products  : MEDIUM   (FK to same table)
-  hotfix/login-fix      : NONE     (snapshot = develop)
+--------------------------------------------------------------------------------
+  feature/user-auth       : LOW      (different tables)
+  feature/add-products    : MEDIUM   (FK to same table)
+  hotfix/login-fix        : NONE     (snapshot = develop)
+--------------------------------------------------------------------------------
 
 RECOMMENDED MERGE ORDER
-  1. hotfix/login-fix      (NONE - direct merge)
-  2. feature/user-auth     (LOW - merge OK)
-  3. feature/add-products  (MEDIUM - after user-auth)
+--------------------------------------------------------------------------------
+  1. hotfix/login-fix      -> NONE   (direct merge OK)
+  2. feature/user-auth     -> LOW    (merge OK)
+  3. feature/add-products  -> MEDIUM (after user-auth, then rebase)
+--------------------------------------------------------------------------------
 
 ================================================================================
 ```
@@ -181,10 +149,10 @@ RECOMMENDED MERGE ORDER
 
 | Option | Description |
 |--------|-------------|
-| `--json` | JSON output for CI/CD |
-| `--branch <name>` | Scan a specific branch |
-| `--verbose` | Display difference details |
-| `--no-recommend` | Don't display recommendations |
+| `--json` | Output raw JSON for CI/CD |
+| `--branch <name>` | Scan specific branch only |
+| `--verbose` | Show detailed MCP responses |
+| `--no-recommend` | Skip merge order recommendations |
 
 ---
 
@@ -194,9 +162,37 @@ RECOMMENDED MERGE ORDER
 # GitHub Actions
 - name: Scan EF Core migrations
   run: |
+    # Claude Code will use MCP internally
     OUTPUT=$(claude-code "/efcore:scan --json")
-    CONFLICTS=$(echo $OUTPUT | jq '.risks[] | select(.level == "HIGH") | length')
-    if [ "$CONFLICTS" -gt 0 ]; then
-      echo "::warning::High risk migration conflicts detected"
+    HIGH_RISK=$(echo $OUTPUT | jq '[.branches[] | select(.riskLevel == "HIGH")] | length')
+    if [ "$HIGH_RISK" -gt 0 ]; then
+      echo "::warning::$HIGH_RISK branches have HIGH risk migration conflicts"
     fi
 ```
+
+---
+
+## MCP Tool Reference
+
+**Tool:** `mcp__smartstack__check_migrations`
+
+**Description:** Analyze EF Core migrations for conflicts, ordering issues, and ModelSnapshot discrepancies between branches
+
+**Parameters:**
+
+| Parameter | Type | Description |
+|-----------|------|-------------|
+| `projectPath` | string | EF Core project path (default: auto-detect) |
+| `branch` | string | Git branch to check (default: current) |
+| `compareBranch` | string | Branch to compare against |
+
+**Response:** `MigrationCheckResult` with `hasConflicts`, `migrations[]`, `conflicts[]`, `suggestions[]`
+
+---
+
+## Why MCP Integration?
+
+1. **Consistency:** Identical analysis logic for single branch (`/efcore:conflicts`) and multi-branch (`/efcore:scan`)
+2. **Accuracy:** Structured parsing instead of regex on ModelSnapshot files
+3. **Extensibility:** New conflict types added in MCP benefit all commands
+4. **Caching:** MCP can cache results for faster subsequent scans