Vercel MCP has shifted to a self-serve model where clients use a self-hosted Client ID Metadata Document (CIMD) rather than waiting for prior review. To establish trust without a formal verification badge, user consent screens explicitly display the client's logo, name, and hosting domain. Previously registered integrations will continue operating normally under this updated system. Instructions detailing how to connect clients have been published in the official Vercel MCP documentation.
Key points
Developers can now integrate any MCP client without waiting for manual platform review or…: Developers can now integrate any MCP client without waiting for manual platform review or prior evaluation.
The authorization workflow adopts CIMD standards as recommended over Dynamic Client Regis…: The authorization workflow adopts CIMD standards as recommended over Dynamic Client Registration in the MCP specification.
Existing applications registered with Vercel will experience no changes while users still…: Existing applications registered with Vercel will experience no changes while users still explicitly approve every connection.
Sources checked by our analysis pipeline: 1
Any MCP client can now ask to connect to Vercel MCP. You still log in and approve each connection, but the client no longer has to be reviewed by Vercel first. Previously, Vercel reviewed and allowlisted each client and its redirect URIs by hand, and anything not on the list was rejected.
To connect, a client publishes a Client ID Metadata Document (CIMD), a JSON file on its own domain that describes it, and uses that file's HTTPS URL as its OAuth client_id
. This follows the MCP authorization spec, which now recommends CIMD over Dynamic Client Registration.
Because Vercel hasn't reviewed these clients, the consent screen shows where each one comes from: its name, its logo, and the hostname that serves its metadata document, for example "Claude Code by claude.ai". CIMD clients don't get the Vercel verified badge, so the hostname is what you're trusting when you approve.
Apps already registered with Vercel are unchanged.
Read the Vercel MCP documentation to connect your client.
The Chinese technology firm shared these hardware supply plans directly with select customers ahead of the new product release. Relying on components from the two South Korean suppliers signals the memory architecture intended for the forthcoming advanced system. Broader launch timelines and detailed specifications for the equipment have not yet been made public.
Bug bounty programs are increasing rewards for defenders. These larger payouts aim to further incentivize individuals who identify and report vulnerabilities to protect systems.
Developers managing deployments can now leverage a flatter syntax that natively includes comment support for defining application settings. The format serves as a direct alternative to existing setups, maintaining complete parity with all previously supported properties. This gives teams greater flexibility in structuring repository definitions to match their workflow preferences.