Coffee Addict · Authentication Profile
Coffee Addict Authentication
Authentication
None. The OpenAPI 3.1 description (openapi/_original/coffeeaddict-nz-openapi.json) declares no securitySchemes and no security requirement. The docs describe the JSON as "static, CORS-open and free" (llms.txt), and the MCP server as "No key, no account, read-only." (/api/).
Coffee Addict declares 0 security scheme(s) across its OpenAPI definitions.
CompanyCoffeePrice ComparisonNew ZealandOpen DataRetailMCP
Methods:
Schemes: 0
OAuth flows:
API key in:
Security Schemes
Source
Authentication Profile
Work with this as data
Every security artifact here is available over the APIs.io API and to AI agents over MCP.