We are preparing a People’s Court service submission in Vercel Connect. Our public-client authorization-code flow requires S256 and the exact resource https://mcp.peoplescourt.ai/mcp on authorization, token exchange and refresh. The OAuth method uses https://peoplescourt.ai/oauth/authorize and https://peoplescourt.ai/api/oauth/token, with cases:read offline_access and callback https://connect.vercel.com/callback.

Using the selected matching test connector through the Connect API with resources: ['https://mcp.peoplescourt.ai/mcp'] successfully completes authorization, returns a token, refreshes it and permits fictional-account MCP reads. The submission page’s Test User Token flow sends an authorization URL containing the client ID, response type, redirect URI, state, scopes and S256 challenge, but no resource. People’s Court therefore rejects that request with “Select the exact registered API or MCP resource.” The submission method’s advanced fields expose Default Audience but no resource default; an audience parameter is not a substitute for the required resource. A subsequent scope-only API token request also returned User authorization required (401).

What is the supported way to pass a required resource through the submission token test, or have the resource-aware API test count toward the matching method’s verification? We can provide the private connector ID through an appropriate support channel. No passwords, token values, authorization codes, verifiers or case records are included in this report.

Two public reports describe similar resource-targeting failures: Builder.io redirect missing resource and v0 invalid_target issue #17583. Neither records a confirmed resolution at our October 14 check.

References: submission test instructions, SDK resource parameter.