Agent MCP Directory

Vercel MCP accepts Client ID Metadata Documents

Any MCP client can now connect to Vercel MCP without prior review by publishing a Client ID Metadata Document and using its HTTPS URL as the OAuth client_id. Users still approve each connection. Reported 2 November 2026 by vercel.com, read 4 November 2026; products involved: Vercel.

What it changes in the data held here

517 endpoints in the directory offer dynamic client registration, 16 publish OAuth metadata without a registration endpoint, and 191 state client ID metadata document support. 533 endpoints stop at a sign-in challenge, so this directory sees their auth route but not their tools.

Vercel on this directory's rubric, as read on 4 November 2026: remote transport: Streamable HTTP only; oauth with client registration: bring your own AS; CIMD on Vercel MCP; per-tool auth scoping: scopes per handler.

Source: vercel.com, a primary source, dated 2 November 2026 and read 4 November 2026. The opening paragraph above is the item; the figures in this section come from this directory's own run of 4 November 2026.