Vercel Registry and Networking (BYOK)

Vercel Registry and Networking (BYOK) — connector documentation

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

What Vercel Registry and Networking (BYOK) is for

Vercel Registry and Networking (BYOK) lets an AI assistant read your own Vercel Registry and Networking data through the Vercel Registry and Networking API with a key you supply (access token). Read-only: 9 tools (list_registry_repositories, get_registry_repository, list_registry_images, list_registry_tags, get_registry_tag, list_secure_compute_networks, get_secure_compute_network, list_privatelink_endpoints, get_privatelink_endpoint). 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 Registry and Networking. Vercel Registry and Networking 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 container repositories does my Vercel project have?"
• "Show the Vercel registry repository web-app"
• "Which images are in my Vercel repository web-app?"
• "What tags does my Vercel repository web-app have?"
• "Show the latest tag of my Vercel repository web-app"
• "Which Secure Compute networks do I have on Vercel?"

What it does

• list_registry_repositories: List the container registry repositories of a Vercel project with name, visibility and dates.
• get_registry_repository: Get one container registry repository by id or name: project, visibility and dates.
• list_registry_images: List the images of a container repository with digest, platform, size, status and tags. Can show only untagged images.
• list_registry_tags: List the tags of a container repository with the image they point to, digest, platform, size and status.
• get_registry_tag: Get one tag of a container repository: image id, digest, platform, size, status and dates.
• list_secure_compute_networks: List Secure Compute networks with status, region, CIDR and counts of attached projects, peering connections and hosted zones.
• get_secure_compute_network: Get one Secure Compute network by id: status, region, CIDR and counts of attached projects, peering connections and hosted zones.
• list_privatelink_endpoints: List the AWS PrivateLink endpoints of a Vercel project with status, region, AWS service name and dates.
• get_privatelink_endpoint: Get one PrivateLink endpoint of a project: status, region, AWS service name and dates.

BYOK key

You bring your own Vercel Registry and Networking 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

• https://vercel.com/docs/rest-api/reference (the API this connector calls, with a BYOK key)

Live from the Vercel Registry and Networking API (api.vercel.com) with a BYOK key; documentation: https://vercel.com/docs/rest-api/reference. 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 Registry and Networking. Vercel Registry and Networking 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 Registry and Networking account.

Built for: Worldwide. Languages: English.

Vercel Registry and Networking (BYOK) — Privacy Policy

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

What Vercel Registry and Networking (BYOK) is. Vercel Registry and Networking (BYOK) is a connector (an MCP server and REST API) that an AI assistant calls on your behalf to read your own Vercel Registry and Networking data: Read Vercel container registry repositories, images and tags, Secure Compute networks and PrivateLink endpoints with your own access token. You bring your own Vercel Registry and Networking access token; the assistant sends it to us with each request.

BYOK key. The key you supply is used to make the one Vercel Registry and Networking 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 Registry and Networking 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 Registry and Networking receives. The request we make on your behalf, including the key and the arguments, under Vercel Registry and Networking's own terms and privacy policy. Vercel Registry and Networking 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 Registry and Networking 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 Registry and Networking 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 Registry and Networking (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 Registry and Networking at any time to end all access.

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

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

Vercel Registry and Networking (BYOK) — Terms of Service

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

1. The Service. Vercel Registry and Networking (BYOK) provides: Read Vercel container registry repositories, images and tags, Secure Compute networks and PrivateLink endpoints 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 Registry and Networking credentials and only access data you are allowed to access. Vercel Registry and Networking's terms apply to your use of Vercel Registry and Networking; 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 Registry and Networking. Vercel Registry and Networking 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 Registry and Networking returns, lightly trimmed; it may be incomplete, delayed or changed by Vercel Registry and Networking. Check important facts at the source.
5. Read-only. The Service does not create, change, send or delete anything in your Vercel Registry and Networking 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 Registry and Networking'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 Registry and Networking 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 Registry and Networking 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 Registry and Networking 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-registry-networking

Vercel Registry and Networking (BYOK) support

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

• MCP endpoint: https://byok-vercel-registry-networking.connectorbay.com/mcp
• REST API: https://byok-vercel-registry-networking.connectorbay.com/openapi.json
• Live status: https://byok-vercel-registry-networking.connectorbay.com/health

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 Registry and Networking (BYOK) never asks for them.