GitGuardian (BYOK)

GitGuardian (BYOK) — connector documentation

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

What GitGuardian (BYOK) is for

GitGuardian (BYOK) lets an AI assistant read your own GitGuardian data through the GitGuardian API with a key you supply (GitGuardian service account or personal access token (read scopes)). Read-only: 8 tools (check_api_key, get_current_token, get_scan_quota, list_secret_incidents, get_secret_incident, list_sources, list_teams, list_team_sources). 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.gitguardian.com. Unofficial connector by Unify Dynamics LLC: not affiliated with, endorsed by or sponsored by GitGuardian. GitGuardian 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:

• "Is my GitGuardian API key valid?"
• "Which scopes does my GitGuardian key have and when does it expire?"
• "How much GitGuardian scan quota do I have left?"
• "Which critical GitGuardian secret incidents are still open?"
• "Show GitGuardian secret incident 1234"
• "Which monitored repositories are at risk in GitGuardian?"

What it does

• check_api_key: Check that the key is valid by calling the GitGuardian health endpoint; returns the detail message.
• get_current_token: Show details of the API key in use: name, type, status, scopes, creation, last use and expiry (the token value is not returned).
• get_scan_quota: Show the scan API quota of the workspace: calls used, limit, remaining and the rolling period start. Reading incidents does not use this quota.
• list_secret_incidents: List secret incidents of the workspace with detector, status, severity, validity, occurrence count and dashboard link; filter by status, severity, validity, dates and tags. Needs the incidents:read scope. Secret values and hashes are never part of the answer.
• get_secret_incident: Get one secret incident by id: detector, status, severity, validity, occurrence count, revocation state and dashboard link. Needs the incidents:read scope. Secret values and hashes are never part of the answer.
• list_sources: List the monitored sources (repositories) with type, visibility, health, criticality, open and closed incident counts and last scan status. Needs the sources:read scope.
• list_teams: List the workspace teams with name, description and whether the team is the global team.
• list_team_sources: List the sources that belong to one team with type, visibility, health, criticality and incident counts.

BYOK key

You bring your own GitGuardian GitGuardian service account or personal access token (read scopes) (https://docs.gitguardian.com/api-docs/authentication). 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.gitguardian.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://docs.gitguardian.com/api-docs/introduction (the API this connector calls, with a BYOK key)

Live from the GitGuardian API (api.gitguardian.com) with a BYOK key; documentation: https://docs.gitguardian.com/api-docs/introduction. 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 GitGuardian. GitGuardian 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 GitGuardian account.

Built for: Worldwide. Languages: English.

GitGuardian (BYOK) — Privacy Policy

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

What GitGuardian (BYOK) is. GitGuardian (BYOK) is a connector (an MCP server and REST API) that an AI assistant calls on your behalf to read your own GitGuardian data: Read your GitGuardian secret incidents (without secret values), monitored sources, teams, API token scopes and quota with your own API key. You bring your own GitGuardian GitGuardian service account or personal access token (read scopes); the assistant sends it to us with each request.

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

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

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

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

GitGuardian (BYOK) — Terms of Service

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

1. The Service. GitGuardian (BYOK) provides: Read your GitGuardian secret incidents (without secret values), monitored sources, teams, API token scopes and quota with your own API key. 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 GitGuardian credentials and only access data you are allowed to access. GitGuardian's terms apply to your use of GitGuardian; 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 GitGuardian. GitGuardian 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 GitGuardian returns, lightly trimmed; it may be incomplete, delayed or changed by GitGuardian. Check important facts at the source.
5. Read-only. The Service does not create, change, send or delete anything in your GitGuardian 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 GitGuardian'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; GitGuardian 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 GitGuardian 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 GitGuardian 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-gitguardian

GitGuardian (BYOK) support

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

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