mcp-audit
Audit the configured MCP servers (user + project scope) via the Agent Monitor Config Explorer API: transport (stdio vs http), command/args and env variable names, headers, and the source file each definition came from. Reads /api/cc-config/mcp. Use when reviewing MCP integrations for hygiene, duplication, or unexpected transports.
npx skills add hoangsonww/Claude-Code-Agent-Monitor --skill mcp-audit --agent claude-code
Same command for any agent — swap --agent for codex, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
# MCP Audit Inventory and audit every Model Context Protocol server the user has configured — both user-scope and project-scope — read through the Agent Monitor dashboard at `http://localhost:4820`. ## Input The user provides: **$ARGUMENTS** This may be: - empty — audit all MCP servers (default). - a server name fragment — focus on matching servers. - "stdio" / "http" — restrict to one transport kind. ## Data Sources | Endpoint | Returns | |----------|---------| | `GET /api/cc-config/mcp` | `{ user:[…], projectScoped:[…] }`. Each server: `{ name, source, kind }` where `kind` is `stdio` (with `command, args, envNames`), `http` (with `url, headers`), or `unknown`. `source` names the file the definition came from (e.g. `~/.claude.json (top-level)`, `~/.claude.json (projects[<root>])`, `~/.claude/settings.json`) | ## Report Sections ### 1. Server inventory List every server from `user` and `projectScoped`. For each show `name`, `source`, `kind`, and the transport detail: - **stdio** — the `command`, its `args`, and the `envNames` (names only — values are not exposed by the API). - **http** — the `url` and the `headers` key names (values not exposed). - **unknown** — a definition the se
- Input
- Data Sources
- Report Sections
- 1. Server inventory
- 2. Scope split & duplication
- 3. Hygiene flags
- Output
What does the mcp-audit skill do?
Audit the configured MCP servers (user + project scope) via the Agent Monitor Config Explorer API: transport (stdio vs http), command/args and env variable names, headers, and the source file each definition came from. Reads /api/cc-config/mcp. Use when reviewing MCP integrations for hygiene, duplication, or unexpected transports.
How do I install it?
Run `npx skills add hoangsonww/Claude-Code-Agent-Monitor --skill mcp-audit --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.
Where does this skill come from?
From hoangsonww/Claude-Code-Agent-Monitor, a repository with 869 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.
Is a popular skill a good skill?
Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.