Jplay Confirming the same issue in ChatGPT Web with the connected Vercel plugin (0.21.4), in addition to Codex. On Sep 28, 2026, I reconnected my Vercel account via OAuth and started a fresh ChatGPT chat. I requested a minimal production deployment and provided an inline index.html. The exposed tool signature was deploy_to_vercel(): any (no target/name/files inputs), while the current Vercel MCP docs describe those inputs: vercel.com/docs/agent-resources/vercel-mcp/tools ChatGPT called Vercel.deploy_to_vercel({}) and received: {"type":"json_rpc_error","code":-32602,"message":"Tool deploy_to_vercel n

techboy Any updates on this?

whyacatonsteam-9134 Hi! Just following up on this issue. My TXT verification record is publicly visible through Google DNS, but Vercel still requests verification of _vercel.v6.rocks, which I don't control. I only control craycity.v6.rocks through dynv6. Is there a way to verify my individual subdomain instead? Thanks!

system Thank you for bringing this to our attention. To ensure this is investigated with the necessary priority and privacy, please report all security-related concerns, potential exploits, or abuse directly to the Vercel Security Team. Please submit your report here: vercel.com/abuse Reporting via this official channel is the fastest way to reach our security engineers and ensures that sensitive information is handled in a secure environment rather than a public forum.

Amy Egan Hey @dharuvmanchanda. I just came across your post and wanted to check if you're still having trouble with you account. Hopefully this was already solved, but please let me know if you still need help

Neil Ellis Hi, I experienced a very similar situation with Vercel in October 2026. My account was compromised, resulting in over $4,000 USD in unauthorized Sandbox computing charges. Despite reporting the incident immediately and cooperating with Vercel's investigation, they have refused to cancel the charges, citing their terms of service. I noticed your incident occurred in July, before mine, and that Vercel staff subsequently followed up. Were you eventually refunded or credited for the unauthorized charges? Did Vercel explain how your account was compromised? I'm in Canada and considering legal actio

benibhn-3872 I have one additional question regarding commit author eligibility. My private GitHub repository contains an approved commit with the following identity: Commit: 6da92c8d2b81642be7bfaf1d729fcc5f4be9de05 Author: KAI Lab Preparation <kai-lab-preparation@local.invalid> Committer: KAI Lab Preparation <kai-lab-preparation@local.invalid> The Vercel project currently belongs to a Hobby team. The repository is owned by my personal GitHub account. I understand that Vercel requires commit authors to be associated with the Hobby team owner. Is there an officially supported way to deploy the exact content

trulot-oss Following up with additional checks from November 9: The connector authenticates as the same account shown in the Vercel dashboard and can list the correct team. However, listing that team’s projects returns only our other project. The intended project is visible in the dashboard but returns HTTP 404 through the connector using either its exact project ID or its name and team slug. Account Settings → Sign in with Vercel shows ChatGPT, owned by Vercel MCP, connected. Its menu offers Developer Website and Disconnect only, with no project-scope viewer or editor. Reconnecting did not resolve this.

system There's another community post with 404 debugging tips that might be helpful. Please give these solutions a try and let us know how it goes. community.vercel.com/t/debugging-404-errors/437 A human should be around soon to offer more advice. But you can also get helpful information quickly by asking v0.

laurentcoplet-3124 Hello Vercel MCP team, I'm experiencing a persistent authorization issue with the official ChatGPT–Vercel MCP integration. The connection correctly authenticates my Vercel account, recognizes my team and confirms my OWNER role. However: list_projects returns an empty list. get_project returns 404. list_deployments returns 403. get_deployment returns 404. I have already reconnected the integration and explicitly authorized the team, without success. The same account can successfully access and deploy the existing project using Vercel CLI. Vercel Support confirmed that MCP is currently in Beta a

vector541111-6675 hackkkks

attack541111-1390 haskdk

attack541111-1390 hackme