Be the first to get access to new connectors. Get early access →
ConnectorBay Early access

FOSSA (BYOK) — connector documentation

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

What FOSSA (BYOK) is for

FOSSA (BYOK) lets an AI assistant read your own FOSSA data through the FOSSA API with a key you supply (FOSSA API token (a Full access token is needed for the issues API)). Read-only: 7 tools (list_issues, get_issue, count_issues_by_category, count_issues_by_status, list_teams, list_team_projects, get_project_branches). 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 app.fossa.com. Unofficial connector by Unify Dynamics LLC: not affiliated with, endorsed by or sponsored by FOSSA. FOSSA 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 critical vulnerabilities are active across our FOSSA projects?"
  • "Show me FOSSA issue 12345."
  • "How many FOSSA issues do we have in each category?"
  • "How many FOSSA vulnerabilities are active versus ignored?"
  • "Which teams exist in our FOSSA organization?"
  • "Which projects does FOSSA team 1 own?"

What it does

  • list_issues: List open-source compliance issues in one category (licensing, vulnerability or quality) across the organization or for one project revision. Filter by status, severity and depth, with paging.
  • get_issue: Get the details of one FOSSA issue by id and category.
  • count_issues_by_category: Get issue counts grouped by category (licensing, vulnerability, quality) for the organization or one project revision.
  • count_issues_by_status: Get issue counts grouped by status (active, ignored) for one category.
  • list_teams: List the organization's teams.
  • list_team_projects: List the projects that belong to one team.
  • get_project_branches: Get a project with its branch references and the latest revision locator of each branch.

BYOK key

You bring your own FOSSA FOSSA API token (a Full access token is needed for the issues API) (https://docs.fossa.com/docs/api/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 app.fossa.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

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

Built for: Worldwide. Languages: English.