Be the first to get access to new connectors. Get early access →
ConnectorBay Early access
Discover
Vercel Checks (BYOK) icon

Vercel Checks (BYOK)

Read your Vercel project checks, check runs and deployment checks (what blocks a deployment, and whether it passed) with your own access token

Unify Dynamics LLC

Tools6read-only
Sign-inBYOKbring your own key
Key keptNeverused for one call only
PriceFreeoptional Pro limits
ProviderVercel Checksunofficial, not affiliated
Works withMCP · RESTany agent

Try asking

Real questions, and the tools your agent calls to answer them.

Which checks gate deployments of my Vercel project?
Tools called
list_project_checks
Show Vercel project check chk_abc123 of my-site
Tools called
get_project_check
Did the Lighthouse check pass on recent deployments of my-site?
Tools called
list_check_runs
Which checks ran for Vercel deployment dpl_abc123 and what were the results?
Tools called
list_deployment_check_runs
Which integration checks are running on Vercel deployment dpl_abc123?
Tools called
list_deployment_checks
Show Vercel deployment check check_abc123 on dpl_abc123
Tools called
get_deployment_check

About

Vercel Checks (BYOK) lets an AI assistant read your own Vercel Checks data through the Vercel Checks API with a key you supply (access token). Read-only: 6 tools (list_project_checks, get_project_check, list_check_runs, list_deployment_check_runs, list_deployment_checks, get_deployment_check). The BYOK key travels with each request, is used for that one call only and is never stored, logged or cached; it is only ever sent to api.vercel.com. Unofficial connector by Unify Dynamics LLC: not affiliated with, endorsed by or sponsored by Vercel Checks. Vercel Checks and its logos are trademarks of their owners and are used only to say which service the connector works with.

Sources: Live from the Vercel Checks API (api.vercel.com) with a BYOK key; documentation: https://vercel.com/docs/rest-api/reference/endpoints/checks. Endpoints checked against that documentation on 2026-10-16.

Privacy

The publisher, Unify Dynamics LLC, states that tool inputs are processed in memory and not retained.

Data not collectedNo account, no profile, no stored prompts or results.

What it can do

6 tools, grouped by job. Every one is read-only or compute-only.

OpenAPI
Read your data6 tools
  • List project checksList the checks configured for a Vercel project: name, what each blocks (build start, deployment start, alias, promotion), when it needs the…
  • Get project checkGet one project check: what it blocks, when it runs, targets, timeout and source kind.
  • List check runsList the runs of one project check across deployments with status, conclusion, deployment and timing.
  • List deployment check runsList the check runs of one deployment with status, conclusion, what each blocks and timing.
  • List deployment checksList the integration checks registered on one deployment (older checks API) with status, conclusion, blocking flag and details link.
  • Get deployment checkGet one integration check of a deployment: status, conclusion, blocking flag, path, details link and timing.

Information

PublisherUnify Dynamics LLC
CategoryDeveloper tools
LanguagesEnglish
Built forWorldwide
CompatibilityAny MCP client · any agent · REST
Version0.1.0
MCP endpointhttps://byok-vercel-checks.connectorbay.com/mcp
REST APIopenapi.json
SupportGet help · Status
CountryWorldwide
FunctionOther
LayerDeep connectors

Connect it to your agent

Three ways in, the same 6 tools.

MCP (Claude, Cursor, Windsurf, VS Code, any MCP client)https://byok-vercel-checks.connectorbay.com/mcp
RESTPOST https://byok-vercel-checks.connectorbay.com/v1/tools/<tool>
OpenAI function callinghttps://connectorbay.com/openai/byok-vercel-checks.json
OpenAI-compatible chathttps://connectorbay.com/v1/chat/completions · how it works
  • Add the MCP URL in your client's connector, MCP or integration settings (streamable HTTP, no OAuth).
  • Key: send your access token in the X-Upstream-Key header (get one at vercel.com).
  • Ask a question; the agent picks the right tool and answers from the live data.

Vercel Checks connector: questions and answers

What is the Vercel Checks connector?

Vercel Checks (BYOK) lets an AI assistant read your own Vercel Checks data through the Vercel Checks API with a key you supply (access token). It is a hosted MCP server with 6 tools such as List project checks, Get project check, List check runs, List deployment check runs, List deployment checks, Get deployment check, published by Unify Dynamics LLC. It is independent and not affiliated with Vercel Checks.

How do I connect Vercel Checks to Claude, ChatGPT or Cursor?

Add the MCP endpoint https://byok-vercel-checks.connectorbay.com/mcp to your client's MCP, connector or integration settings (streamable HTTP, no OAuth). For REST, POST JSON to https://byok-vercel-checks.connectorbay.com/v1/tools/<tool>; the OpenAPI description is at /openapi.json. For OpenAI function calling, load https://connectorbay.com/openai/byok-vercel-checks.json.

Do I need a Vercel Checks account or API key?

Yes: this is a bring-your-own-key connector. Create a access token at https://vercel.com/account/tokens and send it in the X-Upstream-Key header. ConnectorBay uses it for that one call only and never stores, logs or caches it.

