generated: '2026-09-19'
method: searched
source: live probes of Atlassian .well-known discovery surface (2026-06-20)
hosts:
- host: https://developer.atlassian.com
  documents:
  - path: /.well-known/security.txt
    status: 200
    file: jira-security.txt
  - path: /.well-known/api-catalog
    status: 404
- host: https://auth.atlassian.com
  documents:
  - path: /.well-known/openid-configuration
    status: 200
    file: jira-openid-configuration.json
  - path: /.well-known/oauth-authorization-server
    status: 200
    file: jira-oauth-authorization-server.json
- host: https://api.atlassian.com
  documents:
  - path: /.well-known/oauth-authorization-server
    status: 404
  - path: /.well-known/openid-configuration
    status: 404
- host: https://mcp.atlassian.com
  documents:
  - path: /.well-known/oauth-protected-resource
    status: 200
    file: jira-mcp-oauth-protected-resource.json
    bytes: 748
  path_echo_control: passed
notes:
- OAuth 2.0 (3LO) and OIDC discovery are served from the Atlassian identity host auth.atlassian.com, not
  the per-tenant *.atlassian.net API host.
- security.txt is PGP-signed; canonical copy at https://www.atlassian.com/.well-known/security.txt.
x-mcp-probe:
  probed: '2026-09-19'
  issue: roadmap#321, roadmap#337
  documents:
  - host: https://mcp.atlassian.com
    path: /.well-known/oauth-protected-resource
    file: jira-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.'