Mcp Server Safety Checklist

Automated security auditing and risk assessment for Model Context Protocol (MCP) servers.

Install
cmdop skills install agensi-mcp-server-safety-checklist

MCP Server Safety Checklist is a skill that performs automated security auditing of Model Context Protocol server implementations. It runs entirely offline, meaning source code and configuration files are never transmitted outside the local environment, which makes it suitable for proprietary or enterprise projects.

The skill covers four areas of risk assessment. First, it audits tool permissions, flagging any tools that carry write, delete, or execute capabilities that could be misused by an agent. Second, it performs exposure detection, identifying code paths that access .env files, private keys, or other configuration secrets. Third, it conducts network analysis, mapping external API dependencies and characterizing network exposure patterns within the server. Fourth, it validates mcp.json configuration files against security best practices and structural requirements.

The skill is designed specifically around the MCP security model rather than being a general-purpose code review. This distinction matters because general AI code-review prompts typically lack awareness of the protocol’s specific permission architecture and trust boundaries. Developers building or reviewing MCP servers before connecting them to an LLM can use this skill to surface risks before deployment. There are no tools exposed to a connected agent — the skill operates as a structured checklist-driven audit process. No environment variables are required for its operation.

Use cases

  • Audit an MCP server for overly broad tool permissions before deploying it to a production LLM environment
  • Detect accidental exposure of .env files or private keys in MCP server logic
  • Map all external API calls and network exposure points in an MCP server implementation
  • Validate mcp.json configuration files for structural correctness and security compliance
  • Review a third-party MCP server before integrating it into an internal agent workflow
  • Perform a pre-deployment security check on a proprietary MCP server without sending code to an external service

When to use it

  • When building or reviewing an MCP server before connecting it to any LLM
  • When onboarding a third-party MCP server and needing a structured risk assessment
  • When operating in an enterprise or regulated environment where code must not leave the local machine
  • When mcp.json configuration files need validation against known security requirements

When not to use it

  • When auditing non-MCP codebases or general web services — this skill targets MCP-specific risk patterns only
  • When a runtime or live-traffic security monitor is needed — this is a static, pre-deployment scan
  • When the project has no MCP server implementation to analyze
  • When a formal penetration test or compliance certification is required — this is a checklist audit, not a certified assessment