GPT-5.6 (Sol / Terra / Luna) is now evaluated on TrustVector โ€” with day-1 independent verification, incl. METR's benchmark-cheating findings.

Read the evaluation
Evaluation record ยท mcp-server-vercel

Vercel MCP Server

v2026.7-beta

Vercel

MCPdeploymentdevopshostingmcp
79
Strong
About This MCP

Vercel's official hosted MCP server at mcp.vercel.com. Provides docs search plus tools to inspect teams, projects, deployments, build and runtime logs, and Agent Runs observability. No longer read-only: includes write-capable tools such as buy_domain (domain purchase), toolbar comment replies/edits/resolution, shareable-link creation for protected deployments, and CLI-guided deploys. Remote-only with OAuth 2.1, a client allowlist, and mandatory consent. Still in Beta on all plans.

Last Evaluated: July 9, 2026
Official Website

Trust Vector Analysis

Dimension Breakdown

๐Ÿš€Performance & Reliability
+
api reliability

Endpoint stability analysis on Vercel platform infrastructure

Evidence
Vercel MCP Documentation โ€” Hosted on Vercel's own platform infrastructure with a single managed endpoint at https://mcp.vercel.com
highVerified: 2026-07-09
operation success rate

Operation success testing across documented tools on real projects

Evidence
Vercel MCP Documentation โ€” Read-oriented tools (projects, deployments, logs) are thin wrappers over the stable Vercel REST API and succeed consistently within granted scopes
mediumVerified: 2026-07-09
search accuracy

Relevance assessment of documentation search results for common platform queries

Evidence
Vercel MCP Documentation โ€” Documentation search returns current Vercel docs, reducing hallucinated configuration answers in coding agents
mediumVerified: 2026-07-09
error recovery

Error handling testing across permission, scope, and session-expiry failures

Evidence
Vercel MCP Documentation โ€” Returns structured errors for unauthorized scopes, unknown projects, and expired sessions; OAuth re-consent flow recovers expired grants
mediumVerified: 2026-07-09
rate limit handling

Rate limiting behavior observation; limited published detail during beta

Evidence
Vercel MCP Documentation โ€” Inherits Vercel API rate limits per authenticated user; MCP-specific limits are not separately published during Public Beta
lowVerified: 2026-07-09
๐Ÿ›ก๏ธSecurity
+
authentication security

Review of OAuth 2.1 flow, consent screens, and token lifecycle

Evidence
Vercel MCP Documentation โ€” OAuth 2.1 authorization with mandatory user consent on every connection; no static API tokens are placed in client configuration
highVerified: 2026-07-09
scope limitation

Permission boundary testing of the shipped tool surface for write capability; lowered from 90 because write-capable tools, including one that spends money and one that mints protection-bypassing links, are now part of the default surface

Evidence
Vercel MCP Tools Reference โ€” The read-only launch posture has ended: current tools include buy_domain (purchases a domain with registrant details), reply_to_toolbar_thread / edit_toolbar_message / change_toolbar_thread_resolve_status, get_access_to_vercel_url (creates shareable links bypassing deployment protection), and deploy_to_vercel CLI guidance
highVerified: 2026-07-09
token exposure risk

Token storage and exposure-surface analysis for the remote-only model

Evidence
Vercel MCP Documentation โ€” Remote-only design means no locally stored long-lived secrets; OAuth tokens are short-lived and revocable from the Vercel dashboard
highVerified: 2026-07-09
unauthorized action risk

Threat modeling of agent misuse against the allowlisted tool surface; lowered from 88 following the addition of write-capable and spend-capable tools

Evidence
Vercel MCP Documentation โ€” Client allowlist and per-connection consent remain, with documented confused-deputy protection; however an injected agent could now purchase domains, create protection-bypassing shareable links, or post toolbar replies. Vercel's own docs recommend enabling human confirmation for tool execution
highVerified: 2026-07-09
action auditability

Audit logging review of grant management and access attribution

Evidence
Vercel MCP Documentation โ€” OAuth grants are visible and revocable per user; access activity is attributable to the granting account, though a dedicated MCP audit log is not yet exposed
mediumVerified: 2026-07-09
๐Ÿ”’Privacy & Compliance
+
deployment data exposure

Data flow analysis of tool results from Vercel to LLM providers

Evidence
Vercel MCP Documentation โ€” Project metadata, deployment details, and log contents are returned to the LLM provider as tool results
highVerified: 2026-07-09
sensitive data protection

Assessment of redaction controls on log-reading tools

Evidence
Vercel MCP Documentation โ€” Deployment logs can contain secrets, tokens, or PII printed by application code; the server does not redact log contents before returning them
mediumVerified: 2026-07-09
organization data control

Access control review against Vercel team RBAC

Evidence
Vercel Access Control Documentation โ€” Access mirrors the authenticated user's team roles and project permissions; team admins govern membership and can revoke OAuth grants
mediumVerified: 2026-07-09
third party data sharing

