{"id":"evilfreelancer-openapi-to-mcp","name":"openapi-to-mcp","af_score":59.5,"security_score":41.8,"reliability_score":27.5,"what_it_does":"openapi-to-mcp is a standalone proxy that loads an OpenAPI/Swagger specification at startup and exposes it as an MCP (Model Context Protocol) server. It creates one MCP tool per API operation (filtered by include/exclude env vars) and executes tool calls as HTTP requests to the backend REST API. It supports Streamable HTTP transport via GET/POST /mcp and provides correlation-id logging and optional instruction text customization.","best_when":"You already have a REST API with a valid OpenAPI 3.x JSON and you want to make those endpoints callable as MCP tools with minimal integration work.","avoid_when":"Avoid if you cannot trust or control the OpenAPI spec content (tool schemas/descriptions) or if you require strict transport security and auth/authorization at the MCP server boundary.","last_evaluated":"2026-03-30T15:38:47.190603+00:00","has_mcp":true,"has_api":true,"auth_methods":["HTTP Basic auth to backend API (optional) via MCP_API_BASIC_AUTH","Bearer token to backend API (optional) via MCP_API_BEARER_TOKEN"],"has_free_tier":false,"known_gotchas":["Tool naming is derived from path/method and may change if the OpenAPI spec changes; ensure the spec is stable.","If include/exclude env vars are misconfigured, expected tools may not be registered.","Backend API errors are likely surfaced as MCP/tool call failures, but the specific error mapping and retry behavior are not described."],"error_quality":0.0}