Vercel MCP connector doesn't forward teamId/slug parameter to Vercel API — team-scoped token sees 0 projects

The Vercel MCP connector's list_projects and get_project tools accept a teamId parameter (team ID or slug), but that value doesn't appear to reach the actual Vercel API request.

• list_teams correctly resolves my team (team_OhRJgx3l28SST2A2mbkVjHPF).
• list_projects(teamId: "team_OhRJgx3l28SST2A2mbkVjHPF") returns an empty project list, despite the team having active projects (confirmed visible in the Vercel dashboard under this same team).
• get_project(projectId: "<real project id>", teamId: "team_OhRJgx3l28SST2A2mbkVjHPF") returns 404.
• Retested with the team slug instead of the ID in both calls — identical failure.
• Vercel's own support agent confirmed the personal-access token this connector uses is genuinely team-scoped, and that the fix is exactly to pass teamId/slug on the request — which I am already doing, in two different valid forms, with no change in behavior.
• Fully disconnected and reconnected the connector (not just reauthorized) — no change.

This points to the connector not threading its teamId parameter into the outgoing Vercel API call. Would appreciate someone checking the implementation.