Skip to main content

Review test materials

For an extension with MCP services, provide authorization or account information that lets reviewers reproduce your test results. See Self-test report for the report itself.

Separate authentication from review access

Check the detected authentication method for each plugin MCP service. Standalone connectors use OAuth 2.0. A service's authentication method and the test access you provide for review are separate choices.
AuthenticationReview access
OAuth 2.0Complete online authorization or provide a test account as supported by the form
API Key in a plugin MCP serviceKey acquisition link or instructions, plus a usable test Key
Unable to provide accessExplain the reason, purpose, and supported tools
Do not change service authentication to bypass authorization. Prepare materials separately for each service.

Online OAuth authorization

Provide the service website, choose OAuth authorization, open the service's login page, and approve with your test account. Return to check success and the MCP information. Run a test case and record its steps and expected result. See Configure OAuth for callbacks and troubleshooting. Released service connections still require the appropriate account authorization.

Test account

Provide a dedicated account, password, website, login and authorization steps, test data, and cases. Explain verification codes, organization selection, and other restrictions. Sign out and verify the whole flow with these credentials before submitting. Keep the account usable throughout review.

Test API Key

Use this only for a plugin MCP service detected as API Key authentication. Provide acquisition instructions and the test Key. Check data access, quotas, expiry, and network restrictions and document them. Run a representative call before submission. API Key services do not use OAuth callbacks.

Unable to provide access

Explain why, what the service does, which tools it supports, and what can be verified. This information does not guarantee a substitute for execution testing or approval. Enter credentials only in the dedicated review fields, not public descriptions, screenshots, or packages.