skills.rest
surfingalien
surfingalienCOMMUNITY
Explore all skills by this author →
GitHub

mcp-audit

Audit MCP server configurations for token overhead, redundancy, and usage patterns.

1|Updated May 6, 2026
Search Tags:#context management#claude code#audit#mcp#cost reduction#token optimization#server configuration
One-click install
npx skills add https://github.com/surfingalien/FinSurfing --skill mcp-audit-surfingalien
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: mcp-audit
Source: https://github.com/surfingalien/FinSurfing/tree/main/.claude/skills/mcp-audit
Command: npx skills add https://github.com/surfingalien/FinSurfing --skill mcp-audit-surfingalien

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Every connected MCP server injects all of its tool descriptions into each API request, silently inflating token costs and slowing sessions. This Skill identifies which servers are worth keeping and which are draining context budget. ## Core Features & Use Cases - Token Overhead Estimation: Counts tools per server and estimates per-request token cost using defined thresholds. - Usage-Based Recommendations: Flags servers unused for 7+ days, overlapping in functionality, or mismatched with the current project. - Structured Audit Report: Produces a KEEP / DISABLE / REVIEW breakdown with projected token and cost savings. - Use Case: Before adding a new MCP server, run an audit to confirm total tool count stays under 80 and avoid compounding context overhead. ## Quick Start Audit my active MCP servers and tell me which ones to disable to reduce token overhead.

Frequently Asked Questions about mcp-audit

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

FAQPage Schema
How do I reduce token usage from MCP servers?▼

Audit each connected MCP server and disable any unused for 7+ days or overlapping with another server. Each server adds all its tool descriptions to every request, so removing a 20-tool server saves roughly 2K-4K tokens per call.

How many MCP servers should I have connected at once?▼

Keep total servers under 10 and total tools under 80 for ideal performance. Between 10-15 servers or 80-120 tools warrants monitoring, and anything above that should be reduced or filtered.

Why do MCP servers slow down Claude sessions?▼

Every MCP server injects all of its tool descriptions into each API request, regardless of whether those tools are used. A server with 30+ tools can add over 3000 tokens per request, consuming context window and increasing cost.

Where are MCP server configurations stored?▼

MCP servers are configured in the mcpServers section of .claude/settings.json at the project level and ~/.claude/settings.json at the user level. The audit checks both locations to build a complete server inventory.

Will the audit disable MCP servers automatically?▼

No, the audit only recommends actions and never disables servers without explicit user confirmation. It also checks disabledMcpjsonServers to avoid re-recommending servers you have already turned off.

Related Skills

Explore More Software Engineering Skills→
chanhee-kangchanhee-kang
2

mcp-setup

Configure MCP servers for Gemini CLI via the claude mcp add workflow.

Community
Advanced
rohitg00rohitg00
2.8k

mcp-audit

Audit connected MCP servers for token overhead, redundancy, and security risks.

Community
Intermediate
truefoundrytruefoundry
13

truefoundry-ai-monitoring

Query AI Gateway spans API for traces, costs, latency, errors, and token usage.

Official
Advanced
jleechanorgjleechanorg

native-mcp

Discover and register MCP server tools into Hermes Agent toolsets.

Official
Advanced