Vercel MCP (official, remote)
Last tested 2026-10-22
Score 33/100 · Last tested 2026-10-22 · Server version not reported · Remote endpoint https://mcp.vercel.com (streamable-http) · Repo vercel/vercel-mcp-overview
Summary: Vercel MCP (official, remote) requires credentials or a backing service before it will list tools.
Test results
| Test | Result | Points | Evidence |
|---|---|---|---|
| install | pass | 20 | Endpoint https://mcp.vercel.com reachable over streamable-http (HTTP 401) in 0.2s; no install step for remote servers. |
| handshake | auth-gated | 5 | Auth-gated: HTTP 401 without credentials; OAuth challenge (WWW-Authenticate, resource_metadata https://mcp.vercel.com/.well-known/oauth-protected-resource). We do not sign in; not counted as working. |
| maintenance | partial | 5 | Repo pushed 281 days before test. |
| docs | fail | 0 | README checks failed. Automated check of the package's own README (vendor repo README (github.com/vercel/vercel-mcp-overview)). |
| license | partial | 3 | License not machine-detected as OSI (no license found). |
Local-model readiness
Not yet tested (no tools/list response without credentials).
Not tested
We did not test behavior with real credentials, security, or performance under load. These are planned; see methodology.
Tools listed
Not available (handshake did not complete without credentials).
Config used in our test
{
"mcpServers": {
"vercel-mcp-official-remote": {
"type": "http",
"url": "https://mcp.vercel.com"
}
}
}FAQ
Is Vercel MCP (official, remote) deprecated?
No. vercel-remote was not deprecated or archived when we last tested it on 2026-10-22.
What replaces Vercel MCP (official, remote)?
Nothing; Vercel MCP (official, remote) is not deprecated as of 2026-10-22.
Does Vercel MCP (official, remote) need an API key?
Yes. Without credentials it only printed a missing-credential message and did not list tools (auth-gated).
Embed the badge
The badge always shows the current score; payment never changes it.