generated: '2026-09-19'
method: searched
host: https://api.mireye.com
other_hosts:
- host: https://www.mireye.com
  documents:
  - path: /.well-known/security.txt
    status: 404
- host: https://docs.mireye.ai
  documents:
  - path: /.well-known/security.txt
    status: 404
hosts:
- host: https://api.mireye.com
  documents:
  - path: /.well-known/oauth-authorization-server
    status: 200
    file: mireye-oauth-authorization-server.json
    note: RFC 8414 OAuth 2.0 Authorization Server Metadata (issuer https://api.mireye.com, scope mcp:tools,
      PKCE S256)
  - path: /.well-known/openid-configuration
    status: 404
  - path: /.well-known/oauth-protected-resource
    status: 404
  - path: /.well-known/security.txt
    status: 404
  - path: /.well-known/api-catalog
    status: 404
  - path: /.well-known/oauth-protected-resource
    status: 200
    file: mireye-api-oauth-protected-resource.json
    bytes: 164
  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://api.mireye.com
    path: /.well-known/oauth-protected-resource
    file: mireye-api-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.'