Audit MCP Command

Audit MCP server configurations for quality, compliance, and security.

Step 0: Initialize Audit Environment

Get the current UTC date, capture the project root path, ensure the temp directory exists, and clean up any stale audit files if the user confirms. Invoke the claude-ecosystem:mcp-integration skill to load authoritative MCP configuration guidance.

What Gets Audited

This command audits MCP server configurations from multiple sources:

• Project scope: .mcp.json in project root (version-controlled, team-shared)
• User (Global) scope: ~/.claude.json with root-level mcpServers key
• Local scope: .claude/settings.local.json with mcpServers key if present
• Plugin scope: .mcp.json files within plugin directories
• Enterprise scope: managed-mcp.json in system directories

For each configuration, validate JSON structure, server fields, transport types, authentication, environment variable usage, and security (no exposed credentials).