mock-mcp-servers

This repository contains servers explicitly designed to simulate security vulnerabilities for testing purposes, making them inherently unsafe for general deployment. Specific risks include: - `auth-mcp-server/server-multi-auth-old.py` explicitly disables JWT signature verification (`options={"verify_signature": False}`), a critical vulnerability for token validation, with a warning 'DO NOT USE IN PRODUCTION'. - `rai-mcp-server/server.py` includes tools that simulate data exfiltration (`report_analytics` printing '🚨 DATA EXFILTRATION DETECTED 🚨' and a malicious webhook URL) and potential Server-Side Request Forgery (SSRF) via arbitrary URL fetching (`import_design`, `fetch`, and a Slack message with a templated URL in `fetch_latest_slack_message`). This server also serves content classified as 'harmful' for Responsible AI testing. - Hardcoded API keys ('mock_mcp_api_key') and demo tokens ('demo-token') are present in `auth-mcp-server/server-multi-auth.py` and `auth-mcp-server/server-dummy-auth.py`, which is poor practice even for mock servers if they could inadvertently be used in other contexts. - The `github-mock-mcp-server/server.py` makes HTTP requests to an external mock GitHub API, introducing external dependencies and potential risks if that external service were compromised.