AGENT SKILL

mcp-audit

Audit connected MCP servers for token overhead, redundancy, and security. Use when sessions feel slow or before adding new MCPs.

License 许可
MIT
最近更新
2026-11-14
Stars
★ 1
Forks
0

01 前言 Front Matter

name
mcp-audit
description
Audit connected MCP servers for token overhead, redundancy, and security. Use when sessions feel slow or before adding new MCPs.

03 SKILL.md 正文

MCP Audit

Analyze MCP server overhead and recommend cleanup.

Trigger

Use when:

  • Sessions feel slow or expensive
  • Adding a new MCP server
  • Context fills up quickly
  • Reviewing project configuration

Key Insight

Each MCP server adds ALL its tool descriptions to every API request. A server with 20 tools adds ~2K-4K tokens per request, regardless of whether you use those tools.

Audit Steps

Step 1: List Active Servers

Check all MCP configurations:

cat .claude/settings.json 2>/dev/null | grep -A 50 "mcpServers"
cat ~/.claude/settings.json 2>/dev/null | grep -A 50 "mcpServers"

Step 2: Count Tools Per Server

For each server, estimate token overhead:

  • 1-5 tools: ~200-500 tokens (low overhead)
  • 6-15 tools: ~500-1500 tokens (moderate)
  • 16-30 tools: ~1500-3000 tokens (high)
  • 30+ tools: ~3000+ tokens (excessive — consider tool filtering)

Step 3: Check Usage

Questions to ask:

  • Which servers were actually used this session?
  • Which servers haven't been used in 7+ days?
  • Are there servers with overlapping functionality?
  • Are there servers only needed for specific tasks?

Step 4: Recommend Actions

Disable servers that:

  • Haven't been used in 7+ days
  • Overlap with another active server
  • Are project-specific but you're in a different project

Keep servers that:

  • Are used every session (filesystem, git)
  • Provide unique capabilities needed for current work
  • Have low tool count (<5 tools)

Output

MCP AUDIT
  Active servers: [N]
  Total tools: [N]
  Estimated overhead: ~[N]K tokens per request

  Server Analysis:
    [name] — [N] tools, ~[N] tokens
      Status: KEEP / DISABLE / REVIEW
      Reason: [why]

  Recommendations:
    Disable: [list]
    Keep: [list]
    Review: [list]

  Projected savings: ~[N]K tokens per request (~$X.XX per session)

Thresholds

  • Total servers: <10 (ideal), 10-15 (monitor), >15 (reduce)
  • Total tools: <80 (ideal), 80-120 (monitor), >120 (reduce)
  • Per-server: <15 tools (ok), 15-30 (filter), >30 (split or disable)

Rules

  • Never disable servers without user confirmation
  • Estimate token savings for each recommendation
  • Consider task context — a server might be unused today but critical tomorrow
  • Check for disabledMcpjsonServers to avoid re-recommending already-disabled servers

04 同仓库更多 Skills

surfingalien
surfingalien/FinSurfing

portfolio-management

暂无简介

★ 1
surfingalien
surfingalien/FinSurfing

financial-analysis

暂无简介

★ 1
surfingalien
surfingalien/FinSurfing

tradingview-mcp

AI Trading Intelligence — live prices, 30+ technical indicators, backtesting (6 strategies), walk-forward overfitting detection, trade logs, equity curves, Reddit sentiment, news, and multi-market screener. Supports stocks, crypto, ETFs, indices, Turkish (BIST), and Egyptian (EGX) markets.

★ 1
surfingalien
surfingalien/FinSurfing

sales-engineer

Analyzes RFP/RFI responses for coverage gaps, builds competitive feature comparison matrices, and plans proof-of-concept (POC) engagements for pre-sales engineering. Use when responding to RFPs, bids, or proposal requests; comparing product features against competitors; planning or scoring a customer POC or sales demo; preparing a technical proposal; or performing win/loss competitor analysis. Handles tasks described as 'RFP response', 'bid response', 'proposal response', 'competitor comparison', 'feature matrix', 'POC planning', 'sales demo prep', or 'pre-sales engineering'.

★ 1
surfingalien
surfingalien/FinSurfing

revenue-operations

Analyzes sales pipeline health, revenue forecasting accuracy, and go-to-market efficiency metrics for SaaS revenue optimization. Use when analyzing sales pipeline coverage, forecasting revenue, evaluating go-to-market performance, reviewing sales metrics, assessing pipeline analysis, tracking forecast accuracy with MAPE, calculating GTM efficiency, or measuring sales efficiency and unit economics for SaaS teams.

★ 1
surfingalien
surfingalien/FinSurfing

customer-success-manager

Monitors customer health, predicts churn risk, and identifies expansion opportunities using weighted scoring models for SaaS customer success. Use when analyzing customer accounts, reviewing retention metrics, scoring at-risk customers, or when the user mentions churn, customer health scores, upsell opportunities, expansion revenue, retention analysis, or customer analytics. Runs three Python CLI tools to produce deterministic health scores, churn risk tiers, and prioritized expansion recommendations across Enterprise, Mid-Market, and SMB segments.

★ 1