MCP security checklist
MCP Server Security Checklist Generator
Use this launch gate before you publish an MCP server, list it in a directory, or connect it to coding agents. The checklist focuses on the failures that make AI tool integrations risky: broad permissions, secret leakage, tool injection, and weak observability.
- Use this when you need an MCP server security checklist before launch.
- Related searches: MCP server risk assessment, MCP security scanner, AI tool permission checklist.
When to Use This Checklist
Run this review before public directory submission, customer demos, or connecting an MCP server to coding agents. The goal is a practical launch gate: inspect the server, identify missing controls, and leave with a concrete report.
Pre-launch Review
Check whether the server is safe enough to publish, demo, or connect to an agent.
Release Decision
The scoring model turns abstract security advice into an operational go, harden, or stop decision.
Next Checklist
If one tool class is risky, split the review into filesystem MCP safety, database MCP safety, or browser MCP safety.
Release Gate
Use the score as a product gate, not a security certification. A score above 80 means the server is ready for a limited public demo. A score between 50 and 79 means you should add confirmations, logs, and tighter scopes before launch. A score below 50 means the server should stay private until the risky tools are redesigned.
Example Review
A filesystem MCP server should start with read-only tools, narrow path allowlists, clear tool names, and no secret-bearing output. A database MCP server should add query limits, write confirmations, and audit logs. If the server cannot explain what each exposed tool can do, do not submit it to a public directory yet.
FAQ
Is this a full MCP penetration test?
No. It is a launch-readiness checklist. Use code review and security testing for high-risk servers.
Should an MCP server expose write tools by default?
No. Default to read-only tools, then add confirmations, scopes, and logs for write actions.
What should I publish with a public MCP server?
Publish tool names, risk classes, permissions, privacy behavior, rate limits, and contact information for vulnerability reports.