Semgrep (BYOK)

Semgrep (BYOK) — connector documentation

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

What Semgrep (BYOK) is for

Semgrep (BYOK) lets an AI assistant read your own Semgrep data through the Semgrep API with a key you supply (Semgrep API token with Web API access enabled). Read-only: 9 tools (list_deployments, list_projects, get_project, list_findings, search_scans, get_scan, search_dependencies, list_secrets_findings, list_policies). 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 semgrep.dev. Unofficial connector by Unify Dynamics LLC: not affiliated with, endorsed by or sponsored by Semgrep. Semgrep 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 Semgrep deployment is my token for?"
• "Which of my repositories does Semgrep scan?"
• "When was acme/web last scanned by Semgrep?"
• "What open high severity Semgrep findings do I have?"
• "Which Semgrep scans failed recently?"
• "Show me the details of Semgrep scan 1"

What it does

• list_deployments: List the Semgrep deployment (organisation) your token can access, with its numeric id, name and slug. Use the id and slug in the other tools.
• list_projects: List projects (repositories) scanned by Semgrep with default branch, last scan time, creation time and tags. Archived repositories are left out.
• get_project: Get one project by name (for example 'acme/web'): branches, last scan time, tags and URL.
• list_findings: List Semgrep findings: code (sast), supply chain (sca) or AI-powered detection (ai_sast), newest first, with severity, status, rule, repository, file and line, and for supply chain the vulnerable package, reachability and fix versions.
• search_scans: List scans of the last 30 days with status, branch, commit, finding counts and duration. Filter by repository id, branch or start time.
• get_scan: Get one scan: status, exit code, branch, commit, repository, CI job URL, enabled products and statistics.
• search_dependencies: Find a package in your projects' dependency lists (software bill of materials): ecosystem, version, licences, whether direct or transitive and where it is defined.
• list_secrets_findings: List secrets findings (leaked credentials detected in code) with type, severity, status, validation state, repository, file path and branch. The secret values themselves are not part of the answer.
• list_policies: List Semgrep policies (rule sets applied to repositories) with name, slug, product type and whether the policy is the default.

BYOK key

You bring your own Semgrep Semgrep API token with Web API access enabled (https://semgrep.dev/orgs/-/settings/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 semgrep.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.semgrep.dev/public_v1.openapi.yaml (the API this connector calls, with a BYOK key)

Live from the Semgrep API (semgrep.dev) with a BYOK key; documentation: https://docs.semgrep.dev/public_v1.openapi.yaml. 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 Semgrep. Semgrep 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 Semgrep account.

Built for: Worldwide. Languages: English.

Semgrep (BYOK) — Privacy Policy

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

What Semgrep (BYOK) is. Semgrep (BYOK) is a connector (an MCP server and REST API) that an AI assistant calls on your behalf to read your own Semgrep data: Read your Semgrep AppSec Platform deployments, projects, code and supply chain findings, scans, dependencies, secrets findings and policies with your own API token. You bring your own Semgrep Semgrep API token with Web API access enabled; the assistant sends it to us with each request.

BYOK key. The key you supply is used to make the one Semgrep 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 semgrep.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 Semgrep 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 Semgrep receives. The request we make on your behalf, including the key and the arguments, under Semgrep's own terms and privacy policy. Semgrep acts at your direction and is the only recipient of the data of your request besides our hosting provider.

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

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

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

Semgrep (BYOK) — Terms of Service

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

1. The Service. Semgrep (BYOK) provides: Read your Semgrep AppSec Platform deployments, projects, code and supply chain findings, scans, dependencies, secrets findings and policies with your own 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 Semgrep credentials and only access data you are allowed to access. Semgrep's terms apply to your use of Semgrep; 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 Semgrep. Semgrep 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 Semgrep returns, lightly trimmed; it may be incomplete, delayed or changed by Semgrep. Check important facts at the source.
5. Read-only. The Service does not create, change, send or delete anything in your Semgrep 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 Semgrep'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; Semgrep 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 Semgrep 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 Semgrep 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-semgrep

Semgrep (BYOK) support

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

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