{ "schema": "varexis-public-evidence-record/0.3", "generated_at_utc": "2026-10-11T21:27:53.457Z", "record_id": "VXI-EXT-TOOL-TRUST-VERCEL-01-v1", "record_kind": "external_reference", "title": "Vercel MCP: Team access and deployment authority", "system": "Vercel MCP", "evidence_family": "agent_tool_trust_review", "index_status": "PUBLIC_SAFE_SOURCE_REVIEW", "evidence_state": "PRIMARY_DOCUMENTATION_REVIEW_ONLY", "canonical_question": "What should an agent verify before using a deployment connector to inspect or change a team's project?", "near_questions": [ "Does adding a deployment connector authorize access to every team?", "What should be checked before an agent deploys a project?", "Does Vercel MCP retain existing user permissions?", "Can Vercel MCP read runtime logs?", "Why might a Vercel team be missing after connection?", "Is a hosted MCP app on Vercel the same as Vercel MCP?", "Can a deployment diagnosis turn into an unintended change?", "What data can leave Vercel through an AI client?", "Which team owns the project a deployment tool will change?", "How should an agent distinguish preview and production targets?", "What does a saved Vercel connector review preserve?", "Does this profile verify my Vercel team grants?" ], "supported_claims": [ { "claim": "Vercel documents a separate sign-in and team-authorization step after adding its MCP server. Existing Vercel permissions still apply. Tools cover project and deployment inspection as well as operational changes, so a diagnosis request should not silently become a deployment or account change. Review the target team, project and environment, and the handling of returned logs.", "reliance": "DOCUMENTED_CAPABILITY_ONLY" } ], "not_demonstrated_claims": [ "Verified buyer configuration or effective access rights", "Independent tool execution or security testing", "Vendor certification, guaranteed safety or no-training assurance" ], "public_summary": "Vercel documents a separate sign-in and team-authorization step after adding its MCP server. Existing Vercel permissions still apply. Tools cover project and deployment inspection as well as operational changes, so a diagnosis request should not silently become a deployment or account change. Review the target team, project and environment, and the handling of returned logs.", "related_record_ids": [ "VXI-EXT-TOOL-TRUST-AWS-01-v1", "VXI-EXT-TOOL-TRUST-AZURE-01-v1" ], "source_review": { "source_type": "official_external_documentation", "source_title": "Vercel MCP authorization and security", "source_url": "https://vercel.com/docs/agent-resources/vercel-mcp", "checked_on": "2026-10-11", "candidate_record_id": "VXI-EXT-TOOL-TRUST-VERCEL-01-v1", "candidate_record_sha256": "a1e72aeb7451b656bb9bdcce5d7d67b29df2d683434a317e5389fa00b9503e64", "method": "Primary documentation reviewed for the published bounded statement.", "deployment_tested_by_varexis": false, "revalidation": "The delivered snapshot preserves the review date shown. Recheck current primary documentation and deployment context before relying on present applicability; payment does not trigger fresh research." }, "answer_policy": { "classification": "DOCUMENTED_WITH_DEPLOYMENT_BOUNDARY", "bounded_answer": "Vercel documents a separate sign-in and team-authorization step after adding its MCP server. Existing Vercel permissions still apply. Tools cover project and deployment inspection as well as operational changes, so a diagnosis request should not silently become a deployment or account change. Review the target team, project and environment, and the handling of returned logs.", "required_buyer_context": "Vercel's hosted account-management MCP, not an arbitrary MCP application deployed on Vercel. Authorized teams, effective role, target environment and client retention/approval settings.", "missing_evidence": "A broader claim needs evidence matching the intended use. Payment does not upgrade the evidence state." }, "private_boundary": "Raw logs, thresholds, private paths, source code, protected mechanisms and reconstruction-level details are excluded from public and paid delivery.", "trust_profile": { "schema": "varexis-agent-tool-trust/1", "identity": { "tool": "Vercel MCP", "variant": "Vercel's hosted account-management MCP, not an arbitrary MCP application deployed on Vercel." }, "review_status": "documentation_review_only", "checked_on": "2026-10-11", "version_scope": "Dated rolling documentation snapshot; no installed or hosted runtime version independently verified.", "plan_scope": "Buyer plan, feature entitlement and effective configuration are not verified.", "findings": [ { "field": "operator", "label": "Publisher and operator", "status": "documented", "statement": "Vercel operates its hosted MCP service.", "source_ids": [ "vercel-main" ] }, { "field": "purpose", "label": "Purpose", "status": "documented", "statement": "Inspect and manage Vercel projects, deployments and other account resources.", "source_ids": [ "vercel-tools" ] }, { "field": "reads", "label": "Read capability", "status": "documented", "statement": "Team/project information, deployment status and runtime logs are documented tool areas.", "source_ids": [ "vercel-tools" ] }, { "field": "writes", "label": "Write capability", "status": "documented", "statement": "The tool catalog includes deployment, project and account-management operations.", "source_ids": [ "vercel-tools" ] }, { "field": "auth", "label": "Authentication", "status": "documented", "statement": "Clients use a sign-in/OAuth flow and team authorization.", "source_ids": [ "vercel-main", "vercel-tools" ] }, { "field": "permissions", "label": "Permission surface", "status": "documented", "statement": "Adding the server does not complete authorization; the owning team must be granted and existing rights apply.", "source_ids": [ "vercel-tools" ] }, { "field": "egress", "label": "Data leaving the environment", "status": "review_inference", "statement": "Operational context is returned to the AI client and may be shared onward by other tools.", "source_ids": [ "vercel-main" ] }, { "field": "failures", "label": "Failure modes to consider", "status": "review_inference", "statement": "Wrong team or environment, sensitive log disclosure, or treating a missing team grant as an absent project.", "source_ids": [ "vercel-main", "vercel-tools" ] }, { "field": "unknown", "label": "Unknowns and applicability", "status": "unknown", "statement": "Authorized teams, effective role, target environment and client retention/approval settings.", "source_ids": [] }, { "field": "gate", "label": "Suggested refusal or clarification condition", "status": "varexis_review_policy", "statement": "During diagnosis, stop before deployment or account changes until the exact target and action are authorized.", "source_ids": [] } ], "evidence_sources": [ { "source_id": "vercel-main", "url": "https://vercel.com/docs/agent-resources/vercel-mcp", "final_url": "https://vercel.com/docs/agent-resources/vercel-mcp", "title": "Vercel MCP authorization and security", "checked_on": "2026-10-11", "sha256": "5696e3d24e1ece760827b228adae52e71e71259fdcdbccd4441209c7a861769f", "bytes": 1024067 }, { "source_id": "vercel-tools", "url": "https://vercel.com/docs/agent-resources/vercel-mcp/tools", "final_url": "https://vercel.com/docs/agent-resources/vercel-mcp/tools", "title": "Vercel MCP team access and tool categories", "checked_on": "2026-10-11", "sha256": "8a3ca6211f3ec75acc22b8131f0e9fd1987920017f0e7d5ab875d604dd613823", "bytes": 814811 } ], "observed_tool_execution": false, "policy_basis": "Suggested VAREXIS review gates; apply the buyer's authorized task and policy. These conditions do not execute or enforce controls.", "commercial_reliance_boundary": "A source-linked review aid, not a vendor certification, security clearance or deployment assessment. Unknown does not mean false or unsafe.", "paid_value": { "decision_context": "Preserve team, environment and log-disclosure checks used to approve a deployment assistant.", "free": "Complete profile, practical questions, sources and limitations; may be saved locally.", "single_request": "Existing server-saved version-bound route snapshot for later authenticated retrieval.", "evidence_receipt": "The same snapshot plus the existing unsigned delivery receipt.", "excluded": [ "Fresh vendor research", "Continuous monitoring or change alerts", "Testing the buyer configuration", "Private evidence or vendor certification" ], "integrity": "Hashes identify content versions; they do not prove truth or provide a signature." }, "revalidation": { "trigger": "Recheck when permissions, deployment, authentication, source guidance or intended use changes; a purchase does not trigger revalidation.", "specific_watch": "Recheck granted teams, project role and deployment target whenever the connection or task changes." }, "change_history": [ { "version": 1, "date": "2026-10-11", "change": "Initial documentation review; no earlier vendor assessment claimed." } ] }, "paid_access_note": "The full published answer and boundaries are free. Paid access saves the selected route and source versions, with an unsigned receipt when purchased. Preview coverage before paying. Fresh research, bespoke assessment and protected evidence are excluded.", "service_route": { "request_guide": "/varexis-index/request.html", "request_workflow": "/varexis-index/request-workflow.json", "service_id": "single_request", "service_routes_url": "/varexis-index/service-routes.json", "payment_required": true, "availability_endpoint": "/api/index/capabilities", "operational_status": "AUTOMATIC_SERVICE_CAPABILITIES_GATED", "checkout_url": "/index-access" }, "authority_boundary": "VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.", "human_page": "/varexis-index/catalog.html#vercel-mcp-team-deployment-trust", "machine_readable_record": "/varexis-index/records/vercel-mcp-team-deployment-trust.json" }