Analysis of downstream data sharing once tool results leave Vercel

Evidence
Vercel Privacy Policy โ€” Project and log data retrieved via MCP is shared with the user's chosen LLM provider under that provider's data policy
mediumVerified: 2026-07-09
๐Ÿ‘๏ธTrust & Transparency
+
documentation quality

Documentation completeness and accuracy review

Evidence
Vercel MCP Documentation โ€” Clear official documentation covering endpoint, OAuth setup, supported clients, tool capabilities, and security model
highVerified: 2026-07-09
operation visibility

Logging and traceability assessment across client and dashboard

Evidence
Vercel MCP Documentation โ€” Tool calls are visible in MCP client logs; connected integrations and grants are visible in the Vercel dashboard
mediumVerified: 2026-07-09
open source transparency

Source availability and independent verifiability review

Evidence
Vercel MCP Overview Repository โ€” Server implementation is closed source; a public overview repository documents capabilities but the code cannot be independently audited
highVerified: 2026-07-09
api coverage clarity

Comparison of documented tool surface against observed server capabilities

Evidence
Vercel MCP Documentation โ€” Tools reference (updated 2026-07-02) documents every tool with parameters, including the write-capable domain, toolbar, and access tools; documented surface matches observed behavior
mediumVerified: 2026-07-09
โš™๏ธOperational Excellence
+
ease of setup

Setup complexity assessment across allowlisted MCP clients

Evidence
Vercel MCP Documentation โ€” Zero installation: add https://mcp.vercel.com in a supported client and complete the OAuth consent flow
highVerified: 2026-07-09
api performance

Latency observation across representative tool calls

Evidence
Vercel MCP Documentation โ€” Hosted on Vercel's edge-adjacent infrastructure; typical tool responses return quickly, with log retrieval slowest for large deployments
mediumVerified: 2026-07-09
reliability

Uptime analysis combined with beta-status risk assessment

Evidence
Vercel Status โ€” Rides on Vercel platform availability, which is historically strong, though the MCP product itself is in Public Beta
mediumVerified: 2026-07-09
feature coverage

Feature completeness assessment against the full Vercel API surface; raised from 68 after substantial tool surface expansion (runtime logs, Agent Runs, domains, toolbar)

Evidence
Vercel MCP Tools Reference โ€” Coverage now spans docs search, teams/projects/deployments, build and runtime logs (with filtering), eve Agent Runs observability and traces, domain availability checks and purchase, toolbar comment workflows, deployment URL fetching, and CLI-guided deploys; environment variable management is still absent
highVerified: 2026-07-09
community adoption

Adoption analysis across the Vercel developer ecosystem and MCP clients

Evidence
Vercel MCP Overview Repository โ€” First-party server promoted to Vercel's large developer base and supported by major MCP clients since the Public Beta announcement
mediumVerified: 2026-07-09
Strengths
  • +Strong authentication posture: OAuth 2.1, mandatory consent, client allowlist, and documented confused-deputy protection
  • +Remote-only design eliminates locally stored long-lived secrets
  • +Live documentation search reduces hallucinated Vercel configuration answers
  • +Build and runtime log access with rich filtering enables fast AI-assisted debugging
  • +Agent Runs observability tools expose eve agent traces for production debugging
  • +Zero-install setup in supported MCP clients, including one-command install via npx add-mcp
  • +Backed by Vercel's reliable platform infrastructure
Limitations
  • !No longer read-only: buy_domain can spend money, toolbar tools post/edit content, and get_access_to_vercel_url mints links that bypass deployment protection โ€” human confirmation strongly recommended
  • !Closed source; implementation cannot be independently audited
  • !Deployment and runtime logs may contain unredacted secrets or PII that flow to the LLM provider
  • !Beta status means the tool surface and limits may change
  • !Client allowlist excludes unsupported or custom MCP clients
  • !No dedicated MCP-specific audit log exposed yet
Metadata
repository: https://github.com/vercel/vercel-mcp-overview
license: Proprietary (closed source; public overview repo)
maintained by: Vercel
status: Beta (all plans)
remote endpoint: https://mcp.vercel.com
authentication: OAuth 2.1 with mandatory consent and client allowlist
transport types
0: streamable-http (remote only)
installation methods
0: Remote MCP endpoint
1: npx add-mcp https://mcp.vercel.com
write access: Write-capable tools present since 2026 (domain purchase, toolbar comments, shareable links); no env var management
mcp version: 1.0

Use Case Ratings

code generation

Docs search plus project and log context makes coding agents far more accurate on Vercel deployments

research assistant

Good for investigating deployment history, failures, and project configuration across teams

data analysis

Useful for inspecting deployment metadata and logs, but no aggregate analytics tooling

customer support

Helps internal support diagnose customer-facing deployment issues from logs

education

Well suited to teaching deployment and platform concepts, though the surface is no longer purely read-only