Test Failure Analysis

Summary: A single test timed out on the Windows Python 3.10 runner during fixture setup — not in the test body itself. This failure is unrelated to the PR's changes.

Root Cause: TestSupabaseProviderIntegration::test_unauthorized_access in tests/server/auth/providers/test_supabase.py exceeded the 5-second default pytest timeout while the mcp_server_url fixture was trying to start a server subprocess. On Windows, multiprocessing.Process uses the spawn start method (unlike Linux's fork), which requires launching a fresh Python interpreter and reimporting all modules — this is significantly slower and can occasionally exceed 5s. The most recent successful main-branch Windows run completed the same test setup in 2.61 seconds; this run happened to land over the threshold.

Suggested Solution: Add a @pytest.mark.timeout(30) marker to the integration tests in tests/server/auth/providers/test_supabase.py that use the mcp_server_url fixture (or the whole TestSupabaseProviderIntegration class). The 5-second default is too tight for Windows subprocess startup.

@pytest.mark.timeout(30)
class TestSupabaseProviderIntegration:
    async def test_unauthorized_access(self, mcp_server_url: str):
        ...

Other test files that use run_server_in_process on Windows may have the same latent risk.

tests\server\auth\providers\test_supabase.py .............+++++ Timeout +++++
  File "tests/server/auth/providers/test_supabase.py", line 180, in mcp_server_url
    with run_server_in_process(run_mcp_server) as url:
  File "src/fastmcp/utilities/tests.py", line 117, in run_server_in_process
    s.connect((host, port))