mcp4openapi

The project demonstrates a strong focus on security, implementing explicit safeguards against common web vulnerabilities. Key measures include: DNS rebinding protection, robust prototype pollution prevention (`isSafePropertyName`), ReDoS protection in regex handling, comprehensive sensitive data redaction in logs and HTTP requests, and strict policy enforcement (including private network access control, MIME type validation, and size limits) for proxy downloads to mitigate SSRF and LFI. Payload size limits are enforced for incoming requests. Authentication is flexible, supporting OAuth 2.0 (with PKCE, state parameter, redirect URI validation) and various token-based methods. Input validation is performed using a schema validator. Tool filtering further reduces the attack surface by controlling API exposure.