audit-mcp-health

Cross-reference configured MCP servers against the live deferred tool list.

2|Updated Dec 20, 2020
One-click install
npx skills add https://github.com/buvis/home --skill audit-mcp-health
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: audit-mcp-health
Source: https://github.com/buvis/home/tree/main/.claude/skills/audit-mcp-health
Command: npx skills add https://github.com/buvis/home --skill audit-mcp-health

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Cross-reference configured MCP servers against the live deferred tool list to detect disconnected, unused, or bloated servers and provide actionable findings.

Core Features & Use Cases

  • Cross-reference configured MCP servers with the live deferred tool list to identify connectivity status and usage.
  • Detect duplicates across global and project configs and generate a structured health report.
  • Use the findings to guide cleanup of unused or stale MCP servers and improve operational hygiene.

Quick Start

Audit MCP servers against the live deferred tool list and generate a health report.

Frequently Asked Questions about audit-mcp-health

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

FAQPage Schema
How do I check MCP server connectivity and find disconnected servers?

To check MCP server connectivity, cross-reference configured servers against the live deferred tool list. This audit identifies disconnected, unused, or bloated servers by scanning for mcp__ prefixes and parsing session history.

Why does my MCP server show as unused in Claude workflows?

An MCP server shows as unused when configured servers do not match the live deferred tool list. The audit detects this by parsing observed MCP tool invocations from JSONL session history and cross-referencing global and project configs.

How do I audit MCP servers for duplicate configurations across global and project settings?

Audit MCP servers for duplicates by reading ~/.claude/settings.json and project settings to locate mcpServers. The process cross-references these configs to detect duplicates and generates a structured health report.

Can I count available tools per MCP server to identify bloated configurations?

You can count tools per MCP server by scanning the deferred tool list for mcp__ prefixes. This audit counts tools per server across local and global MCP configurations to identify bloated or stale servers.

What is the best way to clean up stale MCP servers and improve operational hygiene?

The best way to clean up stale MCP servers is generating a health report that cross-references configured servers with the live deferred tool list. Use these findings to remove disconnected or unused servers and improve operational hygiene.

Does MCP server health auditing work with both local and global Claude configurations?

MCP server health auditing works with both local and global Claude configurations. It analyzes ~/.claude/settings.json and project settings to locate mcpServers, cross-referencing both config levels to identify connectivity and usage issues.