generated: '2026-09-19' method: searched description: Results of probing the /.well-known/ discovery surface for every base host in apis.yml (baseURL) and the OpenAPI servers[]. Status is the HTTP code observed at fetch time. Buildkite publishes no /.well-known/ discovery documents on any API or web host — every probed path returns 404. Absence is valid, expected data; nothing was saved. hosts: - host: https://api.buildkite.com documents: - path: /.well-known/security.txt status: 404 - path: /.well-known/openid-configuration status: 404 - path: /.well-known/oauth-authorization-server status: 404 - path: /.well-known/api-catalog status: 404 - path: /.well-known/ai-plugin.json status: 404 - host: https://buildkite.com documents: - path: /.well-known/security.txt status: 404 - path: /.well-known/openid-configuration status: 404 - path: /.well-known/oauth-authorization-server status: 404 - host: https://agent.buildkite.com documents: - path: /.well-known/security.txt status: 404 - host: https://graphql.buildkite.com documents: - path: /.well-known/security.txt status: 404 - host: https://mcp.buildkite.com documents: - path: /.well-known/oauth-protected-resource status: 200 file: buildkite-com-mcp-oauth-protected-resource.json bytes: 137 - path: /.well-known/oauth-authorization-server status: 200 file: buildkite-com-mcp-oauth-authorization-server.json bytes: 518 path_echo_control: passed x-mcp-probe: probed: '2026-09-19' issue: roadmap#321, roadmap#337 documents: - host: https://mcp.buildkite.com path: /.well-known/oauth-protected-resource file: buildkite-com-mcp-oauth-protected-resource.json - host: https://mcp.buildkite.com path: /.well-known/oauth-authorization-server file: buildkite-com-mcp-oauth-authorization-server.json validated_on: resource (RFC 9728) / issuer (RFC 8414, OIDC) negative_control: one per host; a 2xx JSON object at an impossible path discards the host note: 'MCP-host OAuth discovery added 2026-09-19 (roadmap#321/#337): the harvest visits a provider''s primary hosts, and RFC 9728 protected-resource metadata lives on the MCP host, so these documents existed and were invisible to the scorer. Fetched live and validated on `resource`/`issuer`; one negative control per host.'