/ Verzeichnis / Playground / Cisco MCP Scanner
● Offiziell cisco-ai-defense ⚡ Sofort

Cisco MCP Scanner

von cisco-ai-defense · cisco-ai-defense/mcp-scanner

Run a battery of prompt-injection, tool-shadowing, and exfiltration tests against any MCP server before you trust it in production.

Cisco's scanner enumerates an MCP server's tools, descriptions, and prompts, then probes them with known attack templates: indirect injection in returned data, tool-name shadowing, suspicious schema fields, exfil-via-error, and more. You get a Markdown/JSON report you can attach to a PR.

Warum nutzen

Hauptfunktionen

Live-Demo

In der Praxis

bereit

Installieren

Wählen Sie Ihren Client

~/Library/Application Support/Claude/claude_desktop_config.json  · Windows: %APPDATA%\Claude\claude_desktop_config.json
{
  "mcpServers": {
    "cisco-mcp-scanner": {
      "command": "uvx",
      "args": [
        "mcp-scanner",
        "--server",
        "stdio:npx -y <target>"
      ],
      "_doc": "Run against any MCP server config; produces a security report."
    }
  }
}

Öffne Claude Desktop → Settings → Developer → Edit Config. Nach dem Speichern neu starten.

~/.cursor/mcp.json · .cursor/mcp.json
{
  "mcpServers": {
    "cisco-mcp-scanner": {
      "command": "uvx",
      "args": [
        "mcp-scanner",
        "--server",
        "stdio:npx -y <target>"
      ],
      "_doc": "Run against any MCP server config; produces a security report."
    }
  }
}

Cursor nutzt das gleiche mcpServers-Schema wie Claude Desktop. Projektkonfiguration schlägt die globale.

VS Code → Cline → MCP Servers → Edit
{
  "mcpServers": {
    "cisco-mcp-scanner": {
      "command": "uvx",
      "args": [
        "mcp-scanner",
        "--server",
        "stdio:npx -y <target>"
      ],
      "_doc": "Run against any MCP server config; produces a security report."
    }
  }
}

Klicken Sie auf das MCP-Servers-Symbol in der Cline-Seitenleiste, dann "Edit Configuration".

~/.codeium/windsurf/mcp_config.json
{
  "mcpServers": {
    "cisco-mcp-scanner": {
      "command": "uvx",
      "args": [
        "mcp-scanner",
        "--server",
        "stdio:npx -y <target>"
      ],
      "_doc": "Run against any MCP server config; produces a security report."
    }
  }
}

Gleiche Struktur wie Claude Desktop. Windsurf neu starten zum Übernehmen.

~/.continue/config.json
{
  "mcpServers": [
    {
      "name": "cisco-mcp-scanner",
      "command": "uvx",
      "args": [
        "mcp-scanner",
        "--server",
        "stdio:npx -y <target>"
      ]
    }
  ]
}

Continue nutzt ein Array von Serverobjekten statt einer Map.

~/.config/zed/settings.json
{
  "context_servers": {
    "cisco-mcp-scanner": {
      "command": {
        "path": "uvx",
        "args": [
          "mcp-scanner",
          "--server",
          "stdio:npx -y <target>"
        ]
      }
    }
  }
}

In context_servers hinzufügen. Zed lädt beim Speichern neu.

claude mcp add cisco-mcp-scanner -- uvx mcp-scanner --server 'stdio:npx -y <target>'

Einzeiler. Prüfen mit claude mcp list. Entfernen mit claude mcp remove.

Anwendungsfälle

Praxisnahe Nutzung: Cisco MCP Scanner

Audit a third-party MCP before adopting it

👤 Developers ⏱ ~15 min intermediate

Wann einsetzen: A teammate wants to install a community MCP and you want a security signal first.

Ablauf
  1. Install scanner
    uvx mcp-scanner --help✓ Kopiert
    → Scanner runs
  2. Scan
    mcp-scanner --server "stdio:npx -y the-mcp" --output report.md✓ Kopiert
    → Report written
  3. Review
    Open report.md; triage findings by severity.✓ Kopiert
    → Adoption decision documented

Ergebnis: Documented security review before merging the MCP into your config.

Gate MCP changes in CI

👤 Developers ⏱ ~15 min intermediate

Wann einsetzen: You ship an internal MCP and want a baseline check on every PR.

Ablauf
  1. Add CI step
    Run mcp-scanner against the built server; fail on HIGH findings.✓ Kopiert
    → PR fails on regressions
  2. Fix or accept
    Each finding gets fixed or annotated with a risk acceptance.✓ Kopiert
    → Clean baseline

Ergebnis: No new prompt-injection surface ships unreviewed.

Kombinationen

Mit anderen MCPs für 10-fache Wirkung

cisco-mcp-scanner + github

Run on every PR via Actions; comment findings on the PR

Combine cisco-mcp-scanner with github: Run on every PR via Actions; comment findings on the PR✓ Kopiert
cisco-mcp-scanner + sentry

Pipe scanner findings as Sentry alerts on main branch

Combine cisco-mcp-scanner with sentry: Pipe scanner findings as Sentry alerts on main branch✓ Kopiert

Werkzeuge

Was dieses MCP bereitstellt

WerkzeugEingabenWann aufrufenKosten
scanner CLI (see docs) Not exposed as MCP tools — this is a scanner, not a server 1 call

Kosten & Limits

Was der Betrieb kostet

API-Kontingent
N/A
Tokens pro Aufruf
Local — uses the target MCP only
Kosten in €
Free OSS
Tipp
Run scans in a sandboxed network so probes can't exfil real data

Sicherheit

Rechte, Secrets, Reichweite

Credential-Speicherung: No credentials by itself
Datenabfluss: Whatever the target MCP egresses
Niemals gewähren: point at a production MCP with real credentials — use a staging instance

Fehlerbehebung

Häufige Fehler und Lösungen

Scanner times out on a slow MCP

Increase --timeout; check the server actually starts under stdio

False positives on benign tools

Use --baseline to mark them; future runs ignore

Alternativen

Cisco MCP Scanner vs. andere

AlternativeWann stattdessenKompromiss
Manual reviewSingle-author trusted MCPMisses subtle injection patterns

Mehr

Ressourcen

📖 Offizielle README auf GitHub lesen

🐙 Offene Issues ansehen

🔍 Alle 400+ MCP-Server und Skills durchsuchen