mcp-server-audit

Audit MCP server registrations across user, project, and plugin scopes.

3|Updated Apr 1, 2026
One-click install
npx skills add https://github.com/anthril/official-claude-plugins --skill mcp-server-audit
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: mcp-server-audit
Source: https://github.com/anthril/official-claude-plugins/tree/main/plugins/resource-manager/skills/mcp-server-audit
Command: npx skills add https://github.com/anthril/official-claude-plugins --skill mcp-server-audit

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

Audit MCP server registrations across user, project, and plugin scopes to identify always-on instances and duplicates, helping you reduce wasted resources and confusion.

Core Features & Use Cases

  • Audit and align MCP server registrations across user, project, and plugin scopes.
  • Identify always-on servers and duplicates across scopes and generate actionable disable or scope-down recommendations.
  • Generate a markdown report summarizing live processes, memory usage, and config paths for remediation.

Quick Start

Run the MCP Server Audit to generate a live report of current MCP registrations and duplicates.

Frequently Asked Questions about mcp-server-audit

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I audit MCP server registrations across multiple scopes?

Audit MCP server registrations across user, project, and plugin scopes to identify always-on instances and duplicates using read-only access to MCP configs. It compiles a markdown report summarizing live processes and memory usage.

Why do I have duplicate MCP servers running in my Claude Code environment?

Duplicate MCP servers occur when sessions spawn instances per user, per project, or via plugins. Auditing cross-scope configurations detects these active duplicates and proposes precise remediation steps.

What's the best way to identify always-on MCP server instances?

Identify always-on MCP server instances by inspecting live processes and config paths across user, project, and plugin scopes. The audit generates actionable disable or scope-down recommendations to cut wasted resources.

Do I need Python to inspect MCP server configs for resource waste?

Yes, auditing MCP server configs requires Python 3.8+ and Bash-based tooling with read-only access. It detects active servers across scopes and outputs a markdown report for remediation.

How to remediate cross-scope MCP server conflicts in Claude Code?

Remediate cross-scope MCP server conflicts by running an audit to surface always-on instances and duplicates. The generated markdown report provides precise disable or scope-down steps to resolve conflicts.

Can I check MCP server memory usage without modifying active configs?

Check MCP server memory usage safely using read-only config analysis. The audit scans user, project, and plugin scopes to compile live process data and memory usage into a markdown report without modifying configs.