Vercel (robinson_ai_systems) MCP Server

@robinson_ai_systems/vercel-mcp npm v1.0.1

Published by @robinson_ai_systems — no publish provenance and no public repository, so the publisher could not be verified and the source cannot be independently located.

Comprehensive Vercel MCP server with 50+ tools for deployments, domains, env vars, and more

Trust grade
A
92/100
Last scanned get badge →
Trust
A · 92/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
High
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 = 92/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 − 8 = 92. 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
−6 capability blast radius (high) — client exposure if the model is manipulated
−2 publisher verification (unlinked) — no provenance/repo link, but the shipped source was fully read

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 3

high Sensitive-source and external-sink co-existMTC-FLOW-004

Tools that read sensitive data ([vercel_list_secrets, vercel_list_deployment_files, vercel_kv_list_keys]) and tools that can send data out ([vercel_create_webhook, vercel_delete_webhook, vercel_create_comment]) are exposed together. An agent can move private data to the sink.

Evidence: sources [vercel_list_secrets, vercel_list_deployment_files, vercel_kv_list_keys] → sinks [vercel_create_webhook, vercel_delete_webhook, vercel_create_comment]

Fix: Keep secret-reading and egress capabilities on separate, separately-approved servers.

Location: flow vercel_list_secrets → vercel_create_webhook

high Shell/command execution in server code (count-all-tools.cjs)MTC-SRC-002

In the server's implementation (`count-all-tools.cjs:1`): Spawning a shell/process is command-execution capability; with unsanitized tool input it is command injection / RCE. This is read from the code itself — not from the tool description — so a poisoned server cannot hide it behind honest-looking metadata.

