Mcp Security Audit

If you're letting AI agents loose with MCP servers, this catches the security holes before they bite you. It scans .mcp.json files for hardcoded API keys and tokens, flags shell injection patterns in server args, and warns when you're using @latest instead of pinned versions. The pattern matching is solid: catches GitHub tokens, OpenAI keys, AWS credentials, plus dangerous stuff like bash -c and command substitution. Honestly most valuable during code review or as a pre-commit hook. The checks are straightforward Python you can extend with your own patterns or approved server lists. Not a replacement for a real secrets scanner, but a good first line of defense for MCP-specific risks.

skills.sh installs: 1.1K
GitHub stars: 41K
last updated: Aug 21, 2026

View on GitHub

Install

$ npx -y skills add github/awesome-copilot --skill mcp-security-audit --agent claude-code

Installs into .claude/skills of the current project.

Files

MCP Security Audit

Audit MCP server configurations for security issues — secrets exposure, shell injection, unpinned dependencies, and unapproved servers.

Overview

MCP servers give agents direct tool access to external systems. A misconfigured .mcp.json can expose credentials, allow shell injection, or connect to untrusted servers. This skill catches those issues before they reach production.

.mcp.json → Parse Servers → Check Each Server:
  1. Secrets in args/env?
  2. Shell injection patterns?
  3. Mutable package selectors (bare, @latest, ranges)?
  4. Dangerous commands (eval, bash -c)?
  5. Server on approved list?
→ Generate Report