action_mcp

The project demonstrates strong security awareness, explicitly rejecting STDIO transport for production and focusing on robust network-based deployments. It includes a Gateway system for pluggable authentication (JWT, API Keys, session-based) with input validation, origin header checks, and DNS rebinding protection. Consent management for sensitive tool operations is a key feature. Detailed documentation highlights security best practices like preventing token theft and addressing the 'Confused Deputy Problem'. Middleware conflicts are acknowledged with a `mcp_vanilla.ru` solution, though this can be a friction point for less experienced users if not handled carefully.