Connection name: vercel_humanity_laws_official Endpoint: https://mcp.vercel.com Observed: September 24, 2026, approximately 14:36 UTC.

OAuth sign-in completed successfully, but subsequent read-only checks returned:

list_teams: teams: [] (zero teams). Project requests using either the verified team ID or team slug: HTTP 403, “Not authorized” for the requested team scope. The error resolved to the expected team ID.

There is no configured static bearer token or authorization-header override.

I can see the team and its projects in my browser. However, we have not verified which account identity and team scope are bound to the MCP OAuth grant. We therefore cannot confirm whether this is an account mismatch, a grant-scope issue, or a service-side authorization problem.

Please advise how to inspect the existing grant and make the narrowest correction. A separate official MCP connection has already completed OAuth and reproduced the issue, so I would like to avoid creating more duplicate connections.

I can provide team and project identifiers privately through an official channel if needed. No credentials are included in this report.