JFrog Xray (BYOK)

JFrog Xray (BYOK) — connector documentation

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

What JFrog Xray (BYOK) is for

JFrog Xray (BYOK) lets an AI assistant read your own JFrog Xray data through the JFrog Xray API with a key you supply (JFrog access token (a read-only scoped token is enough)). Read-only: 12 tools (get_version, list_policies, get_policy, list_watches, get_watch, list_ignore_rules, list_binary_managers, get_repos_indexing_config, get_repository_scan_config, get_db_sync_status, list_git_repositories, search_violations). 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 *.jfrog.io. Unofficial connector by Unify Dynamics LLC: not affiliated with, endorsed by or sponsored by JFrog Xray. JFrog Xray 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 Xray version does my JFrog platform run?"
• "Which Xray security policies do I have?"
• "What rules does Xray policy block-critical-cves have?"
• "Which Xray watches are active?"
• "Which resources does Xray watch prod-images monitor?"
• "Which Xray ignore rules expire soon?"

What it does

• get_version: Show the Xray version and revision.
• list_policies: List Xray policies (security, license and operational risk) with their rules, criteria, actions and the watches they are assigned to.
• get_policy: Get one Xray policy by name with its rules, criteria, actions and assigned watches.
• list_watches: List Xray watches with the repositories, builds or bundles they monitor, assigned policies and ticket settings.
• get_watch: Get one Xray watch by name with its monitored resources and assigned policies.
• list_ignore_rules: List violation ignore rules with creation time, notes, expiry and what they ignore; filter by CVE, watch or policy.
• list_binary_managers: List the Artifactory instances connected to Xray with version, license state and their repositories.
• get_repos_indexing_config: Show which repositories of one connected Artifactory are indexed by Xray and which are not.
• get_repository_scan_config: Show the scanning settings of one repository: contextual analysis, exposures, retention days and path specific settings.
• get_db_sync_status: Show the state of the Xray vulnerability database sync: last update time, state and online or offline mode (admin token needed).
• list_git_repositories: List Git repositories scanned by Xray source code scanning with provider, last scanned commit and scanned branches.
• search_violations: Search Xray violations with description, severity, type, affected components, watch, issue id and impacted artifacts; filter by watch, type, minimum severity, CVE or time. Cursor paged.

BYOK key

You bring your own JFrog Xray JFrog access token (a read-only scoped token is enough) (https://docs.jfrog.com/administration/docs/access-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 *.jfrog.io 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.jfrog.com/security/reference/xray-rest-apis/llms.txt (the API this connector calls, with a BYOK key)

Live from the JFrog Xray API (*.jfrog.io) with a BYOK key; documentation: https://docs.jfrog.com/security/reference/xray-rest-apis/llms.txt. 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 JFrog Xray. JFrog Xray 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 JFrog Xray account.

Built for: Worldwide. Languages: English.

JFrog Xray (BYOK) — Privacy Policy

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

What JFrog Xray (BYOK) is. JFrog Xray (BYOK) is a connector (an MCP server and REST API) that an AI assistant calls on your behalf to read your own JFrog Xray data: Read your JFrog Xray watches, policies, violations, ignore rules, indexed repositories and database sync status with your own access token; no scans or changes. You bring your own JFrog Xray JFrog access token (a read-only scoped token is enough); the assistant sends it to us with each request.

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

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

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

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

JFrog Xray (BYOK) — Terms of Service

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

1. The Service. JFrog Xray (BYOK) provides: Read your JFrog Xray watches, policies, violations, ignore rules, indexed repositories and database sync status with your own access token; no scans or changes. 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 JFrog Xray credentials and only access data you are allowed to access. JFrog Xray's terms apply to your use of JFrog Xray; 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 JFrog Xray. JFrog Xray 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 JFrog Xray returns, lightly trimmed; it may be incomplete, delayed or changed by JFrog Xray. Check important facts at the source.
5. Read-only. The Service does not create, change, send or delete anything in your JFrog Xray 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 JFrog Xray'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; JFrog Xray 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 JFrog Xray 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 JFrog Xray 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-jfrog-xray

JFrog Xray (BYOK) support

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

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