Is Vercel Checks read-only?

Yes. Every tool reads or computes. Nothing is created, changed, sent, paid or deleted in your account.

Is the Vercel Checks connector free?

Yes. It is free to use within the published rate limits; an optional Pro key raises them. There is no account to create.

More like this

More in Other

AfterShip (BYOK)

Read your AfterShip parcel trackings and their checkpoints and look up supported couriers with your own API key

Live · MCP + REST5 tools

Agenta (BYOK)

Read your Agenta LLMOps project: prompt applications, test sets, evaluators and the template catalog, with your own project API key

Live · MCP + REST8 tools

AgentMail (BYOK)

Read your AgentMail agent email infrastructure: inboxes, pods, domains, webhooks, API key metadata, organization limits and usage, never message content, with your own API key

Live · MCP + REST9 tools

Agora REST (BYOK)

Read your Agora projects, project usage, Conversational AI agents, call quality records and usage insights with your own RESTful customer ID and secret

Live · MCP + REST7 tools

AIMLAPI (BYOK)

Read your AI/ML API balance, account ledger, key spend, request logs and model catalog with your own API key

Live · MCP + REST7 tools

Airbrake (BYOK)

Read your Airbrake projects, error groups, error occurrences and deploys with BYOK

Live · MCP + REST8 tools

Documentation

Back to top

Vercel Checks (BYOK) — connector documentation

  • MCP endpoint: https://byok-vercel-checks.connectorbay.com/mcp
  • REST API: POST https://byok-vercel-checks.connectorbay.com/v1/tools/{tool_name}, described by the OpenAPI 3.1 spec at https://byok-vercel-checks.connectorbay.com/openapi.json
  • Transport: Streamable HTTP, stateless, MCP specification 2025-06-18 or later
  • Authentication: your own Vercel Checks access token, sent in the X-Upstream-Key header of every request (never stored, logged or cached)
  • Health: https://byok-vercel-checks.connectorbay.com/health · Tool schemas: https://byok-vercel-checks.connectorbay.com/tools.json
  • Publisher: Unify Dynamics LLC · connectorbay.com/byok-vercel-checks · agent@connectorbay.com

What Vercel Checks (BYOK) is for

Vercel Checks (BYOK) lets an AI assistant read your own Vercel Checks data through the Vercel Checks API with a key you supply (access token). Read-only: 6 tools (list_project_checks, get_project_check, list_check_runs, list_deployment_check_runs, list_deployment_checks, get_deployment_check). The BYOK key travels with each request, is used for that one call only and is never stored, logged or cached; it is only ever sent to api.vercel.com. Unofficial connector by Unify Dynamics LLC: not affiliated with, endorsed by or sponsored by Vercel Checks. Vercel Checks and its logos are trademarks of their owners and are used only to say which service the connector works with.

Ask your assistant things like:

  • "Which checks gate deployments of my Vercel project?"
  • "Show Vercel project check chk_abc123 of my-site"
  • "Did the Lighthouse check pass on recent deployments of my-site?"
  • "Which checks ran for Vercel deployment dpl_abc123 and what were the results?"
  • "Which integration checks are running on Vercel deployment dpl_abc123?"
  • "Show Vercel deployment check check_abc123 on dpl_abc123"

What it does

  • list_project_checks: List the checks configured for a Vercel project: name, what each blocks (build start, deployment start, alias, promotion), when it needs the deployment, targets and timeout.
  • get_project_check: Get one project check: what it blocks, when it runs, targets, timeout and source kind.
  • list_check_runs: List the runs of one project check across deployments with status, conclusion, deployment and timing.
  • list_deployment_check_runs: List the check runs of one deployment with status, conclusion, what each blocks and timing.
  • list_deployment_checks: List the integration checks registered on one deployment (older checks API) with status, conclusion, blocking flag and details link.
  • get_deployment_check: Get one integration check of a deployment: status, conclusion, blocking flag, path, details link and timing.

BYOK key

