AfterShip (BYOK)
Read your AfterShip parcel trackings and their checkpoints and look up supported couriers with your own API key
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
Real questions, and the tools your agent calls to answer them.
list_project_checksget_project_checklist_check_runslist_deployment_check_runslist_deployment_checksget_deployment_checkVercel 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.
The publisher, Unify Dynamics LLC, states that tool inputs are processed in memory and not retained.
6 tools, grouped by job. Every one is read-only or compute-only.
https://byok-vercel-checks.connectorbay.com/mcpThree ways in, the same 6 tools.
https://byok-vercel-checks.connectorbay.com/mcpPOST https://byok-vercel-checks.connectorbay.com/v1/tools/<tool>https://connectorbay.com/openai/byok-vercel-checks.jsonhttps://connectorbay.com/v1/chat/completions · how it worksX-Upstream-Key header (get one at vercel.com).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.
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.
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.
Yes. Every tool reads or computes. Nothing is created, changed, sent, paid or deleted in your account.
Yes. It is free to use within the published rate limits; an optional Pro key raises them. There is no account to create.
Read your AfterShip parcel trackings and their checkpoints and look up supported couriers with your own API key
Read your Agenta LLMOps project: prompt applications, test sets, evaluators and the template catalog, with your own project API key
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
Read your Agora projects, project usage, Conversational AI agents, call quality records and usage insights with your own RESTful customer ID and secret
Read your AI/ML API balance, account ledger, key spend, request logs and model catalog with your own API key
Read your Airbrake projects, error groups, error occurrences and deploys with BYOK
https://byok-vercel-checks.connectorbay.com/mcpPOST 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.jsonX-Upstream-Key header of every request (never stored, logged or cached)https://byok-vercel-checks.connectorbay.com/health · Tool schemas: https://byok-vercel-checks.connectorbay.com/tools.jsonVercel 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:
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.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.
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.
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.
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.
Effective 24 October 2026. These terms govern use of the Vercel Checks (BYOK) connector ("the Service") operated by Unify Dynamics LLC ("we", "us").
Email agent@connectorbay.com. We answer within two business days.
https://byok-vercel-checks.connectorbay.com/mcphttps://byok-vercel-checks.connectorbay.com/openapi.jsonWhen 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.