FOSSA MCP Server

A Model Context Protocol server for the FOSSA API that allows AI assistants to inspect FOSSA organizations and answer practical software composition analysis questions.

Unofficial project. Not affiliated with, endorsed by, or supported by FOSSA, Inc. "FOSSA" is a trademark of FOSSA, Inc., used here only to identify the API this software interoperates with. For the official product and support, see fossa.com.

Safety Statement

This version is read-only and does not modify FOSSA state.

Related MCP server: SonarQube MCP Server

Deployment model — single-tenant

This server is designed to be run by one operator with one FOSSA API token. You run your own instance; there is no multi-user mode.

⚠️ The server executes every request using the single FOSSA_API_TOKEN it was started with. It does not authenticate callers or scope requests per user. If you expose the HTTP transport to other people, every one of them gets the full access of that token — including anything it can read across your FOSSA organization.

• stdio is the default transport and the intended deployment shape: your MCP client launches the process, and the token stays local to it.

• streamable-http binds 127.0.0.1 by default and is intended for local or sidecar use. Do not put it on a shared network interface without an authenticating proxy in front of it.

Requirements

• Python 3.13+

• uv

• Full FOSSA API token for live calls

• Node/npm only when launching MCP Inspector through mcp dev

Setup

git clone <repo>
cd fossa-mcp
uv sync
cp .env.example .env

Then edit .env and add your FOSSA API token:

FOSSA_API_TOKEN=<your-full-api-token>

Validate

uv run pytest
uv run ruff check .
uv run ruff format --check .
uv run pyright

pytest never touches the network; the live smoke test is opt-in via uv run pytest -m live and needs a real FOSSA_API_TOKEN.

MCP Inspector

uv run mcp dev src/fossa_mcp/server.py

stdio

uv run fossa-mcp

Streamable HTTP

uv run fossa-mcp --transport streamable-http

Container

docker run --rm -i -e FOSSA_API_TOKEN=<your-full-api-token> rashford/fossa-mcp:0.1

For streamable-http, publish the port and override the default CMD:

docker run --rm -p 8000:8000 -e FOSSA_API_TOKEN=<your-full-api-token> \
  rashford/fossa-mcp:0.1 --transport streamable-http

Images are tagged :0.1.0 and :0.1. :latest is intentionally not published until a release has soaked — see DECISIONS.md.

Every image ships LICENSE, NOTICE, and a consolidated /app/THIRD_PARTY_LICENSES.txt covering every runtime dependency actually installed in that image, generated at build time by scripts/generate_third_party_licenses.py.

Tools

Example Prompts

List my FOSSA projects sorted by security issues, highest first.

Show active critical and high vulnerabilities for revision <REVISION_LOCATOR>.

Compare revision <NEW_REVISION> with <OLD_REVISION> and show only new vulnerability issues.

Give me the FOSSA risk posture for project <PROJECT_LOCATOR> at revision <REVISION_LOCATOR>.

Generate the Markdown attribution report for revision <REVISION_LOCATOR>.

License

Licensed under the Apache License, Version 2.0. See NOTICE for attribution, the trademark disclaimer, and third-party license information.

All runtime dependencies are under permissive licenses (MIT, BSD, Apache-2.0, ISC, PSF) with the exception of certifi, which is MPL-2.0 and is redistributed unmodified.

Container images are built on SUSE Base Container Images, which carry SUSE's own license terms separate from this project's.

Project decisions — including the deliberate mcp version pin and the single-tenant constraint — are recorded in DECISIONS.md.