domains / families / security / mcp-server-security

mcp-server-security

combined

Secure Model Context Protocol (MCP) servers with transport encryption, tool authorization, input validation, and audit logging for safe AI agent integrations. Secure Model Context Protocol (MCP) servers with transport encryption,

When to use

• Deploying an MCP server that exposes tools (filesystem, database, API) to AI agents.
• Connecting an agent runtime (Claude Desktop, Cursor, a custom orchestrator) to one or
• Building a multi-tenant platform where multiple users share the same MCP server.
• Passing sensitive data (PII, credentials, internal documents) through MCP resources.
• Operating in a regulated environment (SOC 2, HIPAA, PCI-DSS) where tool invocations

When not to use

• Apply guidance only within authorized scope; test destructive steps in non-production first.
• Docs-only import: upstream scripts and templates not bundled.

Skill page

Conflict

The second copy (sickn33) is a mirror of the first (BagelHole) but contains a significant, conflicting modification in Section 3.3 (Securing stdio Transport). The original suggests using `npx` with Node permission flags, while the mirror explicitly warns against `npx -y` and Node flags as a complete boundary, recommending absolute paths to reviewed binaries and separate sandboxing instead. Because the mirror corrects a potential security weakness in the original, crowning the original would hide a safer, more robust alternative, and crowning the mirror would lose the original's specific configuration context. Therefore, they must be combined to reflect the stricter, corrected guidance.