Evidence: st { spawn } = require('child_process'); const vercelToken = process.argv[2] || process.env.VERCEL_TOKEN || ''; if (!v

Fix: Review this call path: confirm it never receives unsanitized tool input, constrain it, or remove it. Treat a server whose code reaches these sinks as high-capability regardless of what its tools claim.

Location: server count-all-tools.cjs

medium Unconstrained URL/host parameter "url" on "vercel_create_webhook"MTC-CAP-007

Tool "vercel_create_webhook" takes a URL/host parameter "url" with no allowlist/pattern. An outbound-request tool with an unbounded destination enables SSRF and cloud-metadata access (e.g. 169.254.169.254).

Fix: Allowlist destinations or constrain the parameter; block private/link-local addresses server-side.

Location: tool vercel_create_webhook · inputSchema.properties.url

Tools 150

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

  • vercel_create_commentnetwork egress
  • vercel_create_webhooknetwork egress
  • vercel_delete_webhooknetwork egress
  • vercel_kv_list_keysreads sensitive data
  • vercel_list_deployment_filesreads sensitive data
  • vercel_list_secretsreads sensitive data
  • vercel_add_domainno sensitive capability
  • vercel_assign_aliasno sensitive capability
  • vercel_blob_deleteno sensitive capability
  • vercel_blob_headno sensitive capability
Show 140 more tools ↓
  • vercel_blob_listno sensitive capability
  • vercel_blob_putno sensitive capability
  • vercel_block_ipno sensitive capability
  • vercel_bulk_create_env_varsno sensitive capability
  • vercel_cancel_deploymentno sensitive capability
  • vercel_clone_storageno sensitive capability
  • vercel_connect_git_repositoryno sensitive capability
  • vercel_create_alertno sensitive capability
  • vercel_create_checkno sensitive capability
  • vercel_create_cron_jobno sensitive capability
  • vercel_create_custom_headerno sensitive capability
  • vercel_create_deploymentno sensitive capability
  • vercel_create_dns_recordno sensitive capability
  • vercel_create_edge_configno sensitive capability
  • vercel_create_env_varno sensitive capability
  • vercel_create_firewall_ruleno sensitive capability
  • vercel_create_projectno sensitive capability
  • vercel_create_redirectno sensitive capability
  • vercel_create_secretno sensitive capability
  • vercel_delete_aliasno sensitive capability
  • vercel_delete_commentno sensitive capability
  • vercel_delete_cron_jobno sensitive capability
  • vercel_delete_custom_headerno sensitive capability
  • vercel_delete_deploymentno sensitive capability
  • vercel_delete_dns_recordno sensitive capability
  • vercel_delete_env_varno sensitive capability
  • vercel_delete_firewall_ruleno sensitive capability
  • vercel_delete_projectno sensitive capability
  • vercel_delete_redirectno sensitive capability
  • vercel_delete_secretno sensitive capability
  • vercel_deploy_middlewareno sensitive capability
  • vercel_disconnect_git_repositoryno sensitive capability
  • vercel_enable_attack_challenge_modeno sensitive capability
  • vercel_export_audit_logsno sensitive capability
  • vercel_export_blob_datano sensitive capability
  • vercel_export_usage_reportno sensitive capability
  • vercel_get_audit_logno sensitive capability
  • vercel_get_bandwidth_usageno sensitive capability
  • vercel_get_billing_summaryno sensitive capability
  • vercel_get_build_logsno sensitive capability
  • vercel_get_cache_metricsno sensitive capability
  • vercel_get_compliance_reportno sensitive capability
  • vercel_get_cost_breakdownno sensitive capability
  • vercel_get_deploymentno sensitive capability
  • vercel_get_deployment_diffno sensitive capability
  • vercel_get_deployment_eventsno sensitive capability
  • vercel_get_deployment_fileno sensitive capability
  • vercel_get_deployment_healthno sensitive capability
  • vercel_get_deployment_logsno sensitive capability
  • vercel_get_domainno sensitive capability
  • vercel_get_edge_config_itemsno sensitive capability
  • vercel_get_error_logsno sensitive capability
  • vercel_get_error_rateno sensitive capability
  • vercel_get_firewall_analyticsno sensitive capability
  • vercel_get_function_invocationsno sensitive capability
  • vercel_get_git_integration_statusno sensitive capability
  • vercel_get_integrationno sensitive capability
  • vercel_get_integration_logsno sensitive capability
  • vercel_get_invoiceno sensitive capability
  • vercel_get_middleware_logsno sensitive capability
  • vercel_get_middleware_metricsno sensitive capability
  • vercel_get_performance_insightsno sensitive capability
  • vercel_get_projectno sensitive capability
  • vercel_get_project_analyticsno sensitive capability
  • vercel_get_response_timeno sensitive capability
  • vercel_get_runtime_logs_streamno sensitive capability
  • vercel_get_security_eventsno sensitive capability
  • vercel_get_security_headersno sensitive capability
  • vercel_get_spending_limitsno sensitive capability
  • vercel_get_storage_usageno sensitive capability
  • vercel_get_teamno sensitive capability
  • vercel_get_team_activityno sensitive capability
  • vercel_get_team_usageno sensitive capability
  • vercel_get_tracesno sensitive capability
  • vercel_get_uptime_metricsno sensitive capability
  • vercel_get_usage_metricsno sensitive capability
  • vercel_get_web_vitalsno sensitive capability
  • vercel_import_blob_datano sensitive capability
  • vercel_install_integrationno sensitive capability
  • vercel_invite_team_memberno sensitive capability
  • vercel_kv_deleteno sensitive capability
  • vercel_kv_getno sensitive capability
  • vercel_kv_setno sensitive capability
  • vercel_list_access_eventsno sensitive capability
  • vercel_list_aliasesno sensitive capability
  • vercel_list_audit_logsno sensitive capability
  • vercel_list_blocked_ipsno sensitive capability
  • vercel_list_checksno sensitive capability
  • vercel_list_commentsno sensitive capability
  • vercel_list_cron_jobsno sensitive capability
  • vercel_list_custom_headersno sensitive capability
  • vercel_list_deploymentsno sensitive capability
  • vercel_list_dns_recordsno sensitive capability
  • vercel_list_domainsno sensitive capability
  • vercel_list_edge_configsno sensitive capability
  • vercel_list_env_varsno sensitive capability
  • vercel_list_firewall_rulesno sensitive capability
  • vercel_list_git_repositoriesno sensitive capability
  • vercel_list_integration_configurationsno sensitive capability
  • vercel_list_integrationsno sensitive capability
  • vercel_list_invoicesno sensitive capability
  • vercel_list_middlewareno sensitive capability
  • vercel_list_projectsno sensitive capability
  • vercel_list_redirectsno sensitive capability
  • vercel_list_team_membersno sensitive capability
  • vercel_list_teamsno sensitive capability
  • vercel_list_webhooksno sensitive capability
  • vercel_optimize_storageno sensitive capability
  • vercel_pause_deploymentno sensitive capability
  • vercel_postgres_create_databaseno sensitive capability
  • vercel_postgres_delete_databaseno sensitive capability
  • vercel_postgres_get_connection_stringno sensitive capability
  • vercel_postgres_list_databasesno sensitive capability
  • vercel_promote_deploymentno sensitive capability
  • vercel_redeployno sensitive capability
  • vercel_remove_domainno sensitive capability
  • vercel_remove_team_memberno sensitive capability
  • vercel_rename_secretno sensitive capability
  • vercel_resolve_commentno sensitive capability
  • vercel_resume_deploymentno sensitive capability
  • vercel_rollback_deploymentno sensitive capability
  • vercel_scan_deployment_securityno sensitive capability
  • vercel_sync_git_repositoryno sensitive capability
  • vercel_test_middlewareno sensitive capability
  • vercel_trigger_cron_jobno sensitive capability
  • vercel_trigger_integration_syncno sensitive capability
  • vercel_unblock_ipno sensitive capability
  • vercel_uninstall_integrationno sensitive capability
  • vercel_update_checkno sensitive capability
  • vercel_update_commentno sensitive capability
  • vercel_update_cron_jobno sensitive capability
  • vercel_update_edge_config_itemsno sensitive capability
  • vercel_update_env_varno sensitive capability
  • vercel_update_firewall_ruleno sensitive capability
  • vercel_update_integration_configurationno sensitive capability
  • vercel_update_projectno sensitive capability
  • vercel_update_security_headersno sensitive capability
  • vercel_update_spending_limitsno sensitive capability
  • vercel_update_team_member_roleno sensitive capability
  • vercel_verify_domainno 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
v1.0.1 latest A 92/100 3 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 · 92/100
Markdown (GitHub README)
[![MCP Trust Score](https://mcptrustchecker.com/registry/robinson-ai-systems-vercel-mcp/badge.svg)](https://mcptrustchecker.com/registry/robinson-ai-systems-vercel-mcp)
HTML
<a href="https://mcptrustchecker.com/registry/robinson-ai-systems-vercel-mcp"><img src="https://mcptrustchecker.com/registry/robinson-ai-systems-vercel-mcp/badge.svg" alt="MCP Trust Score" height="20"></a>
Prefer shields.io styling? Point it at https://mcptrustchecker.com/registry/robinson-ai-systems-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 @robinson_ai_systems/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