generated: '2026-09-19' method: searched source: https://manual.firstresonance.io/api/access-tokens notes: ION's public API host (api.buildwithion.com) exposes no /.well-known/ surface; discovery lives on the Keycloak realm that issues API-key access tokens and on the beta MCP server. Both documents below returned 200 and are saved verbatim. hosts: - host: https://auth.buildwithion.com documents: - path: /realms/api-keys/.well-known/openid-configuration status: 200 file: first-resonance-openid-configuration.json note: OpenID Connect discovery for the api-keys realm (client_credentials token endpoint) - host: https://mcp.staging.buildwithion.com documents: - path: /.well-known/oauth-authorization-server status: 200 file: first-resonance-mcp-oauth-authorization-server.json note: RFC 8414 OAuth 2.1 authorization-server metadata for the beta MCP server (DCR + PKCE S256) - path: /.well-known/openid-configuration status: 401 - path: /.well-known/oauth-protected-resource status: 200 file: first-resonance-mcp-oauth-protected-resource.json bytes: 195 path_echo_control: passed probed_not_found: - host: https://api.buildwithion.com paths: - 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 - host: https://www.firstresonance.io paths: - path: /.well-known/security.txt status: 404 - host: https://firstresonance.io paths: - path: /.well-known/security.txt status: 404 x-mcp-probe: probed: '2026-09-19' issue: roadmap#321, roadmap#337 documents: - host: https://mcp.staging.buildwithion.com path: /.well-known/oauth-protected-resource file: first-resonance-mcp-oauth-protected-resource.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.'