What problem does it solve? MCP servers often ship without proper security: shared tokens, missing tenant isolation, no rate limiting, and publicly exposed tool manifests. This Skill provides a structured methodology to build, harden, or audit the security layer around MCP tools using seven dependency-ordered layers, without prescribing a specific tech stack. ## Core Features & Use Cases - Seven-layer security model: personal token identity, OAuth 2.1 delegation, per-tool tenant isolation, identity-based rate limiting, tool call logging, sandbox mode, and authenticated manifest discovery. - Two entry modes: a construction phase for building or hardening a server layer by layer with TDD, and an audit phase for verifying an existing server against all seven layers with CONFIRMED/PLAUSIBLE findings. - Pitfall knowledge base: an append-only references file capturing generic and stack-specific traps (e.g., Next.js + mcp-handler OAuth discovery issues). - Use Case: You built an MCP server exposing CRM tools and suspect tenant data leaks. Ask for an audit, and the Skill systematically greps every function touching each entity, verifies identity guards, and reports exploitable gaps before any fix. ## Quick Start Ask the assistant to audit the security of your existing MCP server tools or to harden your MCP server layer by layer starting with token identity.