mcp_openapi_bridge

The server itself does not contain obvious vulnerabilities like 'eval' or hardcoded secrets. It relies on environment variables for its API base URL (`BASE_URL`) and OpenAPI documentation URL (`DOC_URL`). The primary security risk is operational: if `BASE_URL` is set to an internal network address and `DOC_URL` points to a potentially malicious or overly permissive OpenAPI specification, an MCP client could leverage the server to perform Server-Side Request Forgery (SSRF) attacks against internal services. The path parameter substitution uses `trim_matches('"')` for basic sanitization, but careful configuration of `BASE_URL` and `DOC_URL` is crucial to prevent exposing sensitive resources.