Agent MCP Directory

Vercel: MCP server, CLI and agent surfaces

Sign-in required, tools not seen, not counted. The MCP endpoint listed for Vercel at mcp.vercel.com answered 401 with OAuth metadata on 4 November 2026. Its tools can be listed only after a person authorizes a client, and this directory never signs in.

Fact sheet

CompanyVercel
Domainvercel.com
CategoryInfrastructure (Ora leaderboard category)
MCP serverSign-in required (OAuth with client registration)
Tranco rank3,040 on the list of 4 November 2026
Ora score91, grade A; Ora scanned the domain on 5 November 2026 and the cached score was read on 5 November 2026 from its score API (Ora's score page for vercel.com, a vendor-published score)
Company found throughthe vendor's own documentation; the awesome-remote-mcp-servers list; the GitHub MCP Registry; the official MCP Registry; Ora's public leaderboard
Last verified4 November 2026

MCP server

Endpointhttps://mcp.vercel.com
How it was foundlisted in the vendor's own documentation; the awesome-remote-mcp-servers list; the GitHub MCP Registry; the official MCP Registry; Ora's public leaderboard
Transportstreamable-http
HTTP status401
Connected4 November 2026, 20:01 UTC
Handshake time964 ms over 1 attempt
Documentationvercel.com

The endpoint answered the handshake with a sign-in challenge, so the tool list is not visible to this directory. It is not counted as an MCP server: a sign-in challenge is its own state, and the connector listed no tools.

Connector log

2 connections on 4 November 2026, read-only methods only

  • 19:56:01Z https://mcp.vercel.com sent initialize result auth-required (HTTP 401) 912 ms
  • 20:01:37Z https://mcp.vercel.com sent initialize result auth-required (HTTP 401) 964 ms

Authentication

Auth typeOAuth with client registration
What the challenge saidBearer error="invalid_token", error_description="No authorization provided", resource_metadata="https://mcp.vercel.com/.well-known/oauth-protected-resource"
Protected resource metadatamcp.vercel.com
Authorization server metadatavercel.com
Registration endpointhttps://api.vercel.com/login/oauth/register
Client ID metadata documentssupported
Auth as listed by a registryOAuth2.1 (a claim, not checked by connecting)

The sign-in route, step by step

  1. Request https://mcp.vercel.com without a token. It answers 401 and a WWW-Authenticate header.
  2. Read the protected resource metadata at https://mcp.vercel.com/.well-known/oauth-protected-resource to find the authorization server.
  3. Register a client at the registration endpoint https://api.vercel.com/login/oauth/register (dynamic client registration), so no human has to create an app first.
  4. Send a person through the authorization page, then retry the endpoint with the bearer token. The connector stops after step 2 and never authorizes.

See OAuth for MCP: client ID metadata documents and dynamic registration for how each route works.

CLI

Packagevercel on npm (page)
Existsyes
Latest version65.11.0
Last publish3 November 2026
Command namesvc, vercel
Checked4 November 2026

Other agent surfaces

Agent surfaces other than MCP and CLI
SurfaceResult
OpenAPI fileFound: vercel.com (JSON, via a direct request).
WebMCP in the initial HTMLNot detected on the home page by the shared crawl.
MCP discovery fileNot found (the crawl got a non-200 answer).
A2A agent cardNot found (the crawl got a non-200 answer).
A2A agent card (older path)Not found (the crawl got a non-200 answer).
agents.jsonThe path answered with a web page, not the file. Not counted.
OAuth authorization server metadataFound: vercel.com/.well-known/oauth-authorization-server answered with a valid document in the shared crawl.
NLWeb endpointNot checked in this edition.

Registry listings

Registry listings
RegistryListed
Official MCP RegistryYes: com.vercel/vercel-mcp
GitHub MCP RegistryYes
awesome-remote-mcp-serversYes
SmitheryNot checked: Smithery's listing pages and search API were unavailable on 4 November 2026.
GlamaNot checked: Glama's API needs a key and attribution terms.