Kjell Tore Guttormsen
3b034d9266
Hver /security <cmd> som produserer rapport printer nå en klikkbar file://-lenke til en self-contained HTML-versjon. Levert over fem sesjoner; sesjon 5 wirer de 14 resterende skill-filene + slipper v7.7.0 (versjonsbump + docs). Sesjon-historikk: - Sesjon 1 (0dc7ff4) — playground katalog list-view + builder-pane med copy-knapp på alle 18 rapporter - Sesjon 2 (86d6ecd) — playground prosjekt-surface opprydding (stub-screen + topbar-splitt) - Sesjon 3 (fa5fb48) — extract 18 inline parsers + 18 inline renderers fra playground til canonical ESM-modul scripts/lib/report-renderers.mjs (playground beholder bit-identisk inline-kopi siden ESM import ikke fungerer fra file://) - Sesjon 4 (db80854) — ny zero-dep CLI scripts/render-report.mjs (stdin/file/stdout-modus, kebab→camel commandId-routing, ~140 KB self-contained HTML med 6 inlined DS-stylesheets + lokal .report-table, absolutte file://-paths for Ghostty cmd-click). 4 skills wired: scan, audit, posture, deep-scan. - Sesjon 5 (denne) — 14 resterende skills wired: plugin-audit, mcp-audit, mcp-inspect, ide-scan, supply-check, dashboard, pre-deploy, diff, watch, registry, clean, harden, threat-model, red-team. Hver skill-fil har nå en HTML Report-step som instruerer Claude å skrive markdown verbatim, kjøre CLI, og appende klikkbar file://-lenke til respons. Release-arbeid: - Versjonsbump v7.6.1 → v7.7.0 i 6 plugin-filer + 2 rot-filer (package.json, .claude-plugin/plugin.json, README badge, CLAUDE.md header + state-seksjon, docs/version-history.md, plugin Recent versions- tabell, rot README plugin-entry, rot CLAUDE.md plugin-katalog) - CHANGELOG [7.7.0] med full historikk fra sesjon 1-5 - docs/version-history.md v7.7.0-seksjon Verifisert: - 18/18 commandIds i CLI gir > 138 KB self-contained HTML - 1819/1820 tester grønne (pre-compact-scan-perf-flake fyrte under last, passerer i isolasjon på 1582 ms — pre-eksisterende, defer til v7.7.x) - 18/18 skill-filer har HTML Report-step - Ingen kildefil-treff på 7.6.1 utenfor historiske changelog/version- history/README releases-tabell Ingen scanner- eller hook-atferdsendringer — purely additive surface. Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>
67 lines
3 KiB
Markdown
67 lines
3 KiB
Markdown
---
|
|
name: security:mcp-audit
|
|
description: Audit all installed MCP server configurations for security risks, trust verification, and permission analysis
|
|
allowed-tools: Read, Glob, Grep, Agent, Bash
|
|
model: sonnet
|
|
---
|
|
|
|
# /security mcp-audit [--live]
|
|
|
|
Full MCP server security audit — project-level and global. Add `--live` to also connect to running servers and scan live tool descriptions.
|
|
|
|
## Step 0: Parse Flags
|
|
|
|
If `$ARGUMENTS` contains `--live`, strip it and set `run_live_inspection = true`.
|
|
|
|
## Step 1: Discovery
|
|
|
|
Read MCP configs from: `.mcp.json`, `.claude/settings.json`, `claude_desktop_config.json`, `~/.claude/settings.json`, `~/.claude/mcp.json`, `~/.config/claude/mcp.json`.
|
|
|
|
For each server extract: name, transport (stdio/sse), command+args or URL, env var names (redact values), source origin. Report total count.
|
|
|
|
## Step 2: Scan
|
|
|
|
Spawn `subagent_type: "llm-security:mcp-scanner-agent"`, `model: "sonnet"`:
|
|
|
|
> Full MCP audit. Read: \<plugin-root\>/knowledge/mcp-threat-patterns.md
|
|
> Execute all 5 phases per server (tool descriptions, source code, dependencies, config, rug pull detection).
|
|
> Servers: \<discovered server list with name, type, command, source, env vars\>
|
|
> Return per-server trust rating + findings.
|
|
|
|
## Step 3: Report
|
|
|
|
Output: MCP Landscape Summary table (server, source, transport, trust rating, finding counts).
|
|
Overall risk: Low (all trusted) / Medium (cautious+high) / High (untrusted) / Critical (dangerous).
|
|
Group servers: Keep / Review / Remove immediately.
|
|
|
|
## Step 4: Live Inspection (only if `--live`)
|
|
|
|
Run: `node <plugin-root>/scanners/mcp-live-inspect.mjs "<cwd>"`
|
|
|
|
Parse JSON output. Append a **Live Inspection Results** section:
|
|
|
|
- Contact status per server (contacted / timed-out / skipped / failed)
|
|
- Live injection findings (sorted critical → info)
|
|
- Tool shadowing across servers
|
|
|
|
**Cross-reference escalation:** If a server was rated "Untrusted" or "Dangerous" in Step 2 AND has live injection findings → escalate to CRITICAL priority in the final report and highlight as "Confirmed active threat (static + live)".
|
|
|
|
## Step 5: HTML Report
|
|
|
|
After producing the markdown MCP audit report (Step 3 + optional Step 4 Live Inspection):
|
|
|
|
1. Compute a temp markdown path:
|
|
```bash
|
|
node -p "require('path').join(require('os').tmpdir(), 'sec-mcp-audit-' + Date.now() + '.md')"
|
|
```
|
|
2. Use the Write tool to save the **entire markdown report you just produced** (MCP Landscape Summary + per-server analysis + Live Inspection Results section if `--live` + Keep/Review/Remove groupings + overall risk) to that temp path. Verbatim.
|
|
3. Run the renderer:
|
|
```bash
|
|
node <plugin-root>/scripts/render-report.mjs mcp-audit --in "<temp-md-path>"
|
|
```
|
|
The CLI writes `reports/mcp-audit-<YYYYMMDD-HHmmss>.html` relative to CWD and prints `file:///abs/path.html` on stdout.
|
|
4. Append to your response (markdown link, no bare URL):
|
|
|
|
> **HTML-rapport:** [Åpne i nettleser](file:///abs/path.html)
|
|
|
|
If the CLI exits non-zero, mention the error but do not block — the markdown report above is the primary deliverable.
|