Socket (BYOK)

Socket (BYOK) — connector documentation

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

What Socket (BYOK) is for

Socket (BYOK) lets an AI assistant read your own Socket data through the Socket API with a key you supply (Socket organization API token (sktsec_...)). Read-only: 11 tools (get_quota, list_organizations, list_repositories, get_repository, list_full_scans, get_full_scan_metadata, list_alerts, list_diff_scans, list_threat_feed, list_audit_log, list_webhooks). 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.socket.dev. Unofficial connector by Unify Dynamics LLC: not affiliated with, endorsed by or sponsored by Socket. Socket 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:

• "How much Socket API quota do I have left?"
• "Which Socket organization is my token for?"
• "Which repositories are tracked in my Socket organization?"
• "Show the Socket repository web-app in my organization"
• "What are the latest Socket scans of the main branch of web-app?"
• "Show metadata of Socket full scan s1"

What it does

• get_quota: Show how many Socket API quota units the token has left, the maximum and when the window refreshes. This call uses no quota.
• list_organizations: List the Socket organizations the token belongs to, keyed by organization id, with name, slug and plan. Each call uses 1 unit of the key's Socket API quota.
• list_repositories: List the repositories of an organization with visibility, default branch, workspace and the id of the latest full scan. Each call uses 1 unit of the key's Socket API quota.
• get_repository: Get one repository of an organization by slug: visibility, default branch, workspace, latest full scan id and tracked branch patterns. Each call uses 1 unit of the key's Socket API quota.
• list_full_scans: List full scans of an organization with repository, branch, commit, scan type, state and report link; filter by repository, branch, pull request or commit. Each call uses 1 unit of the key's Socket API quota.
• get_full_scan_metadata: Get metadata of one full scan by id: repository, branch, commit, pull request, scan type, state and report link. Each call uses 1 unit of the key's Socket API quota.
• list_alerts: List the latest security alerts of an organization with type, category, severity, status, title and dashboard link; filter by severity, status, type or repository. Each call uses 1 unit of the key's Socket API quota.
• list_diff_scans: List diff scans (comparisons between two full scans) of an organization with before and after scan ids, description and links. Each call uses 1 unit of the key's Socket API quota.
• list_threat_feed: List packages Socket flagged as threats (malware, vulnerability, typosquat and others) with ecosystem purl, threat type, review flag and dates. Each call uses 1 unit of the key's Socket API quota.
• list_audit_log: List organization audit log events (needs a token with the audit-log scope) with time, type, user email and status code. Each call uses 1 unit of the key's Socket API quota.
• list_webhooks: List the organization's webhooks with name, target URL and subscribed events (secrets are not returned). Each call uses 1 unit of the key's Socket API quota.

BYOK key

You bring your own Socket Socket organization API token (sktsec_...) (https://socket.dev/dashboard/settings/api-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.socket.dev 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://docs.socket.dev/reference/introduction-to-socket-api (the API this connector calls, with a BYOK key)

Live from the Socket API (api.socket.dev) with a BYOK key; documentation: https://docs.socket.dev/reference/introduction-to-socket-api. 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 Socket. Socket 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 Socket account.

Built for: Worldwide. Languages: English.

Socket (BYOK) — Privacy Policy

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

What Socket (BYOK) is. Socket (BYOK) is a connector (an MCP server and REST API) that an AI assistant calls on your behalf to read your own Socket data: Read your Socket supply chain security repositories, full scans, diff scans, alerts, threat feed, audit log and webhooks with your own organization API token. You bring your own Socket Socket organization API token (sktsec_...); the assistant sends it to us with each request.

BYOK key. The key you supply is used to make the one Socket 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.socket.dev, over https, and is removed from any text we return to you or your assistant. We do not follow redirects with your key. If Socket 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 Socket receives. The request we make on your behalf, including the key and the arguments, under Socket's own terms and privacy policy. Socket acts at your direction and is the only recipient of the data of your request besides our hosting provider.

What we return. The answer Socket 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 Socket 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. Socket (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 Socket at any time to end all access.

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

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

Socket (BYOK) — Terms of Service

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

1. The Service. Socket (BYOK) provides: Read your Socket supply chain security repositories, full scans, diff scans, alerts, threat feed, audit log and webhooks with your own organization API 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 Socket credentials and only access data you are allowed to access. Socket's terms apply to your use of Socket; 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 Socket. Socket 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 Socket returns, lightly trimmed; it may be incomplete, delayed or changed by Socket. Check important facts at the source.
5. Read-only. The Service does not create, change, send or delete anything in your Socket 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 Socket'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; Socket 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 Socket 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 Socket 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-socketdev

Socket (BYOK) support

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

• MCP endpoint: https://byok-socketdev.connectorbay.com/mcp
• REST API: https://byok-socketdev.connectorbay.com/openapi.json
• Live status: https://byok-socketdev.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. Socket (BYOK) never asks for them.