generated: '2026-09-19' method: searched host: https://developers.beyondpricing.com notes: Only the RFC 8414 OAuth 2.0 Authorization Server Metadata document is published (on the developers.beyondpricing.com host). It advertises authorization/token/introspection/ registration/revocation endpoints, nine scopes, four grant types (authorization_code, client_credentials, device_code, refresh_token) and PKCE S256. The apex host beyondpricing.com and api.beyondpricing.com return 404 for all probed well-known paths. hosts: - host: https://developers.beyondpricing.com documents: - path: /.well-known/oauth-authorization-server status: 200 file: beyond-oauth-authorization-server.json standard: RFC 8414 - path: /.well-known/security.txt status: 404 - path: /.well-known/openid-configuration status: 404 - path: /.well-known/api-catalog status: 404 - path: /.well-known/ai-plugin.json status: 404 - host: https://neyoba.beyondpricing.com documents: - path: /.well-known/oauth-protected-resource status: 200 file: beyond-neyoba-oauth-protected-resource.json bytes: 249 path_echo_control: passed x-shape-fix: converted: '2026-08-20' from: documents note: Rewritten into hosts[] -> documents[], the only shape well_known_docs() in score.rb reads. A served .well-known surface recorded in any other shape scores as absent. x-mcp-probe: probed: '2026-09-19' issue: roadmap#321, roadmap#337 documents: - host: https://neyoba.beyondpricing.com path: /.well-known/oauth-protected-resource file: beyond-neyoba-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.'