You bring your own Vercel Checks access token (https://vercel.com/account/tokens). Your assistant sends it in the X-Upstream-Key header with each request. ConnectorBay uses it for that one call only: it is never stored, logged or cached, never shown in an answer, and it is only sent to api.vercel.com over https, with no redirects followed. Create a key with the fewest permissions the tools need (read-only if the provider offers it), and revoke it at the provider whenever you like.

Data sources

Live from the Vercel Checks API (api.vercel.com) with a BYOK key; documentation: https://vercel.com/docs/rest-api/reference/endpoints/checks. Endpoints checked against that documentation on 2026-10-16.

What it is not

Unofficial connector by Unify Dynamics LLC: not affiliated with, endorsed by or sponsored by Vercel Checks. Vercel Checks and its logos are trademarks of their owners and are used only to say which service the connector works with. It is read-only: it never creates, changes, sends or deletes anything in your Vercel Checks account.

Built for: Worldwide. Languages: English.

Privacy policy

Back to top

Vercel Checks (BYOK) — Privacy Policy

Effective 24 October 2026. Unify Dynamics LLC ("we", "us"), Menlo Park, California.

What Vercel Checks (BYOK) is. Vercel Checks (BYOK) is a connector (an MCP server and REST API) that an AI assistant calls on your behalf to read your own Vercel Checks data: Read your Vercel project checks, check runs and deployment checks (what blocks a deployment, and whether it passed) with your own access token. You bring your own Vercel Checks access token; the assistant sends it to us with each request.

BYOK key. The key you supply is used to make the one Vercel Checks call you asked for. Our application does not store it, write it to a log, put it in a cache, or share it. It is sent only to api.vercel.com, over https, and is removed from any text we return to you or your assistant. We do not follow redirects with your key. If Vercel Checks rejects it, we say so without repeating it.

What we receive. The arguments of each tool call, the BYOK key (for that call only), the technical headers needed to serve the request (an IP address or a client identifier supplied by the assistant) and standard server logs. What Vercel Checks receives. The request we make on your behalf, including the key and the arguments, under Vercel Checks's own terms and privacy policy. Vercel Checks acts at your direction and is the only recipient of the data of your request besides our hosting provider.

What we return. The answer Vercel Checks gives for your request, trimmed to the fields the tool documents. We do not keep it: it is returned to your assistant and not stored, cached or used to train anything.

What we do not do. We do not build a profile, sell or share personal information, or keep your Vercel Checks data. Rate-limit counters (a client identifier and timestamps) are held in memory for at most 24 hours. Hosting access logs (IP addresses, request paths and status codes) are kept for up to 30 days for security and abuse prevention; our application adds no request headers or bodies to them.

Sub-processors. Vercel Checks (the API you call with a BYOK key, at your direction). Hosting: Vercel (United States regions).

Your rights. Because we store no personal data beyond short-lived logs, requests to access, correct or delete data are usually satisfied automatically; you can still contact agent@connectorbay.com and we will respond within 30 days. Revoke your key at Vercel Checks at any time to end all access.

Children. Vercel Checks (BYOK) is a general-audience service operated by the adult using the assistant, under Vercel Checks's own age rules.

Changes. We will post changes here with a new effective date.

Terms of service

Back to top

Vercel Checks (BYOK) — Terms of Service

Effective 24 October 2026. These terms govern use of the Vercel Checks (BYOK) connector ("the Service") operated by Unify Dynamics LLC ("we", "us").

  1. The Service. Vercel Checks (BYOK) provides: Read your Vercel project checks, check runs and deployment checks (what blocks a deployment, and whether it passed) with your own access token. It is accessed through an AI assistant or directly over MCP or HTTP, and is read-only.
  2. Your own key, your own account. You must use your own Vercel Checks credentials and only access data you are allowed to access. Vercel Checks's terms apply to your use of Vercel Checks; you are responsible for complying with them, including any rate limits and permitted uses. Do not share a key you do not own.
  3. Independent. Unofficial connector by Unify Dynamics LLC: not affiliated with, endorsed by or sponsored by Vercel Checks. Vercel Checks and its logos are trademarks of their owners and are used only to say which service the connector works with.
  4. No advice, no guarantees. Output is the data Vercel Checks returns, lightly trimmed; it may be incomplete, delayed or changed by Vercel Checks. Check important facts at the source.
  5. Read-only. The Service does not create, change, send or delete anything in your Vercel Checks account.
  6. Acceptable use. Automated use within the published rate limits is welcome. Do not use the Service to access data you are not entitled to, to circumvent Vercel Checks's controls, or to attack any system.
  7. Availability. The Service is provided "as is" without warranty. We may change, limit or discontinue it at any time; Vercel Checks may change or end its API at any time.
  8. Data. Our Privacy Policy describes what we process. In short: the BYOK key is used for the one call and not stored or logged.
  9. Pro keys. Optional ConnectorBay Pro API keys are issued at our discretion and are separate from your Vercel Checks key.
  10. Liability. To the fullest extent permitted by law, Unify Dynamics LLC is not liable for any loss arising from use of or reliance on the Service, including any action Vercel Checks takes on your account. Our total liability is limited to US $100.
  11. Governing law. California law; venue in San Mateo County, California.
  12. Contact. Unify Dynamics LLC · agent@connectorbay.com · https://connectorbay.com/byok-vercel-checks

Vercel Checks (BYOK) support

Email agent@connectorbay.com. We answer within two business days.

When you report a problem, include the question you asked your agent, roughly when, and which agent you used (for example Claude, ChatGPT or Gemini). Never send us passwords, account numbers or ID numbers. Vercel Checks (BYOK) never asks for them.

Get Vercel Checks (BYOK)

Free · BYOK · Read-only

BYOK: bring your own keyThis connector uses your own Vercel Checks access token. Create one at https://vercel.com/account/tokens, with the fewest permissions it needs (read-only if the provider offers it). Your assistant sends it in the X-Upstream-Key header with every request. It is used for that one call only: never stored, logged or cached, and only ever sent to Vercel Checks. Revoke it at the provider whenever you like. Unofficial connector: not affiliated with Vercel Checks.