Discovery & Onboarding Gates


MCP Server & UI Tiers

Gate 0 Domain Verification & OAuth Auto-Discovery

Before a partner MCP server can be linked or invoked, automated onboarding checks verify domain ownership (/.well-known/google-connected-apps), RFC 9728 Protected Resource Metadata (/.well-known/oauth-protected-resource), RFC 8414 Authorization Server Metadata (/.well-known/oauth-authorization-server), and MCP snapshot responsiveness.

Zero-Redirect Requirement on /.well-known/google-connected-apps

Automated domain ownership verifiers do not follow HTTP 301 or 302 redirects. Ensure your CDN and web server serve GET /.well-known/google-connected-apps directly with HTTP 200 OK within 5 seconds using the token configured in demo-verify-8cc0c654befeeaf4fc28b33dfe0ba708.

Interactive Readiness Checks

1. Gate 0 Domain Ownership Verification (/.well-known/google-connected-apps)

Test the live GET /.well-known/google-connected-apps endpoint in both JSON ({"verification_token": "...", "tokens": [...]}) and text/plain formats, or simulate an HTTP 302 redirect failure mode.

{
  "verification_token": "demo-verify-8cc0c654befeeaf4fc28b33dfe0ba708",
  "tokens": [
    "demo-verify-8cc0c654befeeaf4fc28b33dfe0ba708"
  ]
}

2. RFC 9728 & RFC 8414 Auto-Discovery Chain Validator

When an unauthenticated client probes POST /mcp, the server responds with HTTP 401 Unauthorized and a WWW-Authenticate: Bearer resource_metadata=".../oauth-protected-resource" header. Run the validator below to test all 3 RFC 9728 path variants (/.well-known/oauth-protected-resource, /.well-known/oauth-protected-resource/mcp, /mcp/.well-known/oauth-protected-resource) and verify that RFC 8414 metadata includes "S256" PKCE and "private_key_jwt" when client_id_metadata_document_supported: true is advertised.

3. 5-Stage End-to-End Snapshot Probe (< 5000ms Budget)

Execute the complete 5-stage readiness probe combining Gate 0 domain verification, RFC 9728 401 challenge inspection, RFC 8414 metadata validation, and MCP Streamable HTTP initialize + tools/list + resources/list within the 5000ms latency budget.