Awesome-MCP-ZH

Awesome-MCP-ZH Security Hardening Guide

Least-privilege permissions

• Audit each connector individually: Before enabling any MCP server from the curated list, review what access it requests (file folders, databases, APIs). Approve only what's genuinely needed for its stated purpose.
• Revoke unnecessary scopes: If a server requests access to your entire file system but only needs a single folder, configure it to access only that folder. Deny requests for API keys or credentials unless absolutely required.
• Create isolated service accounts: Use separate, limited-access user accounts or API credentials specifically for third-party connectors rather than your primary credentials.

Network isolation

• Use air-gapped testing environments: Test new MCP servers in a sandboxed setup (separate computer or virtual machine) before connecting to production systems or sensitive data.
• Restrict outbound network access: Where possible, configure firewalls or tools to limit which external servers your connectors can contact—block unexpected network destinations.
• VPN or private endpoints: If using MCP servers, route their traffic through a VPN or private network gateway to encrypt and control data flow.

Monitoring

• Log all connector activity: Enable logging on MCP servers and review logs weekly for unexpected data access, failed authentication attempts, or unusual API calls.
• Set up alerts for permission changes: Configure notifications if a connector's scope or privileges are modified, or if it attempts to access new resources.
• Track update history: Note when each connector was last updated by its maintainer; flag servers without updates for 6+ months for re-evaluation or removal.

Red flags to watch for

• Unmaintained or unknown authors: Avoid connectors with no clear author name, missing contact information, or no updates in over a year—these may harbor unpatched vulnerabilities.
• Over-broad permission requests: Reject servers asking for "full system access," access to password managers, or unrelated API keys; this often signals poor security design.
• Unavailable documentation or source code: Do not enable closed-source connectors or those with no public repository; you cannot verify what they actually do.
• Unusual data requests or outputs: Stop using a connector if it suddenly requests new credentials, sends unexpected network traffic, or returns garbled or suspicious information in responses.