audit-mcp

Validate MCP server configurations and report per-server health statuses.

Updated Jan 28, 2026
One-click install
npx skills add https://github.com/mesca/claude-plugins --skill audit-mcp
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: audit-mcp
Source: https://github.com/mesca/claude-plugins/tree/main/plugins/wf/skills/audit-mcp
Command: npx skills add https://github.com/mesca/claude-plugins --skill audit-mcp

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

MCP server configurations can be inconsistent or misconfigured, leading to undetected issues during deployment or operation. This skill automates verification to ensure MCP servers are properly configured and reachable.

Core Features & Use Cases

  • Discover and read MCP configuration files such as .mcp.json at the project root or within plugin directories.
  • Validate JSON syntax, enumerate all configured MCP servers, and categorize their types (stdio, http, sse, etc.).
  • Run lightweight health checks against each server and report per-server status to help diagnose connectivity and setup issues.

Quick Start

Run this skill against your project to verify all configured MCP servers are reachable and healthy.

Frequently Asked Questions about audit-mcp

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

FAQPage Schema
How do I check if my MCP servers are configured correctly?

You can verify MCP server configuration by running a health check that reads .mcp.json files at the project root or plugin directories. This process validates JSON syntax, enumerates servers, and reports per-server status.

What is an MCP server health check?

An MCP server health check is a read-only test that verifies each configured server is reachable and operating correctly. It categorizes server types like stdio, http, and sse to diagnose connectivity and setup issues.

Can I test MCP server reachability for different server types?

Yes, you can test MCP server reachability for various types including stdio, http, and sse. The verification process enumerates all configured servers from .mcp.json, categorizes their types, and runs lightweight health checks against each one.

Why are my MCP servers unreachable during deployment?

MCP servers might be unreachable due to inconsistent or misconfigured settings in .mcp.json files. Running an automated health check identifies these setup issues by testing server reachability and basic operation before deployment.

Does MCP server verification work with config files in plugin directories?

Yes, MCP server verification works with config files in plugin directories as well as the project root. It reads .mcp.json configurations from both locations to discover, validate, and test all configured servers.