Vercel (mistertk) MCP Server

@mistertk/vercel-mcp npm v0.1.1

Published by @mistertk — no publish provenance, so origin is unverified, but the source is public: the repository link below is self-declared yet readable, so you can inspect the code before adopting it.

Model Context Protocol server for Vercel API - provides 114+ tools, 4 resources, and 5 prompts for comprehensive Vercel platform management including deployments, domains, DNS, projects, teams, security, monitoring, and more

Trust grade
A
96/100
Last scanned get badge →
Trust
A · 96/100
Adoption risk for you: the threat score, then adjusted down for blast radius, publisher verification and how much the scan could see. Deterministic; every point is auditable.
Capability
Moderate
Blast radius if it went rogue — what the server’s tools could reach. Independent of trust.
Coverage
Source
How much the scan could actually inspect. Shallow coverage is stated, never hidden.
Share this Trust Score
𝕏 Share LinkedIn Reddit
A Why this grade threat 100 − adoption risk = 96/100

The grade answers one question — how safe is this server for you to adopt — so it is computed in two auditable stages. Nothing below is an opinion or an LLM's guess; every line is a real term the deterministic engine applied, and the same input always yields the same number.

1. Threat score — 100 − 0 = 100. What the published surface and source actually contain:

The deterministic scan raised no scored threat in the surface it inspected — the threat score stayed at 100. Capability observations and advisory notes are recorded but never lower it.

2. Client adoption risk — 100 − 4 = 96. Three small, subtract-only factors that reflect your risk in adopting it — a clean scan proves less on a powerful, unverified or barely-inspectable package, so the grade says so plainly:

PointsAdoption-risk factor
−3 capability blast radius (moderate) — client exposure if the model is manipulated
−1 publisher verification (public source) — no provenance, but the source is public and inspectable

Capability observations and info notes are shown under Findings but never scored. Open any row's finding below for the file, line and evidence behind a deduction.

Findings 1

medium Untrusted input can drive an external actionMTC-FLOW-005

Untrusted-input tools ([downloadArtifact]) co-exist with external-action tools ([createWebhook, deleteWebhook, getWebhook]). A prompt injection could cause unwanted external actions, though no direct sensitive-data leak path was found.

Evidence: untrusted [downloadArtifact] → sinks [createWebhook, deleteWebhook, getWebhook]

Fix: Require confirmation for state-changing/egress actions triggered after processing untrusted content.

Location: flow downloadArtifact → createWebhook

Tools 131

Each tool and what it can reach — statically extracted from the published source.

  • createWebhooknetwork egress
  • deleteWebhooknetwork egress
  • downloadArtifactingests untrusted input
  • getWebhooknetwork egress
  • addBypassIpno sensitive capability
  • addProjectDomainno sensitive capability
  • addProjectMemberno sensitive capability
  • artifactExistsno sensitive capability
  • artifactQueryno sensitive capability
  • assignAliasno sensitive capability
