mcp-graveyard

Audit which MCP server tools your Claude Code sessions actually invoke. Use when the user wants to find dead MCP servers (configured but never called), hallucinated MCP tool calls, or per-project MCP

SKILL.md

GitHub

mcp-graveyard

CLI that audits MCP server tool usage. Server-first table grouped into ACTIVE / DEAD / HALLUCINATED / MISSING buckets.

How to invoke

Run via npx mcp-graveyard@latest <subcommand> [flags] — no install needed.

Subcommands

  • audit (default) — classify every server. Flags: --days N, --only <bucket>, --tools <server> (drill-in), --json, --claude-dir <path>.
  • prune — print removal plan. --apply to execute (with auto-backup of removed config to a timestamped file).
  • suggest — actionable triage for unused/hallucinated.
  • projects — per-project breakdown.

Decision flow

  • "which MCP servers do I not use?" → npx mcp-graveyard@latest
  • "clean up MCP config" → prune, then --apply
  • "MCP tool didn't work" → suggest
  • per-project breakdown → projects

After running, print output verbatim. Do not summarize unless the user asks.

Related in security

git-workflow

Git workflow guidance for commits, branches, and pull requests

by agno-agi
37,144

clerk-observability

Implement monitoring, logging, and observability for Clerk authentication. Use when setting up monitoring, debugging aut...

by jeremylongshore
1,061

juicebox-migration-deep-dive

Advanced Juicebox data migration strategies. Use when migrating from other recruiting platforms, performing bulk data im...

by jeremylongshore
1,061