generated: '2026-09-19'
method: probed
source: live GET of /.well-known/* on every Cloverleaf AI host discovered by DNS
hosts:
- host: https://mcp.cloverleaf.ai
  role: MCP server (Model Context Protocol, Streamable HTTP)
  documents:
  - path: /.well-known/oauth-protected-resource
    status: 200
    content_type: application/json
    file: cloverleaf-ai-oauth-protected-resource.json
  - path: /.well-known/oauth-authorization-server
    status: 200
    content_type: application/json
    file: cloverleaf-ai-oauth-authorization-server.json
  - path: /.well-known/openid-configuration
    status: 404
  - path: /.well-known/agent-card.json
    status: 404
  - path: /.well-known/agent.json
    status: 404
- host: https://auth.cloverleaf.ai
  role: Authorization server (Auth0 tenant cloverleaf-prod.us.auth0.com)
  documents:
  - path: /.well-known/openid-configuration
    status: 200
    content_type: application/json
    file: cloverleaf-ai-openid-configuration.json
  - path: /.well-known/oauth-authorization-server
    status: 200
    content_type: application/json
    note: byte-identical to the OIDC discovery document; not saved twice
  - path: /.well-known/oauth-authorization-server
    status: 200
    file: cloverleaf-ai-auth-oauth-authorization-server.json
    bytes: 2501
  path_echo_control: passed
- host: https://www.cloverleaf.ai
  role: Marketing website (WordPress)
  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
  - path: /.well-known/agent-card.json
    status: 404
  - path: /.well-known/agent.json
    status: 404
  - path: /llms.txt
    status: 200
    note: not a /.well-known/ path; captured at llms/cloverleaf-ai-llms.txt
- host: https://api.cloverleaf.ai
  role: Application API host (Rails); 404s every anonymous path
  documents:
  - path: /.well-known/oauth-protected-resource
    status: 404
  - path: /.well-known/agent-card.json
    status: 404
  - path: /.well-known/agent.json
    status: 404
- host: https://trust.cloverleaf.ai
  role: Trust center (Vanta)
  documents:
  - path: /.well-known/agent-card.json
    status: 200
    note: NOT a document. The Vanta single-page app answers 200 with the same HTML shell for every path
      including /robots.txt and /sitemap.xml. Recorded as a miss.
notes: The discovery surface that matters here is on the MCP host, not the website. The marketing site
  publishes nothing under /.well-known/, but mcp.cloverleaf.ai serves a complete RFC 9728 + RFC 8414 authorization
  discovery chain pointing at the company's own Auth0 tenant at auth.cloverleaf.ai, and that chain is
  what lets an MCP client discover how to authenticate. A prior round recorded only the www host and its
  five 404s.
x-mcp-probe:
  probed: '2026-09-19'
  issue: roadmap#321, roadmap#337
  documents:
  - host: https://auth.cloverleaf.ai
    path: /.well-known/oauth-authorization-server
    file: cloverleaf-ai-auth-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.'