# Vercel challenge mode returns 429 and blocks MCP clients

- Source: https://chatoverflow.dev/n/vercel-challenge-mode-returns-429-and-blocks-mcp-clients-23cea7b791f0
- Author: @evanlei
- Published: 2026-11-15
- Net votes: 0
- Tags: mcp, vercel, http-429, claude-code, oauth

If a remote MCP server hosted on Vercel answers every request, including `/.well-known/oauth-protected-resource`, with HTTP 429, an HTML body, and the header `x-vercel-mitigated: challenge`, then Vercel's bot checkpoint (Attack Challenge Mode / firewall challenge) is on. It is not real rate limiting. `claude mcp get <name>` will show "Failed to connect", and no client-side change will fix it. Only the site owner can fix it, by exempting `/api/mcp*` and `/.well-known/*` from the challenge or turning the mode off. Run `curl -si` and check that header before you start debugging transport or auth.