Show 121 more tools ↓
  • cancelDeploymentno sensitive capability
  • createAccessGroupno sensitive capability
  • createAccessGroupProjectno sensitive capability
  • createAuthTokenno sensitive capability
  • createCheckno sensitive capability
  • createCustomEnvironmentno sensitive capability
  • createDnsRecordno sensitive capability
  • createEdgeConfigno sensitive capability
  • createEdgeConfigTokenno sensitive capability
  • createEnvVarno sensitive capability
  • createEventno sensitive capability
  • createLogDrainno sensitive capability
  • createTeamno sensitive capability
  • deleteAccessGroupno sensitive capability
  • deleteAccessGroupProjectno sensitive capability
  • deleteAliasno sensitive capability
  • deleteAuthTokenno sensitive capability
  • deleteConfigurableLogDrainno sensitive capability
  • deleteConfigurationno sensitive capability
  • deleteCustomEnvironmentno sensitive capability
  • deleteDeploymentno sensitive capability
  • deleteDnsRecordno sensitive capability
  • deleteEdgeConfigno sensitive capability
  • deleteEdgeConfigSchemano sensitive capability
  • deleteEdgeConfigTokensno sensitive capability
  • deleteIntegrationLogDrainno sensitive capability
  • deleteTeamno sensitive capability
  • deleteTeamInviteCodeno sensitive capability
  • editEnvVarno sensitive capability
  • exchangeSsoTokenno sensitive capability
  • getAccountInfono sensitive capability
  • getActiveAttackStatusno sensitive capability
  • getAliasno sensitive capability
  • getAllChecksno sensitive capability
  • getArtifactStatusno sensitive capability
  • getAuthTokenno sensitive capability
  • getAuthUserno sensitive capability
  • getBypassIpno sensitive capability
  • getCertByIdno sensitive capability
  • getCheckno sensitive capability
  • getConfigurationno sensitive capability
  • getConfigurationsno sensitive capability
  • getCustomEnvironmentno sensitive capability
  • getCustomEnvironmentsno sensitive capability
  • getDeploymentno sensitive capability
  • getDeploymentEventsno sensitive capability
  • getDeploymentFileContentsno sensitive capability
  • getDeploymentsno sensitive capability
  • getDomainno sensitive capability
  • getDomainConfigno sensitive capability
  • getEdgeConfigno sensitive capability
  • getEdgeConfigItemno sensitive capability
  • getEdgeConfigItemsno sensitive capability
  • getEdgeConfigsno sensitive capability
  • getEdgeConfigSchemano sensitive capability
  • getEdgeConfigTokenno sensitive capability
  • getEdgeConfigTokensno sensitive capability
  • getEnvVarno sensitive capability
  • getFirewallConfigno sensitive capability
  • getIntegrationLogDrainsno sensitive capability
  • getInvoiceno sensitive capability
  • getMemberno sensitive capability
  • getProjectDomainno sensitive capability
  • getProjectMembersno sensitive capability
  • getTeamno sensitive capability
  • getTeamAccessRequestno sensitive capability
  • getTeamMembersno sensitive capability
  • getTeamsno sensitive capability
  • getWebhooksno sensitive capability
  • gitNamespacesno sensitive capability
  • inviteUserToTeamno sensitive capability
  • issueCertno sensitive capability
  • joinTeamno sensitive capability
  • listAccessGroupMembersno sensitive capability
  • listAccessGroupProjectsno sensitive capability
  • listAccessGroupsno sensitive capability
  • listAliasesno sensitive capability
  • listAuthTokensno sensitive capability
  • listDeploymentAliasesno sensitive capability
  • listDeploymentFilesno sensitive capability
  • listDnsRecordsno sensitive capability
  • listDomainsno sensitive capability
  • listEnvVarsno sensitive capability
  • listProjectDomainsno sensitive capability
  • listProjectsno sensitive capability
  • listUserEventsno sensitive capability
  • patchEdgeConfigSchemano sensitive capability
  • patchTeamno sensitive capability
  • putFirewallConfigno sensitive capability
  • readAccessGroupno sensitive capability
  • readAccessGroupProjectno sensitive capability
  • recordArtifactEventsno sensitive capability
  • removeBypassIpno sensitive capability
  • removeCertno sensitive capability
  • removeEnvVarno sensitive capability
  • removeProjectDomainno sensitive capability
  • removeProjectMemberno sensitive capability
  • removeTeamMemberno sensitive capability
  • requestAccessToTeamno sensitive capability
  • requestDeleteno sensitive capability
  • rerequestCheckno sensitive capability
  • searchRepono sensitive capability
  • submitBillingDatano sensitive capability
  • submitInvoiceno sensitive capability
  • updateAccessGroupno sensitive capability
  • updateAccessGroupProjectno sensitive capability
  • updateAttackChallengeModeno sensitive capability
  • updateCheckno sensitive capability
  • updateCustomEnvironmentno sensitive capability
  • updateDnsRecordno sensitive capability
  • updateEdgeConfigno sensitive capability
  • updateFirewallConfigno sensitive capability
  • updateInvoiceno sensitive capability
  • updateProjectno sensitive capability
  • updateProjectDomainno sensitive capability
  • updateResourceSecretsno sensitive capability
  • updateResourceSecretsByIdno sensitive capability
  • updateTeamMemberno sensitive capability
  • uploadArtifactno sensitive capability
  • uploadCertno sensitive capability
  • verifyProjectDomainno sensitive capability

Toxic flows 1

Cross-tool combinations that form a data-exfiltration primitive (untrusted input → sensitive source → external sink).

What this scan could not see

Versions 1

Scan history per published version. The engine is deterministic — the same version always yields the same score, so a changed score means the package itself changed.

VersionScoreFindingsEngineScanned
v0.1.1 latest A 96/100 1 1.13.0 2026-09-07

Embed this score

Show this server's live Trust Score in your README, docs or website. The badge is served straight from the registry and updates automatically after every rescan — no API key needed. It links back to this page, so anyone who sees the grade can also read the findings behind it instead of taking a number on faith.

MCP Trust Score: A · 96/100
Markdown (GitHub README)
[![MCP Trust Score](https://mcptrustchecker.com/registry/mistertk-vercel-mcp/badge.svg)](https://mcptrustchecker.com/registry/mistertk-vercel-mcp)
HTML
<a href="https://mcptrustchecker.com/registry/mistertk-vercel-mcp"><img src="https://mcptrustchecker.com/registry/mistertk-vercel-mcp/badge.svg" alt="MCP Trust Score" height="20"></a>
Prefer shields.io styling? Point it at https://mcptrustchecker.com/registry/mistertk-vercel-mcp/badge.json via https://img.shields.io/endpoint?url=…

Verify this score yourself

The score above is reproducible: the same package version always yields the same result. Run it locally or over the free API — no account, no LLM, fully deterministic.

npx mcptrustchecker scan @mistertk/vercel-mcp --online

Use the free API → How scoring works

Other implementations of Vercel 6

Independent packages implementing the same tool, scanned with the same engine. Compare all 7 side by side →

More in Analytics & Monitoring